Ocean Schedules

io.github.lxxmng由 GitHub 账号 lxxmng 发布v0.4.0更新于 Oct 24, 2026

Compare ocean carrier schedules, transit times and reliability: 60+ carriers, 72,000+ sailings.

已验证Streamable HTTP可网页运行数据与分析商业与电商

概览

AI 生成的概览

面向海运的托管 MCP 服务器:让助手在订舱前比较船公司船期、运输时效与准班率。

可以做什么
按准班率与运输时效比较某条起运港到目的港航线的船公司,并查看船公司排行榜及按 SCAC 的延误分布(compare_lanes、carrier_league、carrier_reliability)。查询未来船期,含船名、航次、ETD/ETA、截关时间与航线信息(get_schedules)。按日期范围、运输天数、准班率、截关是否仍开放及直达或中转筛选,找出每家船公司最佳可订航次(find_best_sailings)。按 UN/LOCODE 查看港口拥堵等级与预计额外等待时间(port_congestion)。查看当前活跃热带气旋,以及某航线是否穿过风暴预报大风区(active_cyclones、lane_storm_exposure)。
适用场景
适合在规划或比较海运订舱时使用:为某条航线选择订哪家船公司、了解某船公司过往准班表现、查看即将开航的船期与截关时间,或在订舱前评估港口拥堵与风暴风险。
运行要求
远程 MCP 端点,无需自行部署。需在 Authorization 请求头中提供 Bearer 密钥;提供公开演示密钥可试用,但为合成演示数据,完整数据需使用控制台密钥。部分调用会消耗 Navo Tokens。
安装前请注意
多个工具按次计费:使用 Navo Tokens 时 compare_lanes、carrier_reliability、carrier_league 和 port_congestion 每次调用消耗 10 个 token,watch_lane 标注为付费并会发送邮件提醒。需在 Authorization 请求头中提供密钥。演示数据为合成数据,演示密钥返回的并非真实船期。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Ocean Schedules,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.lxxmng%2Focean-schedules/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "ocean-schedules": {
      "type": "http",
      "url": "https://mcp.schedulesmcp.com/mcp"
    }
  }
}

README

Sailing Schedule MCP Server

[npm]

Compare ocean sailing schedules, transit times, and carrier on-time reliability across 60+ carriers from Claude, Cursor, or any MCP client.

SchedulesMCP is an ocean-freight sailing-schedule MCP server that lets an AI assistant find sailings and rank shipping lines before you book. It covers 60+ carriers, 72,000+ forward sailings, and 5,000+ point-to-point lanes across 255 ports. Carrier reliability is derived from observed actual-vs-scheduled arrivals across 4,200+ scored ocean port calls — not carrier promises. It runs as a hosted remote server, so there is nothing to self-host.

Ask your AI: "Compare Shanghai→Rotterdam carriers by reliability" or "What's the median transit time for Maersk on CNSHA→USLAX?"

Coverage

  • 60+ ocean carriers ranked head-to-head on any lane (Maersk, MSC, CMA CGM, COSCO, Hapag-Lloyd, ONE, Evergreen, HMM, Yang Ming, ZIM, and more)
  • 72,000+ forward sailings — observed and derived upcoming departures
  • 5,000+ point-to-point lanes across 255 ports (UN/LOCODE)
  • On-time reliability scored from 4,200+ observed actual-vs-scheduled port calls, with median / p90 transit-time distributions

Sister product to TrackingMCP (ocean container tracking) and LoadingMCP (container load planning).

Tools

ToolWhat it does
compare_lanesRank carriers serving an origin→destination port pair by on-time reliability and transit time. Use this to decide which line to book.
carrier_reliabilityOn-time performance and delay distribution for a specific carrier (by SCAC).

Quick connect

The server is hosted at https://mcp.schedulesmcp.com/mcp. Try it with zero signup using the public demo key smcp_demo_public (synthetic demo data; try lanes CNSHA→NLRTM or CNSHA→USLAX).

Claude Desktop

json
{  "mcpServers": {    "ocean-schedules": {      "command": "npx",      "args": ["-y", "mcp-remote", "https://mcp.schedulesmcp.com/mcp",               "--header", "Authorization: Bearer smcp_demo_public"]    }  }}

Cursor / Windsurf / VS Code (native HTTP MCP)

json
{  "mcpServers": {    "ocean-schedules": {      "url": "https://mcp.schedulesmcp.com/mcp",      "headers": { "Authorization": "Bearer smcp_demo_public" }    }  }}

Replace smcp_demo_public with a key from your dashboard for full coverage. Don't add "type": "streamable-http" — Claude Desktop rejects unknown config fields; Cursor/Windsurf infer transport from url. Registry ID: io.github.lxxmng/ocean-schedules.

Example prompts

  • "Compare Shanghai→Rotterdam carriers by reliability."
  • "Which line is most on-time from CNSHA to USLAX?"
  • "What's Maersk's on-time performance on the transpacific?"
  • "Give me the median and p90 transit time for CMA CGM from Ningbo to Los Angeles."
  • "Show upcoming sailings from Shanghai to Rotterdam."
  • "How congested is the port of Rotterdam right now?"

Endpoint

  • Remote: https://mcp.schedulesmcp.com/mcp
  • Health: https://mcp.schedulesmcp.com/health

Links

License

MIT

来源:README.md,提交 c72aa48

工具

9

compare_lanes

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.

输入参数origin必填destination必填

carrier_reliability

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.

输入参数carrier_code必填

get_schedules

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.

输入参数fromorigin必填destination必填

find_best_sailings

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.

输入参数tofromsortcutofforigin必填destination必填transshipmentmax_transit_daysreliability_floorcutoff_include_unknown

watch_lane

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.

输入参数origin必填alert_slipalert_blankdestination必填alert_cutoffcarrier_codecutoff_lead_hours

carrier_league

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.

无需输入参数。

port_congestion

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.

输入参数port必填

active_cyclones

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

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.

输入参数origindestination

版本历史

3
  1. v0.4.0最新Oct 23, 2026
  2. v0.3.0Oct 5, 2026
  3. v0.2.0Sep 16, 2026

评分

已满足适用检查项的 100%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分