Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.lxxmng/ocean-schedules

REMOTE · MCP.SCHEDULESMCP.COM

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

0 this week 66 Trust /100

Last scanned (14 hours ago)

Scores higher than 51% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1376 tokens (~196/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
  • Stability check failed: schema churn in the 30 days we've observed: 5 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (11)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 14 Nov 26 −3
    • A breaking change shipped without a version bump: still 1.0.0 ▼ security
    • Tool “active_cyclones” was removed ▼ security
    • Tool “lane_storm_exposure” was removed ▼ security
    • Schema quality: 172 → 196 ▼ functional
    • “find_best_sailings” reworded the description of “from” cosmetic
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Oct 26 −4
    • Stability: pass → fail ▼ security
    • A breaking change shipped without a version bump: still 1.0.0 ▼ security
    • Tool “find_sailings” was removed ▼ security
    • Tool “port_reliability” was removed ▼ security
    • Tool “transit_time” was removed ▼ security
    • Tool “carrier_reliability” rewrote its description, which is the text the model reads security
    • Schema quality: 144 → 172 ▼ functional
  • 23 Oct 26 73
    • Tool “carrier_league” rewrote its description, which is the text the model reads security
    • Tool “carrier_reliability” rewrote its description, which is the text the model reads security
    • Tool “compare_lanes” rewrote its description, which is the text the model reads security
    • Tool “find_best_sailings” rewrote its description, which is the text the model reads security
    • Tool “get_schedules” rewrote its description, which is the text the model reads security
    • Tool “port_congestion” rewrote its description, which is the text the model reads security
    • Tool “watch_lane” rewrote its description, which is the text the model reads security
    • Schema quality: 130 → 144 ▼ functional
    • Schema quality: good → excellent functional
  • 13 Oct 26 0
    • Tool “find_best_sailings” rewrote its description, which is the text the model reads security
    • Tool “get_schedules” rewrote its description, which is the text the model reads security
    • Tool “port_congestion” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
    • Schema quality: excellent → good functional
    • “find_best_sailings” added an optional parameter “cutoff” cosmetic
    • “find_best_sailings” added an optional parameter “cutoff_include_unknown” cosmetic
    • “find_best_sailings” added an optional parameter “transshipment” cosmetic
    • “get_schedules” added an optional parameter “from” cosmetic
    • “find_best_sailings” dropped the optional parameter “cutoff_open” cosmetic
    • “find_best_sailings” dropped the optional parameter “direct_only” cosmetic
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://mcp.schedulesmcp.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.schedulesmcp.com CN=YE2,O=Let's Encrypt,C=US 11 Oct 2026 9 Jan 2027 ECDSA 256 ECDSA-SHA384 6654635f343cc2335c17e5184bb6d3dde14
SANs: mcp.schedulesmcp.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.schedulesmcp.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
schedulesmcp.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.schedulesmcp.com/mcp Verified 200
http (plaintext) http://mcp.schedulesmcp.com/mcp Inconclusive 406
MCP tools · 7 exposed · ~1,376 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
carrier_league ~44

Carrier league table: ocean carriers ranked by overall on-time reliability across all tracked lanes. With Navo Tokens this costs 10 tokens per call; an empty answer is free.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

carrier_reliability ~60

On-time performance and delay distribution for a specific carrier (by SCAC). With Navo Tokens this costs 10 tokens per call; an empty answer is free.

NameTypeReqDescription
carrier_codestringyesCarrier SCAC, e.g. MAEU

No output schema declared.

No examples provided.

compare_lanes ~95

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. With Navo Tokens this costs 10 tokens per call; an empty answer is free.

NameTypeReqDescription
destinationstringyesDestination port UN/LOCODE, e.g. NLRTM
originstringyesOrigin port UN/LOCODE, e.g. CNSHA

No output schema declared.

No examples provided.

find_best_sailings ~415

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. With Navo Tokens this costs 80 tokens for a new port pair and 10 for a repeat of the same pair within 24 hours (shared with the other lane search); an empty answer is free.

NameTypeReqDescription
cutoffstring–Only sailings whose booking cut-off has not passed. Sailings where no cut-off is held are kept by default; each option carries cutoff_status saying which case it is.
cutoff_include_unknownboolean–Default true. false narrows to sailings where a deadline is actually held and still ahead.
destinationstringyesDestination port UN/LOCODE, e.g. NLRTM
fromstring–Earliest departure date YYYY-MM-DD, today or later (default: today)
max_transit_daysnumber–Maximum transit time in days
originstringyesOrigin port UN/LOCODE or name resolves upstream, e.g. CNSHA
reliability_floornumber–Minimum 90-day on-time %, 0-100
sortstring–Ranking (default recommended = reliability blended with transit)
tostring–Latest departure date YYYY-MM-DD (default: +60 days)
transshipmentboolean–true keeps only sailings that change ship, false only sailings proven direct. Omit it for both: a sailing whose routing we do not hold is returned by neither side, because we will not call a sailing…

No output schema declared.

No examples provided.

get_schedules ~450

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. With Navo Tokens this costs 80 tokens for a new port pair and 10 for a repeat of the same pair within 24 hours (shared with the other lane search); an empty answer is free.

NameTypeReqDescription
destinationstringyesDestination port UN/LOCODE, e.g. NLRTM
fromstring–Earliest departure date as YYYY-MM-DD, with no time and no timezone offset. Must be today or later. Sailings are returned from 00:00 of that date, read in each port's local time, onward. Omit for tod…
originstringyesOrigin port UN/LOCODE, e.g. CNSHA

No output schema declared.

No examples provided.

port_congestion ~111

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. With Navo Tokens this costs 10 tokens per call; an empty answer is free.

NameTypeReqDescription
portstringyesPort UN/LOCODE, e.g. NLRTM

No output schema declared.

No examples provided.

watch_lane ~201

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. Free with Navo Tokens: a watch is configuration, not data.

NameTypeReqDescription
alert_blankboolean–Alert on suspected blank sailings (default true)
alert_cutoffboolean–Alert when a booking cut-off is closing (default true)
alert_slipboolean–Alert when a sailing slips vs schedule (default true)
carrier_codestring–Optional SCAC to scope the watch to one carrier
cutoff_lead_hoursnumber–Hours before cut-off to alert (default 48)
destinationstringyesDestination port UN/LOCODE, e.g. NLRTM
originstringyesOrigin port UN/LOCODE, e.g. CNNGB

No output schema declared.

No examples provided.

Install

How do I install the io.github.lxxmng/ocean-schedules MCP server?

io.github.lxxmng/ocean-schedules is a hosted endpoint at https://mcp.schedulesmcp.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.schedulesmcp.com

# add to Claude Code
claude mcp add --transport http lxxmng-ocean-schedules 'https://mcp.schedulesmcp.com/mcp'
Common questions

What is the io.github.lxxmng/ocean-schedules MCP server?

io.github.lxxmng/ocean-schedules is an MCP server listed in the public MCP registry as io.github.lxxmng/ocean-schedules. Compare ocean carrier schedules, transit times and reliability: 60+ carriers, 72,000+ sailings. This page covers its hosted endpoint (https://mcp.schedulesmcp.com/mcp).

Is the io.github.lxxmng/ocean-schedules MCP server safe to use?

io.github.lxxmng/ocean-schedules scores 66 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.lxxmng/ocean-schedules MCP server expose?

io.github.lxxmng/ocean-schedules exposes 7 tools: compare_lanes, carrier_reliability, get_schedules, find_best_sailings, watch_lane, and 2 more. Their descriptions and schemas cost roughly 1,376 tokens of context every time the server is loaded.

Does the io.github.lxxmng/ocean-schedules MCP server require authentication?

No. We connected to io.github.lxxmng/ocean-schedules without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.lxxmng/ocean-schedules MCP server still maintained?

io.github.lxxmng/ocean-schedules is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.lxxmng/ocean-schedules MCP server?

VerifyMCP ran 11 checks on io.github.lxxmng/ocean-schedules, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about io.github.lxxmng/ocean-schedules: Authorization and HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.