io.github.lxxmng/ocean-schedules
REMOTE · MCP.SCHEDULESMCP.COM · SCANNED SEP 26
Compare ocean carrier sailing schedules, transit times, and on-time reliability before you book.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1118 tokens (~93/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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
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
claude mcp add --transport http lxxmng-ocean-schedules 'https://mcp.schedulesmcp.com/mcp'
{
"mcpServers": {
"lxxmng-ocean-schedules": {
"url": "https://mcp.schedulesmcp.com/mcp"
}
}
} {
"servers": {
"lxxmng-ocean-schedules": {
"type": "http",
"url": "https://mcp.schedulesmcp.com/mcp"
}
}
} [mcp_servers.lxxmng-ocean-schedules] url = "https://mcp.schedulesmcp.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"lxxmng-ocean-schedules": {
"type": "remote",
"url": "https://mcp.schedulesmcp.com/mcp",
"enabled": true
}
}
} openclaw mcp add lxxmng-ocean-schedules --url 'https://mcp.schedulesmcp.com/mcp' --transport streamable-http
mcp_servers:
lxxmng-ocean-schedules:
url: "https://mcp.schedulesmcp.com/mcp" {
"McpServers": {
"lxxmng-ocean-schedules": {
"Transport": "http",
"Url": "https://mcp.schedulesmcp.com/mcp"
}
}
} assistant mcp add lxxmng-ocean-schedules -t streamable-http -u 'https://mcp.schedulesmcp.com/mcp'
{
"mcpServers": {
"lxxmng-ocean-schedules": {
"type": "http",
"url": "https://mcp.schedulesmcp.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 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
- 5 Aug 26 0
- HSTS header: unverified → fail ▼ security
- TLS certificate: unverified → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Schema quality: unverified → fail ▼ functional
- Schema quality: unverified → excellent ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → pass ▲ functional
- Stability: fail → 0.33 functional
- New tool “active_cyclones” functional
- New tool “carrier_league” functional
- New tool “carrier_reliability” functional
- New tool “compare_lanes” functional
- New tool “find_best_sailings” functional
- New tool “find_sailings” functional
- New tool “get_schedules” functional
- New tool “lane_storm_exposure” functional
- New tool “port_congestion” functional
- New tool “port_reliability” functional
- New tool “transit_time” functional
- New tool “watch_lane” functional
- 4 Aug 26 0
- HSTS header: fail → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Stability: 0.27 → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “active_cyclones” was removed ▼ security
- Tool “carrier_league” was removed ▼ security
- Tool “carrier_reliability” was removed ▼ security
- Tool “compare_lanes” was removed ▼ security
- Tool “find_best_sailings” was removed ▼ security
- Tool “find_sailings” was removed ▼ security
- Tool “get_schedules” was removed ▼ security
- Tool “lane_storm_exposure” was removed ▼ security
- Tool “port_congestion” was removed ▼ security
- Tool “port_reliability” was removed ▼ security
- Tool “transit_time” was removed ▼ security
- Tool “watch_lane” was removed ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Schema quality: excellent → unverified ▼ functional
- Schema quality: fail → unverified ▼ functional
- Schema quality: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Jul 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
- 27 Jul 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
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 26 Sept 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 | 12 Aug 2026 | 10 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 60f91407fcd9511c68f86fc222f4cd80ec5 |
| 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. | present | 19718 | 13 | Verified |
| schedulesmcp.com. | absent | 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 |
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 →
active_cyclones ~86
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
carrier_league ~26
Carrier league table — ocean carriers ranked by overall on-time reliability across all tracked lanes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
carrier_reliability ~48
On-time performance and delay distribution for a specific carrier (by SCAC), optionally on a given lane.
| Name | Type | Req | Description |
|---|---|---|---|
| carrier_code | string | yes | Carrier SCAC, e.g. MAEU |
No output schema declared.
No examples provided.
compare_lanes ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | Destination port UN/LOCODE, e.g. NLRTM |
| origin | string | yes | Origin port UN/LOCODE, e.g. CNSHA |
No output schema declared.
No examples provided.
find_best_sailings ~233
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?".
| Name | Type | Req | Description |
|---|---|---|---|
| cutoff_open | boolean | – | Only sailings whose booking cut-off has not passed |
| destination | string | yes | Destination port UN/LOCODE, e.g. NLRTM |
| direct_only | boolean | – | Exclude transshipment routings |
| from | string | – | Earliest departure date YYYY-MM-DD (default: today) |
| max_transit_days | number | – | Maximum transit time in days |
| origin | string | yes | Origin port UN/LOCODE or name resolves upstream, e.g. CNSHA |
| reliability_floor | number | – | Minimum 90-day on-time %, 0-100 |
| sort | string | – | Ranking (default recommended = reliability blended with transit) |
| to | string | – | Latest departure date YYYY-MM-DD (default: +60 days) |
No output schema declared.
No examples provided.
find_sailings ~54
Observed and derived upcoming departures on an origin→destination lane, with carrier and frequency.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | Destination port UN/LOCODE |
| origin | string | yes | Origin port UN/LOCODE |
No output schema declared.
No examples provided.
get_schedules ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | Destination port UN/LOCODE, e.g. NLRTM |
| origin | string | yes | Origin port UN/LOCODE, e.g. CNSHA |
No output schema declared.
No examples provided.
lane_storm_exposure ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | – | Destination port UN/LOCODE, e.g. USLAX |
| origin | string | – | Origin port UN/LOCODE, e.g. CNSHA |
No output schema declared.
No examples provided.
port_congestion ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| port | string | yes | Port UN/LOCODE, e.g. NLRTM |
No output schema declared.
No examples provided.
port_reliability ~51
Congestion and dwell signals for a port (UN/LOCODE) — average wait and vessels at anchor.
| Name | Type | Req | Description |
|---|---|---|---|
| port | string | yes | Port UN/LOCODE, e.g. NLRTM |
No output schema declared.
No examples provided.
transit_time ~72
Observed transit-time distribution (median / p90, in days) for a carrier on an origin→destination lane.
| Name | Type | Req | Description |
|---|---|---|---|
| carrier_code | string | – | Optional carrier SCAC to filter |
| destination | string | yes | Destination port UN/LOCODE |
| origin | string | yes | Origin port UN/LOCODE |
No output schema declared.
No examples provided.
watch_lane ~187
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.
| Name | Type | Req | Description |
|---|---|---|---|
| alert_blank | boolean | – | Alert on suspected blank sailings (default true) |
| alert_cutoff | boolean | – | Alert when a booking cut-off is closing (default true) |
| alert_slip | boolean | – | Alert when a sailing slips vs schedule (default true) |
| carrier_code | string | – | Optional SCAC to scope the watch to one carrier |
| cutoff_lead_hours | number | – | Hours before cut-off to alert (default 48) |
| destination | string | yes | Destination port UN/LOCODE, e.g. NLRTM |
| origin | string | yes | Origin port UN/LOCODE, e.g. CNNGB |
No output schema declared.
No examples provided.
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 sailing schedules, transit times, and on-time reliability before you book. 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 74 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 12 tools: compare_lanes, carrier_reliability, transit_time, find_sailings, get_schedules, and 7 more. Their descriptions and schemas cost roughly 1,118 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 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.