# io.github.lxxmng/ocean-schedules > Compare ocean carrier schedules, transit times and reliability: 60+ carriers, 72,000+ sailings. - name: io.github.lxxmng/ocean-schedules - version: 0.3.0 - connection class: R0 (autonomous) - trust: 94/100 - quality: 65/100 (needs work) - owner: not claimed - descriptor: https://api.protogrid.dev/v1/servers/io.github.lxxmng%2Focean-schedules - tools: https://api.protogrid.dev/v1/servers/io.github.lxxmng%2Focean-schedules/tools **An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe. ## Connection (mcpServers) ```json { "mcpServers": { "ocean-schedules": { "type": "http", "url": "https://mcp.schedulesmcp.com/mcp" } } } ``` ## Trust - hygiene: 100 - liveness: 100 - freshness: 100 - provenance: 80 - drivers: +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. ## Quality 65/100 (needs work) ### protocol: 75 (weight 25) - warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28 - n/a `protocol.stateless`: only applies to 2026-07-28 servers - pass `protocol.transport`: streamable HTTP - n/a `protocol.list_ttl`: only applies to 2026-07-28 servers ### authorization: n/a (weight 15) - n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth - n/a `auth.secret_in_url`: no templated URL ### tool hygiene: 64 (weight 30) - pass `tools.descriptions`: every tool has a description - warn `tools.description_length`: 1 tools have descriptions over 1,024 characters, which crowds the context - pass `tools.schemas`: every tool has an object input schema - fail `tools.annotations`: no tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones - fail `tools.directory_hints`: no 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_cost`: about 2,131 tokens to load every tool - pass `tools.api_dump`: tools are not a one-to-one API dump ### stability: 50 (weight 15) - pass `stability.changes`: 3 tool changes in 30 days - fail `stability.rug_pull`: 1 tools kept their name but changed most of their description in 30 days; review before trusting them ### dependencies: n/a (weight 15) - n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package - tools: 12, about 2,131 tokens to load them all - tool set hash: 0bebaddcda53681c451e8fe0720a5f08 - tools last changed: 2026-10-12T18:48:08.217Z - badge: [![protogrid quality](https://protogrid.dev/badge/io.github.lxxmng/ocean-schedules.svg)](https://protogrid.dev/servers/io.github.lxxmng/ocean-schedules) - Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. ### Tool changes - 2026-10-12 `port_congestion` changed (description) - 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: 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-12 `find_best_sailings` changed (description, inputSchema) - 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: 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-12 `get_schedules` changed (description, inputSchema) **meaning 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: 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: https://api.protogrid.dev/v1/servers/io.github.lxxmng%2Focean-schedules/changes ## Remotes - https://mcp.schedulesmcp.com/mcp (streamable-http, auth none, reachable true, uptime30d 1) ## Packages _none_ ## 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.