TrackingMCP 
AirCargoMCP 
SchedulesMCP 
LoadingMCP 
FreightRatesMCP Container visibility
Know where every container is, and when it will really arrive.
Container tracking across 233 carriers: 125 direct connectors, 186 SCACs recognised, with ETAs that tell the truth, demurrage and detention free-time, port congestion and vessel positions. One reference in; status, route, milestones and reasons out, delivered over MCP, REST and webhooks.
{ "tool": "get_container_detail",
"ref": "MSCU1234567" }{ "status": "On board vessel",
"vessel": "MSC TERESA",
"eta": "2026-07-03",
"eta_basis": "predicted", // not a stale promise
"demurrage_free_until": "2026-07-10",
"milestone": "Departed CNNGB",
"delay_reason": null }What it does
Built for the decisions you make at the desk.
Direct carrier connectors, normalised to DCSA
We read the carriers themselves and map every event to the DCSA standard, not a screen-scraped guess. A container number, a bill of lading or a booking all resolve to the same clean timeline.
ETAs that tell the truth
Arrival is predicted from the delay we actually observe on the lane and the vessel, never a stale carrier promise. A box that has not sailed does not read "100% complete".
Demurrage & detention free-time
We surface the carrier’s own published free-time and the clock against it, so your team acts before the charges start, not after the invoice lands.
Webhooks the moment we know
HMAC-signed webhooks fire the instant an ETA moves, a box is discharged, or a hold appears. Your systems hear about a delay when we do, not on the next poll.
Port congestion & live vessel positions
Congestion at the port of discharge and the vessel’s position from AIS, so a slipping ETA comes with a reason a customer will accept.
Self-healing coverage
Every carrier has 2–3 independent data paths: an official API, our own connector, a cross-checked network source, all with automatic failover. When a carrier changes something, the connector re-mints its own credentials and re-probes live boxes before a human is ever paged. Quiet is the goal.
Call it as tools
Every capability, as a tool or an endpoint.
The same functions an assistant can call in plain language, your stack can hit over REST, behind one key, with webhooks to push the changes.
add_container Start tracking a container, B/L or booking. get_container_detail Full timeline, route, vessel and ETA basis. get_shipment_summary One-line status fit for a customer reply. get_demurrage_free_time Published free-time and the clock against it. get_demurrage_report Exposure across every box you hold. get_port_congestion Dwell and congestion at a port. get_vessel_position Latest AIS position for a vessel. Questions
The things people ask first.
Which carriers does TrackingMCP cover?
233 carriers covered, with 125 direct carrier connectors and 186 SCACs recognised, events normalised to the DCSA standard. A container number, a bill of lading or a booking all resolve to the same clean timeline.
How are the ETAs calculated?
Arrival is predicted from the delay we actually observe on the lane and the vessel, reconciled with the carrier’s own estimate and live positions fused from 4 AIS networks. It is not a stale promise that never updates. Events land within five minutes of the carrier knowing.
Can I get a webhook when something changes?
Yes. HMAC-signed webhooks fire the moment an ETA moves, a box is discharged or a hold appears, so your systems react without polling.
Is there a REST API as well as MCP tools?
Both. Every capability is available as a Model Context Protocol tool and as a REST endpoint, behind the same key.
Pairs with
Better with the rest of the spine.
Track any air waybill, from acceptance to delivery, in one clean timeline.
Compare sailings the way a freight desk actually books them.
Plan the stuff inside the box: to the standard, not by eye.
See what a lane costs this week, before you brief a forwarder.
Make your first TrackingMCP call today.
Free tier, five-minute first call, no front-end of ours required.