Connect

8 clients · secrets stay placeholders

JSON (mcpServers)Claude CodeCodexOpenCodeCursorVS CodeGemini CLIGoose

{
  "mcpServers": {
    "ocean-schedules": {
      "type": "http",
      "url": "https://mcp.schedulesmcp.com/mcp"
    }
  }
}

claude mcp add --transport http ocean-schedules https://mcp.schedulesmcp.com/mcp

[mcp_servers.ocean-schedules]
url = "https://mcp.schedulesmcp.com/mcp"

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ocean-schedules": {
      "type": "remote",
      "url": "https://mcp.schedulesmcp.com/mcp",
      "enabled": true
    }
  }
}

{
  "mcpServers": {
    "ocean-schedules": {
      "type": "http",
      "url": "https://mcp.schedulesmcp.com/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=ocean-schedules&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vbWNwLnNjaGVkdWxlc21jcC5jb20vbWNwIn0%3D"
}

{
  "servers": {
    "ocean-schedules": {
      "type": "http",
      "url": "https://mcp.schedulesmcp.com/mcp"
    }
  }
}

{
  "mcpServers": {
    "ocean-schedules": {
      "httpUrl": "https://mcp.schedulesmcp.com/mcp"
    }
  }
}

extensions:
  "ocean-schedules":
    enabled: true
    name: "ocean-schedules"
    type: streamable_http
    uri: "https://mcp.schedulesmcp.com/mcp"
    timeout: 300

Quality 65 / 100needs work

protocol75 · weight 25

warn
protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
n/a
protocol.statelessonly applies to 2026-07-28 servers
pass
protocol.transportstreamable HTTP
n/a
protocol.list_ttlonly applies to 2026-07-28 servers

authorizationn/a · weight 15

n/a
auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
n/a
auth.secret_in_urlno templated URL

tool hygiene64 · weight 30

pass
tools.descriptionsevery tool has a description
warn
tools.description_length1 tools have descriptions over 1,024 characters, which crowds the context
pass
tools.schemasevery tool has an object input schema
fail
tools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
fail
tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: carrier_league (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); port_congestion (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); lane_storm_exposure (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
pass
tools.token_costabout 2,131 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump

stability50 · weight 15

pass
stability.changes3 tool changes in 30 days
fail
stability.rug_pull1 tools kept their name but changed most of their description in 30 days; review before trusting them

dependenciesn/a · weight 15

n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

12 tools, about 2,131 tokens to load them all · tool set 0bebaddcda53 · tools last changed 2026-10-12 · checked 2026-10-20 16:30 UTC

Tool changes

2026-10-12port_congestionchangeddescription
before
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.
after · 58% of words in common
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 the independent readings behind it — measured vessel waiting times, port-call throughput and AIS wait/density.
2026-10-12find_best_sailingschangeddescription, input schema
before
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?".
after · 62% of words in common
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?". etd, eta, cutoff.at and the from/to window are port-local times with no timezone offset (2026-10-01T13:00:00): quote the digits, do not convert; only retrieved_at is UTC.
2026-10-12get_scheduleschangeddescription, input schemameaning changed
before
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.
after · 20% of words in common
Published forward sailing schedules on an origin→destination lane: carrier, vessel, voyage, ETD/ETA, cut-offs and routing (leg count, transshipment ports, distance, CO2 per TEU and the port-by-port route_legs where the carrier publishes them; null where they do not), soonest first, from each carrier's own published schedules. Use this to find concrete upcoming departures to book. Every schedule time (published_departure, published_arrival, cut-offs, route_legs times, the from window) is the local time of its own port as the line publishes it, written without a timezone offset (2026-10-01T13:00:00): quote the digits and do not convert them; departure_precision/arrival_precision say minute (a time) or day (a date only); only retrieved_at is UTC and carries an offset; use transit_days for voyage length. The answer also carries carriers: one entry per line with carrier_code, carrier_name and count (its sailings in this answer; the counts add up to count), most first. An entry has error only when that line was asked live for this lane in this request and gave no answer: timeout (no answer in time), failed (error or unreachable), or paused (not asked; it timed out twice in a row here, retried after 6 h). A line that answered it has no sailings carries no error, and a line in error is listed even at count 0.

Full history: list_changes · trend: quality JSON.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 94 / 100

provenance80

liveness100

freshness100

hygiene100

+repository +namespace-matches-repo +reachable +uptime-100% +updated-16d-ago

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remote	auth	reachable	uptime 30d	p50	protocol	last ok
`https://mcp.schedulesmcp.com/mcp` streamable-http	none	yes	100%	375 ms	2025-11-25	2026-10-20

Tools (12)

`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`	On-time performance and delay distribution for a specific carrier (by SCAC), optionally on a given lane.
`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.
`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?". etd, eta, cutoff.at and the from/to window are port-local times with no timezone offset (2026-10-01T13:00:00): quote the digits, do not convert; only retrieved_at is UTC.
`find_sailings`	Observed and derived upcoming departures on an origin→destination lane, with carrier and frequency.
`get_schedules`	Published forward sailing schedules on an origin→destination lane: carrier, vessel, voyage, ETD/ETA, cut-offs and routing (leg count, transshipment ports, distance, CO2 per TEU and the port-by-port route_legs where the carrier publishes them; null where they do not), soonest first, from each carrier's own published schedules. Use this to find concrete upcoming departures to book. Every schedule time (published_departure, published_arrival, cut-offs, route_legs times, the from window) is the local time of its own port as the line publishes it, written without a timezone offset (2026-10-01T13:00:00): quote the digits and do not convert them; departure_precision/arrival_precision say minute (a time) or day (a date only); only retrieved_at is UTC and carries an offset; use transit_days for voyage length. The answer also carries carriers: one entry per line with carrier_code, carrier_name and count (its sailings in this answer; the counts add up to count), most first. An entry has error only when that line was asked live for this lane in this request and gave no answer: timeout (no answer in time), failed (error or unreachable), or paused (not asked; it timed out twice in a row here, retried after 6 h). A line that answered it has no sailings carries no error, and a line in error is listed even at count 0.
`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.
`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 the independent readings behind it — measured vessel waiting times, port-call throughput and AIS wait/density.
`port_reliability`	Congestion and dwell signals for a port (UN/LOCODE) — average wait and vessels at anchor.
`transit_time`	Observed transit-time distribution (median / p90, in days) for a carrier on an origin→destination lane.
`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.

Schemas: list_tools.

Similar MCP servers

More from io.github.lxxmng

Official server.json

{
  "name": "io.github.lxxmng/ocean-schedules",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-07-09/server.schema.json",
  "remotes": [
    {
      "url": "https://mcp.schedulesmcp.com/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "0.3.0",
  "repository": {
    "url": "https://github.com/lxxmng/schedulesmcp-mcp",
    "source": "github"
  },
  "description": "Compare ocean carrier schedules, transit times and reliability: 60+ carriers, 72,000+ sailings."
}