Kuaidi100 launched China's first MCP-protocol-compatible logistics information service platform. The core API services of Kuaidi100's Baidiy
Nothing to run from here
Ocean Schedules is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
12
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Compare ocean carrier schedules, transit times and reliability: 60+ carriers, 72,000+ sailings.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http ocean-schedules-mcp https://mcp.schedulesmcp.com/mcp
# 2 — ask your agent for something these tools do
# compare_lanes, carrier_reliability, transit_time and 9 more
Ocean Schedules costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
LXAll 4 servers
lxxmng4 servers
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http ocean-schedules-mcp https://mcp.schedulesmcp.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
12 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| origin | string | yes | Origin port UN/LOCODE, e.g. CNSHA |
| destination | string | yes | Destination port UN/LOCODE, e.g. NLRTM |
On-time performance and delay distribution for a specific carrier (by SCAC), optionally on a given lane.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| carrier_code | string | yes | Carrier SCAC, e.g. MAEU |
Observed transit-time distribution (median / p90, in days) for a carrier on an origin→destination lane.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| origin | string | yes | Origin port UN/LOCODE |
| destination | string | yes | Destination port UN/LOCODE |
| carrier_code | string | no | Optional carrier SCAC to filter |
Observed and derived upcoming departures on an origin→destination lane, with carrier and frequency.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| origin | string | yes | Origin port UN/LOCODE |
| destination | string | yes | Destination port UN/LOCODE |
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 ti
| Parameter | Type | Required | Notes |
|---|---|---|---|
| origin | string | yes | Origin port UN/LOCODE, e.g. CNSHA |
| destination | string | yes | Destination port UN/LOCODE, e.g. NLRTM |
| from | string | no | Earliest departure date as YYYY-MM-DD, with no time and no timezone offset. Must be today or later. Sailings are returned from 00:00 of that date, read in each port's local time, onward. Omit for toda |
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 co
| Parameter | Type | Required | Notes |
|---|---|---|---|
| origin | string | yes | Origin port UN/LOCODE or name resolves upstream, e.g. CNSHA |
| destination | string | yes | Destination port UN/LOCODE, e.g. NLRTM |
| from | string | no | Earliest departure date YYYY-MM-DD (default: today) |
| to | string | no | Latest departure date YYYY-MM-DD (default: +60 days) |
| max_transit_days | number | no | Maximum transit time in days |
| reliability_floor | number | no | Minimum 90-day on-time %, 0-100 |
| cutoff | string | no | 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. |
| cutoff_include_unknown | boolean | no | Default true. false narrows to sailings where a deadline is actually held and still ahead. |
| transshipment | boolean | no | 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 d |
| sort | string | no | Ranking (default recommended = reliability blended with transit) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| origin | string | yes | Origin port UN/LOCODE, e.g. CNNGB |
| destination | string | yes | Destination port UN/LOCODE, e.g. NLRTM |
| carrier_code | string | no | Optional SCAC to scope the watch to one carrier |
| alert_blank | boolean | no | Alert on suspected blank sailings (default true) |
| alert_cutoff | boolean | no | Alert when a booking cut-off is closing (default true) |
| alert_slip | boolean | no | Alert when a sailing slips vs schedule (default true) |
| cutoff_lead_hours | number | no | Hours before cut-off to alert (default 48) |
Congestion and dwell signals for a port (UN/LOCODE) — average wait and vessels at anchor.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| port | string | yes | Port UN/LOCODE, e.g. NLRTM |
Carrier league table — ocean carriers ranked by overall on-time reliability across all tracked lanes.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| port | string | yes | Port UN/LOCODE, e.g. NLRTM |
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| origin | string | no | Origin port UN/LOCODE, e.g. CNSHA |
| destination | string | no | Destination port UN/LOCODE, e.g. USLAX |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Ocean Schedules or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.3.0.
0.3.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Ocean Schedules can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.