Skip to content
TrackingMCP

A container tracking API that knows when the box will really arrive.

One container tracking API for 240+ carriers: 203 direct connectors and 350 SCACs recognised. Send a container number, bill of lading or booking and get back status, route, milestones and an ETA built from the delay we actually observe, plus demurrage and detention free-time, port congestion and vessel positions. Delivered over MCP, REST and webhooks.

MCP call

trackingmcp.com · live
{ "tool": "get_container_detail",
"ref": "MSCU1234567" }
response
{ "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 }
add_containerget_container_detailget_shipment_summary
203 direct connectors · 240+ carriers coveredEvents normalised to the DCSA standardHMAC-signed webhooksMCP tools + REST API

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 instead of guessing from a scraped screen. 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 show the carrier’s own published free-time and the clock running 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 and a cross-checked network source, with automatic failover. When a carrier changes something, the connector re-mints its own credentials and re-probes live boxes before anyone gets paged.

Call it as tools

The whole container tracking API, as MCP tools or REST endpoints.

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.

Read the TrackingMCP docs
TrackingMCP · tools
  • 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.

240+ carriers, 203 of them through direct connectors, and 350 SCACs recognised, with every event normalised to the DCSA standard. A container number, a bill of lading or a booking all resolve to the same clean timeline.

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, so the date keeps moving with the ship. Events land within five minutes of the carrier knowing.

Yes. HMAC-signed webhooks fire the moment an ETA moves, a box is discharged or a hold appears, so your systems react without polling.

Both. Every capability is available as a Model Context Protocol tool and as a REST endpoint, behind the same key.

Make your first TrackingMCP call today.

Free tier, five-minute first call, no front-end of ours required.