mcp server
ocean-schedules
Compare ocean carrier sailing schedules, transit times, and on-time reliability before you book.
Description as published by the maintainer. Source
- version 0.2.0
- active
active — Registry entry last updated 2026-07-04.
What this server can do
12 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
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.
carrier_league- Carrier league table — ocean carriers ranked by overall on-time reliability across all tracked lanes.
carrier_reliability(carrier_code)- On-time performance and delay distribution for a specific carrier (by SCAC), optionally on a given lane. Required: carrier_code.
compare_lanes(origin, destination)- 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. Required: origin, destination.
find_best_sailings(to, from, sort, origin, cutoff_open, destination, direct_only, max_transit_days, reliability_floor)- 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?". Required: origin, destination.
find_sailings(origin, destination)- Observed and derived upcoming departures on an origin→destination lane, with carrier and frequency. Required: origin, destination.
get_schedules(origin, destination)- 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. Required: origin, destination.
lane_storm_exposure(origin, destination)- 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.
port_congestion(port)- 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. Required: port.
port_reliability(port)- Congestion and dwell signals for a port (UN/LOCODE) — average wait and vessels at anchor. Required: port.
transit_time(origin, destination, carrier_code)- Observed transit-time distribution (median / p90, in days) for a carrier on an origin→destination lane. Required: origin, destination.
watch_lane(origin, alert_slip, alert_blank, destination, alert_cutoff, carrier_code, cutoff_lead_hours)- 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. Required: origin, destination.
Last successful function declaration observed on . Source: https://mcp.schedulesmcp.com/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://mcp.schedulesmcp.com/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 0.2.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-04 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-04 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 12 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | mcp.schedulesmcp.com | |
| mcp endpoint status | ok | The server listed 12 functions when asked. | as of probe | mcp.schedulesmcp.com |
Where to get it
Also from lxxmng
-
io.github.lxxmng/container-loading
Plan optimal container & truck loads: 3D layouts, utilization, centre of gravity, crush checks.
-
Container Tracking MCP
DCSA container tracking across 228 ocean carriers: live vessel positions, ETAs, demurrage alerts.
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json