Skip to content
SchedulesMCP

Compare sailings the way a freight desk actually books them.

Point-to-point schedules across 5,000+ lanes and 255 ports, grouped by the physical vessel, so the carriers selling slots on the same hull show up together. Transit time, transshipment legs, cut-offs and a reliability score built from arrivals we have actually seen.

MCP call

schedulesmcp.com · live
{ "tool": "find_sailings",
"from": "Ningbo",
"to": "Rotterdam",
"after": "2026-07-01" }
response
{ "vessel": "MSC TERESA",
"carriers": ["MSC", "ZIM"], // same hull
"transit_days": 31,
"transship": "Singapore",
"cutoff": "2026-06-29",
"reliability": 0.82, // from observed arrivals
"sample": 46 }
find_sailingscompare_sailingsget_lane_reliability
5,000+ lanes · 255 ports72,000+ forward sailingsReliability from observed arrivalsMCP tools + REST API

What it does

Built for the decisions you make at the desk.

Vessel-first sailing cards

One card per physical hull. When three carriers sell slots on the same vessel, you see one sailing with three ways to book it, not three near-identical rows.

Reliability scored from real arrivals

On-time performance per lane comes from arrivals we observed through the tracking layer, not a carrier’s own marketing number. Thin lanes are honestly labelled early-data, never faked.

The detail a desk books on

Transit time, transshipment ports and legs, cut-offs, and emissions on every option: the things that decide a booking, on the card.

Type a port, not a code

Search “Shanghai”, not CNSHA. Names resolve to the codes our data actually uses, so you find the lane on the first try.

5,000+ lanes, refreshed weekly

Published schedules cached across 5,000+ lanes and 255 ports, enriched against live vessel movements, with 72,000+ forward sailings.

Call it as tools

Every capability, as a tool or an endpoint.

The same functions an assistant can call in plain language, your stack can hit over REST, behind one key, with webhooks to push the changes.

Read the SchedulesMCP docs
SchedulesMCP · tools
  • find_sailings Sailings for a lane and date window.
  • compare_sailings Rank options by transit, reliability or cut-off.
  • get_lane_reliability On-time score for a lane, with sample size.
  • get_vessel_rotation Published rotation for a vessel.

Questions

The things people ask first.

From arrivals we actually observed through the tracking layer, per lane, with the sample size shown. Thin lanes are honestly labelled early-data, never inflated.

Because several carriers often sell slots on the same hull. One vessel-first card shows one sailing and every way to book it, instead of three near-identical rows.

5,000+ lanes across 255 ports, refreshed weekly and enriched against live vessel movements, with 72,000+ forward sailings.

Yes. Type “Rotterdam”, not a UN/LOCODE. Names resolve to the codes our data actually uses.

Make your first SchedulesMCP call today.

Free tier, five-minute first call, no front-end of ours required.