mcp-registry/io.github.lxxmng/ocean-schedules · v1.0.0
As of 2026-10-21 09:03 UTC, the Lxxmng Ocean Schedules MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 7 minutes.
Compare ocean carrier sailing schedules, transit times, and on-time reliability before you book.
Claude Code
claude mcp add --transport http lxxmng-ocean-schedules-mcp-server https://mcp.schedulesmcp.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"lxxmng-ocean-schedules-mcp-server": {
"type": "http",
"url": "https://mcp.schedulesmcp.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
12 of 12 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Handshake + tools/list takes ~1,951 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
In the last 30 days: 0 tool(s) removed and 2 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.lxxmng%2Focean-schedules/fixes
{
"name": "compare_lanes",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"origin",
"destination"
],
"properties": {
"origin": {
"type": "string",
"description": "Origin port UN/LOCODE, e.g. CNSHA"
},
"destination": {
"type": "string",
"description": "Destination port UN/LOCODE, e.g. NLRTM"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "find_best_sailings",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"origin",
"destination"
],
"properties": {
"to": {
"type": "string",
"description": "Latest departure date YYYY-MM-DD (default: +60 days)"
},
"from": {
"type": "string",
"description": "Earliest departure date YYYY-MM-DD (default: today)"
},
"sort": {
"enum": [
"recommended",
"reliability",
"fastest",
"soonest"
],
"type": "string",
"description": "Ranking (default recommended = reliability blended with transit)"
},
"cutoff": {
"type": "string",
"const": "open",
"description": "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."
},
"origin": {
"type": "string",
"description": "Origin port UN/LOCODE or name resolves upstream, e.g. CNSHA"
},
"destination": {
"type": "string",
"description": "Destination port UN/LOCODE, e.g. NLRTM"
},
"transshipment": {
"type": "boolean",
"description": "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 direct without evidence."
},
"max_transit_days": {
"type": "number",
"description": "Maximum transit time in days"
},
"reliability_floor": {
"type": "number",
"description": "Minimum 90-day on-time %, 0-100"
},
"cutoff_include_unknown": {
"type": "boolean",
"description": "Default true. false narrows to sailings where a deadline is actually held and still ahead."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "find_sailings",
"description": "Observed and derived upcoming departures on an origin→destination lane, with carrier and frequency.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"origin",
"destination"
],
"properties": {
"origin": {
"type": "string",
"description": "Origin port UN/LOCODE"
},
"destination": {
"type": "string",
"description": "Destination port UN/LOCODE"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.lxxmng/ocean-schedules"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.lxxmng/ocean-schedules"}) over MCP.
find_best_sailings ~556 tokensget_schedules ~310 tokenswatch_lane ~297 tokenslane_storm_exposure ~150 tokensport_congestion ~150 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.lxxmng%2Focean-schedules?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.lxxmng%2Focean-schedules?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.lxxmng%2Focean-schedules.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.lxxmng%2Focean-schedules.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.lxxmng%2Focean-schedules?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:bb200cf2749c80cb…, first seen 2026-10-17, included at leaf 3084 of 38,691. Version history · verify what your client received.
Compare: most reliable data servers · most reliable search servers · most reliable communication servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-21 09:03 UTC, the Lxxmng Ocean Schedules MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 7 minutes.
Lxxmng Ocean Schedules MCP server advertises 12 tools, including active_cyclones, carrier_league, carrier_reliability, compare_lanes, find_best_sailings.
Point your MCP client at this streamable-http endpoint: https://mcp.schedulesmcp.com/mcp
Glimind scanned all 12 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.