TrackingMCP gives you live ocean container tracking two ways — a REST API with webhooks, and a hosted MCP server for AI agents. One normalized, DCSA-aligned feed across 50+ carriers: live events, vessel positions, ETAs, and demurrage & detention.
Connect any MCP client — Claude Desktop, ChatGPT, Cursor, Windsurf — to the hosted server at https://mcp.trackingmcp.com/mcp with a bearer API key. Tools:
| Tool | What it does |
|---|---|
| get_container_detail | Full status for one container — route, ETA, vessel position, AI narrative |
| get_shipment_summary | Portfolio overview — active shipments, exceptions, arriving soon, demurrage risk |
| get_demurrage_report | Which containers are past free days and the projected cost |
| get_port_congestion | Wait times and vessel queue at any port by UN/LOCODE |
| add_container | Start tracking a new container or B/L number |
Both return the same normalized, DCSA-aligned data — pick by how you consume it.
Each carrier has its own portal, login, and data shape. TrackingMCP does one integration for you — 50+ carriers normalized to DCSA, no scraping, no per-carrier logins — so your code (or your AI agent) reads every shipment the same way.
Is there a free container tracking API?
Yes. TrackingMCP has a free tier — generate an API key and start tracking containers via the REST API or the MCP server at no cost.
Does the container tracking API work with ChatGPT and Claude?
Yes. TrackingMCP ships a hosted MCP (Model Context Protocol) server at https://mcp.trackingmcp.com/mcp, so Claude, ChatGPT, Cursor, and any MCP client can track containers, check vessel positions, and monitor demurrage directly.
Which carriers does the API cover?
TrackingMCP covers 50+ ocean carriers — MSC, Maersk, CMA CGM, COSCO, Hapag-Lloyd, ONE, Evergreen, ZIM and more — normalized into one DCSA-aligned event model.
Is the data DCSA-compliant?
Yes. Carrier events are normalized to DCSA Track & Trace v2.2-compatible structures — transport and equipment events, UN/LOCODE locations, and event classifiers — so every carrier reads the same way.
REST API or MCP — which should I use?
Use the REST API and webhooks for backend integrations, TMS automations, and dashboards. Use the MCP server when you want an AI agent or copilot to read and act on shipment state conversationally. Both return the same normalized data.
MCP server → · MCP docs → · Developers / REST API → · Track by carrier →