Container Tracking MCP

io.github.lxxmngPublished by GitHub account lxxmngv1.3.0Updated Oct 24, 2026

DCSA container tracking across 228 ocean carriers: live vessel positions, ETAs, demurrage alerts.

VerifiedStreamable HTTPWeb executableLocation & LifestyleBusiness & Commerce

Overview

AI-generated overview

Hosted MCP server that lets an assistant track ocean containers across 200+ carriers, with milestones, vessel positions, ETAs and demurrage risk.

What you can do
Look up shipments by container, bill of lading or booking number and read full status, route, ETA and event history, plus an AI-generated narrative for one container and a portfolio overview of active containers, exceptions and demurrage risk. Retrieve live AIS vessel positions by IMO, including coordinates, speed, heading and navigational status. Report demurrage and detention exposure, free-time countdowns, daily rates and projected cost. Check port congestion by UN/LOCODE, with average wait time, vessels at anchor and a severity level. Add a new container or bill of lading to tracking, with optional tags, first update arriving in about 15 minutes.
When to use it
Useful for freight, logistics and supply-chain work where someone needs to check where a container is, when it will arrive, or whether demurrage charges are looming, without logging into each carrier's portal. Also suited to monitoring port congestion before routing shipments.
Requirements
A remote hosted endpoint; nothing to self-host. OAuth authentication is declared, and the README describes a bearer API key, with a public demo key for trials and a free key for production. Paid token plans are needed for ongoing use. Network access to the hosted server.
Before you install
Usage is token-metered and paid plans range from €49 to €849, so real queries consume purchased tokens. The README's demo key is public and meant only for trying the server; use your own key for live tracking. Adding a container writes new tracking records to your account. Shipment identifiers and queries are sent to the third-party hosted service.

Installation

In SourceWeft

  1. Open Container Tracking MCP in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.lxxmng%2Fcontainer-tracking/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "container-tracking": {
      "type": "http",
      "url": "https://mcp.trackingmcp.com/mcp"
    }
  }
}

README

Container Tracking MCP Server

[npm] [smithery badge]

Track ocean containers across 200+ shipping lines from Claude, ChatGPT, Cursor, or any MCP client.

Container Tracking MCP is an ocean-freight MCP server that lets an AI assistant track a container via MCP across 225 carriers — including Maersk, MSC, CMA CGM, COSCO, and Hapag-Lloyd. Track by container number, bill of lading, or booking number to get live milestones, vessel position, ETA, and demurrage & detention free time as DCSA-normalised events. It runs as a hosted remote server, so there is nothing to self-host.

Ask your AI: "Where is container MSCU7349821?" or "Which shipments have demurrage risk this week?"

Supported carriers & coverage

Container Tracking MCP covers 200+ ocean shipping lines (225 carriers). Top lines include:

Maersk · MSC · CMA CGM · COSCO · Hapag-Lloyd · ONE (Ocean Network Express) · Evergreen · HMM · Yang Ming · ZIM · OOCL · Wan Hai · PIL · Hyundai · SITC · KMTC · Matson · Sinokor · Heung-A · Namsung — and 200+ more.

Every carrier is normalised to the DCSA ocean-tracking event standard, so a milestone from any line looks the same to your AI client. Track by:

  • Container number (e.g. MSCU7349821)
  • Bill of lading number
  • Booking number

You get: live milestone events, current vessel name + IMO, live AIS vessel position, ETA with a confidence percentage, demurrage & detention free-time countdown, and port congestion signals.

Tools

ToolWhat it does
getShipmentSummaryPortfolio overview: total active containers, exceptions, arriving soon, and demurrage risk. Use first to see what needs attention.
getContainerDetailFull status for one container: current location, route, ETA with confidence %, carrier, vessel name + IMO, complete event history, and an AI-generated narrative.
getVesselPositionLive AIS position for a vessel: latitude, longitude, speed over ground, heading, and navigational status (by IMO).
getDemurrageReportDemurrage & detention risk: which containers are near or past free days, daily rates, and projected cost if not moved.
getPortCongestionCongestion at one or more ports by UN/LOCODE: average vessel wait time, vessels at anchor, and level (low/moderate/high/severe).
addContainerStart tracking a new container ID or bill of lading. First status update arrives within ~15 minutes; optional tags organise by client, project, or urgency.

Quick connect

The server is hosted at https://mcp.trackingmcp.com/mcp. Try it with zero signup using the public demo key tmcp_demo_public, or get a free API key.

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

json
{  "mcpServers": {    "container-tracking": {      "command": "npx",      "args": ["-y", "mcp-remote", "https://mcp.trackingmcp.com/mcp",               "--header", "Authorization: Bearer tmcp_demo_public"]    }  }}

Cursor / Windsurf / VS Code (native HTTP MCP)

json
{  "mcpServers": {    "container-tracking": {      "url": "https://mcp.trackingmcp.com/mcp",      "headers": { "Authorization": "Bearer tmcp_demo_public" }    }  }}

Replace tmcp_demo_public with your own key from trackingmcp.com/mcp for live production tracking. Registry ID: io.github.lxxmng/container-tracking.

Example prompts

  • "Where is container MSCU7349821?"
  • "What's the status of bill of lading HLCU2840012?"
  • "Give me a summary of all active shipments."
  • "Which containers arrive at Rotterdam this week?"
  • "Am I at risk of demurrage on any containers?"
  • "How congested is Felixstowe port right now?"
  • "Start tracking BL MAEU123456789."

Pricing

Token-metered, no subscription. Starter 3,000 tokens €49 · Growth 15,000 €199 · Pro 50,000 €549 · Enterprise 100,000 €849. Tokens never expire. One full container check (getContainerDetail + getVesselPosition + getShipmentSummary) ≈ 90 tokens. See trackingmcp.com/pricing.

Links

License

MIT

Source: README.md at commit 259c03c

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.3.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts