io.github.lxxmng/ocean-schedules

Official12 tools

by lxxmng · TypeScript

Compare ocean carrier schedules, transit times and reliability: 60+ carriers, 72,000+ sailings.

io.github.lxxmng/ocean-schedules — MCP Server

The io.github.lxxmng/ocean-schedules MCP server compares ocean carrier sailing schedules, transit times, and on-time reliability prior to booking. It provides access to information across multiple tools (12 total) to help evaluate carrier performance using these schedule and reliability inputs.

🛠️ Key Features

Compares ocean carrier sailing schedules
Compares transit times
Compares on-time reliability
Supports 12 tools

🚀 Use Cases

Validate ocean carrier schedules before booking
Compare expected transit times across carriers
Review on-time reliability when selecting a carrier

⚡ Developer Benefits

Centralizes schedule, transit time, and reliability comparison in one MCP server
Exposes multiple tools (12) for programmatic retrieval and evaluation

⚠️ Limitations

Description does not specify supported regions, ports, carriers, or data coverage.

Topics

logisticsmcpocean-freightshippingai-agentscontainer-trackingmodel-context-protocolsupply-chain

Captured live from the server via tools/list.

compare_lanes

Compare ocean carriers serving an origin→destination port pair, ranked by on-time reliability and transit time. Use this to decide which line to book.

Parameters2

origin	string	required	Origin port UN/LOCODE, e.g. CNSHA
destination	string	required	Destination port UN/LOCODE, e.g. NLRTM

Raw schema

{
  "type": "object",
  "properties": {
    "origin": {
      "type": "string",
      "description": "Origin port UN/LOCODE, e.g. CNSHA"
    },
    "destination": {
      "type": "string",
      "description": "Destination port UN/LOCODE, e.g. NLRTM"
    }
  },
  "required": [
    "origin",
    "destination"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

carrier_reliability

On-time performance and delay distribution for a specific carrier (by SCAC), optionally on a given lane.

Parameters1

carrier_code

string

required

Carrier SCAC, e.g. MAEU

Raw schema

{
  "type": "object",
  "properties": {
    "carrier_code": {
      "type": "string",
      "description": "Carrier SCAC, e.g. MAEU"
    }
  },
  "required": [
    "carrier_code"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

transit_time

Observed transit-time distribution (median / p90, in days) for a carrier on an origin→destination lane.

Parameters3

origin	string	required	Origin port UN/LOCODE
destination	string	required	Destination port UN/LOCODE
carrier_code	string	optional	Optional carrier SCAC to filter

Raw schema

{
  "type": "object",
  "properties": {
    "origin": {
      "type": "string",
      "description": "Origin port UN/LOCODE"
    },
    "destination": {
      "type": "string",
      "description": "Destination port UN/LOCODE"
    },
    "carrier_code": {
      "type": "string",
      "description": "Optional carrier SCAC to filter"
    }
  },
  "required": [
    "origin",
    "destination"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

find_sailings

Observed and derived upcoming departures on an origin→destination lane, with carrier and frequency.

Parameters2

origin	string	required	Origin port UN/LOCODE
destination	string	required	Destination port UN/LOCODE

Raw schema

{
  "type": "object",
  "properties": {
    "origin": {
      "type": "string",
      "description": "Origin port UN/LOCODE"
    },
    "destination": {
      "type": "string",
      "description": "Destination port UN/LOCODE"
    }
  },
  "required": [
    "origin",
    "destination"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

get_schedules

Published forward sailing schedules on an origin→destination lane: carrier, vessel, voyage, ETD/ETA and cut-offs, soonest first. Sourced from carrier connectors (and aggregator coverage). Use this to find concrete upcoming departures to book.

Parameters2

origin	string	required	Origin port UN/LOCODE, e.g. CNSHA
destination	string	required	Destination port UN/LOCODE, e.g. NLRTM

Raw schema

{
  "type": "object",
  "properties": {
    "origin": {
      "type": "string",
      "description": "Origin port UN/LOCODE, e.g. CNSHA"
    },
    "destination": {
      "type": "string",
      "description": "Destination port UN/LOCODE, e.g. NLRTM"
    }
  },
  "required": [
    "origin",
    "destination"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

find_best_sailings

Decision query: the best upcoming sailings on a lane, ONE per carrier (next bookable departure), ranked. Filter by date window, max transit days, min on-time reliability, cut-off still open, and direct-vs-transshipment. Use this to answer "what should I book?".

Parameters9

origin	string	required	Origin port UN/LOCODE or name resolves upstream, e.g. CNSHA
destination	string	required	Destination port UN/LOCODE, e.g. NLRTM
from	string	optional	Earliest departure date YYYY-MM-DD (default: today)
to	string	optional	Latest departure date YYYY-MM-DD (default: +60 days)
max_transit_days	number	optional	Maximum transit time in days
reliability_floor	number	optional	Minimum 90-day on-time %, 0-100
cutoff_open	boolean	optional	Only sailings whose booking cut-off has not passed
direct_only	boolean	optional	Exclude transshipment routings
sort	string	optional	Ranking (default recommended = reliability blended with transit)

Raw schema

{
  "type": "object",
  "properties": {
    "origin": {
      "type": "string",
      "description": "Origin port UN/LOCODE or name resolves upstream, e.g. CNSHA"
    },
    "destination": {
      "type": "string",
      "description": "Destination port UN/LOCODE, e.g. NLRTM"
    },
    "from": {
      "type": "string",
      "description": "Earliest departure date YYYY-MM-DD (default: today)"
    },
    "to": {
      "type": "string",
      "description": "Latest departure date YYYY-MM-DD (default: +60 days)"
    },
    "max_transit_days": {
      "type": "number",
      "description": "Maximum transit time in days"
    },
    "reliability_floor": {
      "type": "number",
      "description": "Minimum 90-day on-time %, 0-100"
    },
    "cutoff_open": {
      "type": "boolean",
      "description": "Only sailings whose booking cut-off has not passed"
    },
    "direct_only": {
      "type": "boolean",
      "description": "Exclude transshipment routings"
    },
    "sort": {
      "type": "string",
      "enum": [
        "recommended",
        "reliability",
        "fastest",
        "soonest"
      ],
      "description": "Ranking (default recommended = reliability blended with transit)"
    }
  },
  "required": [
    "origin",
    "destination"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

watch_lane

Watch a lane for schedule alerts (PAID): get emailed when a sailing on it is blanked, a booking cut-off is about to close, or a sailing slips. Also alerts on reliability drops. Returns the created watch.

Parameters7

origin	string	required	Origin port UN/LOCODE, e.g. CNNGB
destination	string	required	Destination port UN/LOCODE, e.g. NLRTM
carrier_code	string	optional	Optional SCAC to scope the watch to one carrier
alert_blank	boolean	optional	Alert on suspected blank sailings (default true)
alert_cutoff	boolean	optional	Alert when a booking cut-off is closing (default true)
alert_slip	boolean	optional	Alert when a sailing slips vs schedule (default true)
cutoff_lead_hours	number	optional	Hours before cut-off to alert (default 48)

Raw schema

{
  "type": "object",
  "properties": {
    "origin": {
      "type": "string",
      "description": "Origin port UN/LOCODE, e.g. CNNGB"
    },
    "destination": {
      "type": "string",
      "description": "Destination port UN/LOCODE, e.g. NLRTM"
    },
    "carrier_code": {
      "type": "string",
      "description": "Optional SCAC to scope the watch to one carrier"
    },
    "alert_blank": {
      "type": "boolean",
      "description": "Alert on suspected blank sailings (default true)"
    },
    "alert_cutoff": {
      "type": "boolean",
      "description": "Alert when a booking cut-off is closing (default true)"
    },
    "alert_slip": {
      "type": "boolean",
      "description": "Alert when a sailing slips vs schedule (default true)"
    },
    "cutoff_lead_hours": {
      "type": "number",
      "description": "Hours before cut-off to alert (default 48)"
    }
  },
  "required": [
    "origin",
    "destination"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

port_reliability

Congestion and dwell signals for a port (UN/LOCODE) — average wait and vessels at anchor.

Parameters1

port

string

required

Port UN/LOCODE, e.g. NLRTM

Raw schema

{
  "type": "object",
  "properties": {
    "port": {
      "type": "string",
      "description": "Port UN/LOCODE, e.g. NLRTM"
    }
  },
  "required": [
    "port"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

carrier_league

Carrier league table — ocean carriers ranked by overall on-time reliability across all tracked lanes.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}

port_congestion

Fused port-congestion signal for a port (UN/LOCODE): effective level (mild/moderate/severe), expected added wait in days (for ETA-band widening), a 0–1 confidence, and per-source detail — weiyun broad-AIS analysis + IMF PortWatch throughput + our own AIS wait/density.

Parameters1

port

string

required

Port UN/LOCODE, e.g. NLRTM

Raw schema

{
  "type": "object",
  "properties": {
    "port": {
      "type": "string",
      "description": "Port UN/LOCODE, e.g. NLRTM"
    }
  },
  "required": [
    "port"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

active_cyclones

Live tropical cyclones (typhoons/hurricanes) currently active on ocean trade lanes — name, basin, category, center position, max wind, pressure and movement, from CMA (NW-Pacific) + NHC (Atlantic/E-Pacific) + JTWC (Indian/Southern Hemisphere) + GDACS (global). Use this to see which storms are at sea right now.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}

lane_storm_exposure

Whether an origin→destination ocean lane currently passes through an active cyclone's forecast gale field (a "storm-exposed" sailing at risk of weather delay). Omit ports to list every exposed lane.

Parameters2

origin	string	optional	Origin port UN/LOCODE, e.g. CNSHA
destination	string	optional	Destination port UN/LOCODE, e.g. USLAX

Raw schema

{
  "type": "object",
  "properties": {
    "origin": {
      "type": "string",
      "description": "Origin port UN/LOCODE, e.g. CNSHA"
    },
    "destination": {
      "type": "string",
      "description": "Destination port UN/LOCODE, e.g. USLAX"
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

README.md4 KBView on GitHub

Sailing Schedule MCP Server

Compare ocean sailing schedules, transit times, and carrier on-time reliability across 60+ carriers from Claude, Cursor, or any MCP client.

SchedulesMCP is an ocean-freight sailing-schedule MCP server that lets an AI assistant find sailings and rank shipping lines before you book. It covers 60+ carriers, 72,000+ forward sailings, and 5,000+ point-to-point lanes across 255 ports. Carrier reliability is derived from observed actual-vs-scheduled arrivals across 4,200+ scored ocean port calls — not carrier promises. It runs as a hosted remote server, so there is nothing to self-host.

Ask your AI: "Compare Shanghai→Rotterdam carriers by reliability" or "What's the median transit time for Maersk on CNSHA→USLAX?"

Coverage

60+ ocean carriers ranked head-to-head on any lane (Maersk, MSC, CMA CGM, COSCO, Hapag-Lloyd, ONE, Evergreen, HMM, Yang Ming, ZIM, and more)
72,000+ forward sailings — observed and derived upcoming departures
5,000+ point-to-point lanes across 255 ports (UN/LOCODE)
On-time reliability scored from 4,200+ observed actual-vs-scheduled port calls, with median / p90 transit-time distributions

Sister product to TrackingMCP (ocean container tracking) and LoadingMCP (container load planning).

Tools

Tool	What it does
`compare_lanes`	Rank carriers serving an origin→destination port pair by on-time reliability and transit time. Use this to decide which line to book.
`carrier_reliability`	On-time performance and delay distribution for a specific carrier (by SCAC), optionally on a given lane.
`transit_time`	Observed transit-time distribution (median / p90, in days) for a carrier on an origin→destination lane.
`find_sailings`	Observed and derived upcoming departures on an origin→destination lane, with carrier and frequency.
`port_reliability`	Congestion and dwell signals for a port (UN/LOCODE): average wait and vessels at anchor.

Quick connect

The server is hosted at https://mcp.schedulesmcp.com/mcp. Try it with zero signup using the public demo key smcp_demo_public (synthetic demo data; try lanes CNSHA→NLRTM or CNSHA→USLAX).

Claude Desktop

json

{
  "mcpServers": {
    "ocean-schedules": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.schedulesmcp.com/mcp",
               "--header", "Authorization: Bearer smcp_demo_public"]
    }
  }
}

Cursor / Windsurf / VS Code (native HTTP MCP)

json

{
  "mcpServers": {
    "ocean-schedules": {
      "url": "https://mcp.schedulesmcp.com/mcp",
      "headers": { "Authorization": "Bearer smcp_demo_public" }
    }
  }
}

Replace smcp_demo_public with a key from your dashboard for full coverage. Don't add "type": "streamable-http" — Claude Desktop rejects unknown config fields; Cursor/Windsurf infer transport from url. Registry ID: io.github.lxxmng/ocean-schedules.

Example prompts

"Compare Shanghai→Rotterdam carriers by reliability."
"Which line is most on-time from CNSHA to USLAX?"
"What's Maersk's on-time performance on the transpacific?"
"Give me the median and p90 transit time for CMA CGM from Ningbo to Los Angeles."
"Show upcoming sailings from Shanghai to Rotterdam."
"How congested is the port of Rotterdam right now?"

Endpoint

Remote: https://mcp.schedulesmcp.com/mcp
Health: https://mcp.schedulesmcp.com/health

License

MIT

Install

Tools (12)

compare_lanescarrier_reliabilitytransit_timefind_sailingsget_schedulesfind_best_sailingswatch_laneport_reliability

Remote endpoint

Streamable HTTP

Hosted server - connect over the network, no local install.

url

https://mcp.schedulesmcp.com/mcp

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "ocean-schedules": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.schedulesmcp.com/mcp"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.

io.github.lxxmng/ocean-schedules

io.github.lxxmng/ocean-schedules — MCP Server

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

compare_lanes

carrier_reliability

transit_time

find_sailings

get_schedules

find_best_sailings

watch_lane

port_reliability

carrier_league

port_congestion

active_cyclones

lane_storm_exposure

Sailing Schedule MCP Server

Coverage

Tools

Quick connect

Claude Desktop

Cursor / Windsurf / VS Code (native HTTP MCP)

Example prompts

Endpoint

Links

License

Install

Remote endpoint

Related servers