io.github.lxxmng/ocean-schedules

REMOTE · MCP.SCHEDULESMCP.COM · SCANNED AUG 3

Compare ocean carrier sailing schedules, transit times, and on-time reliability before you book.

Available components

+2 this week 63 63 Trust /100

Trust breakdown (6 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 →

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 not yet verified: we couldn't determine whether a plaintext access path exists. 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 Usability77

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 Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

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

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.schedulesmcp.com

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http lxxmng-ocean-schedules https://mcp.schedulesmcp.com/mcp

# ~/.codex/config.toml

[mcp_servers.lxxmng-ocean-schedules]
url = "https://mcp.schedulesmcp.com/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lxxmng-ocean-schedules": {
      "type": "remote",
      "url": "https://mcp.schedulesmcp.com/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add lxxmng-ocean-schedules --url https://mcp.schedulesmcp.com/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  lxxmng-ocean-schedules:
    url: "https://mcp.schedulesmcp.com/mcp"

// mcp.json

{
  "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.

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.

3 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
1 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
31 Jul 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
29 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
28 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
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
26 Jul 26 61

First indexed and scored.

Show 6 earlier entries Hide earlier entries

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 3 Aug 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	13 Jun 2026	11 Sept 2026	ECDSA 256	ECDSA-SHA384	5dd8817bd2703cbcd6119cb5d7b73564753
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

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

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 — 12 exposed · ~1,118 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.

Tool Tokens

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 Output Examples

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 Output Examples

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.

Input Output Examples

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.

Input Output Examples

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?".

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	61
27 Jul	61
28 Jul	62
29 Jul	63
30 Jul	63
31 Jul	61
1 Aug	62
2 Aug	62
3 Aug	63