# io.github.lxxmng/ocean-schedules (remote · mcp.schedulesmcp.com)

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

- Trust score: 63/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.schedulesmcp.com`: 63/100 (this document), [markdown](https://verifymcp.io/servers/lxxmng-ocean-schedules/mcp.md), [page](https://verifymcp.io/servers/lxxmng-ocean-schedules/mcp)

## Channel facts

- Endpoint: `https://mcp.schedulesmcp.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1118 tokens (~93/item across 12 items; 12 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```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
    }
  }
}
```

### OpenClaw

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

### Hermes

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

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 63, +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.

### 2026-08-01 (score 62, +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.

### 2026-07-31 (score 61, −2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 63, +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.

### 2026-07-28 (score 62, +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.

### 2026-07-27 (score 61, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 61)

First indexed and scored.

## MCP tools (12)

### `compare_lanes` (~77 tokens)

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 parameters:

- `destination` (string, required): Destination port UN/LOCODE, e.g. NLRTM
- `origin` (string, required): Origin port UN/LOCODE, e.g. CNSHA

### `carrier_reliability` (~48 tokens)

On-time performance and delay distribution for a specific carrier (by SCAC), optionally on a given lane.

Input parameters:

- `carrier_code` (string, required): Carrier SCAC, e.g. MAEU

### `transit_time` (~72 tokens)

Observed transit-time distribution (median / p90, in days) for a carrier on an origin→destination lane.

Input parameters:

- `carrier_code` (string): Optional carrier SCAC to filter
- `destination` (string, required): Destination port UN/LOCODE
- `origin` (string, required): Origin port UN/LOCODE

### `find_sailings` (~54 tokens)

Observed and derived upcoming departures on an origin→destination lane, with carrier and frequency.

Input parameters:

- `destination` (string, required): Destination port UN/LOCODE
- `origin` (string, required): Origin port UN/LOCODE

### `get_schedules` (~97 tokens)

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 parameters:

- `destination` (string, required): Destination port UN/LOCODE, e.g. NLRTM
- `origin` (string, required): Origin port UN/LOCODE, e.g. CNSHA

### `find_best_sailings` (~233 tokens)

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 parameters:

- `cutoff_open` (boolean): Only sailings whose booking cut-off has not passed
- `destination` (string, required): 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, required): 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)

### `watch_lane` (~187 tokens)

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 parameters:

- `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, required): Destination port UN/LOCODE, e.g. NLRTM
- `origin` (string, required): Origin port UN/LOCODE, e.g. CNNGB

### `port_reliability` (~51 tokens)

Congestion and dwell signals for a port (UN/LOCODE) — average wait and vessels at anchor.

Input parameters:

- `port` (string, required): Port UN/LOCODE, e.g. NLRTM

### `carrier_league` (~26 tokens)

Carrier league table — ocean carriers ranked by overall on-time reliability across all tracked lanes.

### `port_congestion` (~97 tokens)

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 parameters:

- `port` (string, required): Port UN/LOCODE, e.g. NLRTM

### `active_cyclones` (~86 tokens)

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.

### `lane_storm_exposure` (~90 tokens)

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 parameters:

- `destination` (string): Destination port UN/LOCODE, e.g. USLAX
- `origin` (string): Origin port UN/LOCODE, e.g. CNSHA

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/lxxmng-ocean-schedules/mcp#diagnostics

## Score history

- 2026-08-03: 63
- 2026-08-02: 62
- 2026-08-01: 62
- 2026-07-31: 61
- 2026-07-30: 63
- 2026-07-29: 63
- 2026-07-28: 62
- 2026-07-27: 61
- 2026-07-26: 61

## Links

- Remote endpoint: https://mcp.schedulesmcp.com/mcp
- Repository: https://github.com/lxxmng/schedulesmcp
- Changelog RSS feed: https://verifymcp.io/servers/lxxmng-ocean-schedules/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/lxxmng-ocean-schedules/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/lxxmng-ocean-schedules/mcp