ocean-schedules MCP server
io.github.lxxmng/ocean-scheduleslxxmngstreamable-httpv0.4.0Scanned
Compare ocean carrier schedules, transit times and reliability: 60+ carriers, 72,000+ sailings.
9 tools: 6 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
6 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the ocean-schedules MCP server can do
The ocean-schedules MCP server is published by the GitHub account lxxmng. It has 9 tools. It can create or change data (6 tools: carrier_reliability, watch_lane, carrier_league, port_congestion and 2 more), but cannot delete data. 3 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 8, 2026, version 0.4.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
9 tools
Changes things 6Claude Code: ask
active_cyclonesLive tropical cyclones (typhoons/hurricanes) currently active on ocean trade lanes — name, basin, category, center position, max wind, pressure and movement, from CMA (NW-Pacific) …No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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_leagueCarrier league table: ocean carriers ranked by overall on-time reliability across all tracked lanes.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
carrier_reliabilityOn-time performance and delay distribution for a specific carrier (by SCAC).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
lane_storm_exposureWhether an origin→destination ocean lane currently passes through an active cyclone's forecast gale field (a "storm-exposed" sailing at risk of weather delay).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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_congestionFused 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 independ…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
watch_laneWatch 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Only reads 3Show 3 read-only tools
compare_lanesCompare ocean carriers serving an origin→destination port pair, ranked by on-time reliability and transit time.No findings
Why it is in this group
- The name "compare_lanes" says "compare": a word for reading.
Description, as the server wrote it 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.
find_best_sailingsDecision query: the best upcoming sailings on a lane, ONE per carrier (next bookable departure), ranked.No findings
Why it is in this group
- The name "find_best_sailings" says "find": a word for reading.
Description, as the server wrote it 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.
get_schedulesPublished 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…No findings
Why it is in this group
- The name "get_schedules" says "get": a word for reading.
Description, as the server wrote it 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.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:07 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.schedulesmcp.com/mcp: tools/list returned 7 tools to an anonymous client, including carrier_reliability (write), watch_lane (write), carrier_league (write), port_congestion (write)
Posture changes
- Nov 13, 2026
- Tools that change things, listed without credentials: 6 to 4
- Oct 29, 2026
- Tools that change things, listed without credentials: 8 to 6
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 6 -> 4.View diff
- Tools that change things, listed without credentials: 6 to 4
Tools3 removed, 1 changed.−3 removed~1 changedView diff
- Removed:find_sailings
- Removed:port_reliability
- Removed:transit_time
- Changed:carrier_reliabilityChanges thingsdescription
PostureRemote posture changed. Tools that change things, listed without credentials: 8 -> 6.View diff
- Tools that change things, listed without credentials: 8 to 6
Tools7 changed.~7 changedView diff
- Changed:carrier_leagueChanges thingsdescription
- Changed:carrier_reliabilityChanges thingsdescription
- Changed:compare_lanesOnly readsdescription
- Changed:find_best_sailingsOnly readsdescription
- Changed:get_schedulesOnly readsdescription
- Changed:port_congestionChanges thingsdescription
- Changed:watch_laneChanges thingsdescription
Install
Pinned to version 0.4.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http ocean-schedules https://mcp.schedulesmcp.com/mcpclaude mcp add --transport http ocean-schedules https://mcp.schedulesmcp.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__ocean-schedules__compare_lanes",
"mcp__ocean-schedules__get_schedules",
"mcp__ocean-schedules__find_best_sailings"
],
"ask": [
"mcp__ocean-schedules__carrier_reliability",
"mcp__ocean-schedules__watch_lane",
"mcp__ocean-schedules__carrier_league",
"mcp__ocean-schedules__port_congestion",
"mcp__ocean-schedules__active_cyclones",
"mcp__ocean-schedules__lane_storm_exposure"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ocean-schedules. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.lxxmng/ocean-schedules/verify?hash=d7d99b833a753eacc3a52042ec29234757fb09a1f89df9dc8dfe4796bca93bad" | jq -e '.changed == false'Pinned hash d7d99b833a75, from Nov 8, 2026, 21:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.lxxmng/ocean-schedules/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.lxxmng/ocean-schedules)Source: MCP Registry · repository. Synced Oct 23, 2026, 16:25 UTC.
ocean-schedules MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the ocean-schedules MCP server safe?
- No scan can promise that. What its definitions show: 9 tools, 6 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the ocean-schedules MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the ocean-schedules MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the ocean-schedules MCP server have?
- 9 tools: 6 write, 3 read. carrier_reliability, watch_lane, carrier_league, port_congestion, active_cyclones, lane_storm_exposure, compare_lanes, get_schedules and 1 more.
Does the ocean-schedules MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the ocean-schedules MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the ocean-schedules MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 8, 2026. Every change is on this page and in its Atom feed.