Every change Wellknown observed on this MCP server, newest first, with what it was before and what it became. Tool-surface changes carry the definition diff. Nothing here is edited after the fact.
Removed "find_sailings", "port_reliability" and "transit_time"; changed the definition of "carrier_reliability" (12 tools before, 9 now)
On-time performance and delay distribution for a specific carrier (by SCAC), optionally on a given lane.. With Navo Tokens this costs 10 tokens per ⟨6 unchanged words⟩
Observed and derived upcoming departures on an origin→destination lane, with carrier and frequency.
Congestion and dwell signals for a port (UN/LOCODE) — average wait and vessels at anchor.
Observed transit-time distribution (median / p90, in days) for a carrier on an origin→destination lane.
Changed the definition of "carrier_league", "carrier_reliability", "compare_lanes" and 4 more
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.
⟨9 unchanged words⟩ (by SCAC), optionally on a given lane. With Navo Tokens this costs 10 tokens per call; an empty answer is free.
Changed the definition of "find_best_sailings", "get_schedules" and "port_congestion"
⟨32 unchanged words⟩ 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.
{"$schema":"http://json-schema.org/draft-07/schema#","additionalProperties":false,"properties":{"cutoff_opencutoff":{"const":"open","description":"Only sailings whose booking cut-off has notpassedpassed. Sailings where no cut-off is held are kept by default; each option carries cutoff_status saying which case it is.","type":"booleanstring"},"destination
Certificate changed, valid to 2027-01-09
Certificate recorded, valid to 2026-11-10
Authorization not required
First tool surface recorded: 12 tools (server version 1.0.0)
Showing the latest 7 events. The API returns up to 500 and filters by kind: ?kind=tool_surface_changed
⟨15 unchanged words⟩ Use this to decide which line to book. With Navo Tokens this costs 10 tokens per call; an empty answer is free.
⟨59 unchanged words⟩ 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.
⟨206 unchanged words⟩ 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.
⟨19 unchanged words⟩ 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.
⟨28 unchanged words⟩ alerts on reliability drops. Returns the created watch. Free with Navo Tokens: a watch is configuration, not data.
⟨6 unchanged words⟩ origin→destination lane: carrier, vessel, voyage, ETD/ETA, cut-offs andcut-offsrouting (leg count,soonesttransshipmentfirst.ports,Sourceddistance,fromCO2carrierperconnectorsTEU(andaggregatorthecoverageport-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.
⟨11 unchanged words⟩ e.g. NLRTM","type":"string"},"from":{"description":"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 today.","type":"string"},"origin":{"description":"Origin port UN/LOCODE, ⟨9 unchanged words⟩
⟨16 unchanged words⟩ ETA-band widening), a 0–1 confidence, andper-sourcethedetailindependent—readingsweiyunbehindbroad-AISitanalysis—+measuredIMFvesselPortWatchwaitingthroughputtimes,+port-callourthroughputownand AIS wait/density.