Container Tracking MCP
REMOTE · MCP.TRACKINGMCP.COM
DCSA container tracking across 228 ocean carriers: live vessel positions, ETAs, demurrage alerts.
Available components
Last scanned (22 hours ago)
Scores higher than 13% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
Checks we ran (4)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
- Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 13 Oct 26 0
- Endpoint reachability: reachable → behind authorisation ▼ security
- Transport: pass → unverified ▼ security
- Stability: 0.37 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 2 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 1 Oct 26 0
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 93 functional
- First check of Tool coverage: 100 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://mcp.trackingmcp.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=trackingmcp.com | CN=YE1,O=Let's Encrypt,C=US | 24 Sept 2026 | 23 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5b2168bbc403cc6f212bcf3df916e36bc78 |
| SANs: *.trackingmcp.com, trackingmcp.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.trackingmcp.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| trackingmcp.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.trackingmcp.com/.well-known/oauth-protected-resource", scope="openid email profile"
Bearer resource_metadata="https://mcp.trackingmcp.com/.well-known/oauth-protected-resource", scope="openid email profile" | Header | Value |
|---|---|
| www-authenticate | Bearer resource_metadata="https://mcp.trackingmcp.com/.well-known/oauth-protected-resource", scope="openid email profile" |
Protected resource metadata
| Document | https://mcp.trackingmcp.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.trackingmcp.com/mcp |
| Authorisation server | https://kcibhpjcnqusehqgfxpu.supabase.co/auth/v1 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.trackingmcp.com/mcp | Auth required | 401 | |
| http (plaintext) | http://mcp.trackingmcp.com/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_container ~104
Start tracking a new container or Bill of Lading. Returns confirmation once tracking is set up. First status update arrives within 15 minutes.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Container number (e.g. MRKU5004867) or B/L number |
| identifier_type | string | yes | Whether the identifier is a container number or B/L number |
| tags | array | – | Optional tags for organisation (e.g. ["client-acme", "vessel-gulsun"]) |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | On an empty result: NOT_FOUND (no record after asking) or NO_EVENTS (record, nothing filed). |
| data | object | – | – |
| message | string | – | On an empty result: what the emptiness means. |
| ok | boolean | yes | False never appears here — failures arrive as tool errors. |
| result | string | yes | "empty" means the query succeeded and there is nothing to report. |
No examples provided.
get_container_detail ~80
Full status for a single container: current status, route, ETA with confidence, carrier, vessel, all events, and AI-generated shipment narrative. Use this when asked about a specific container.
| Name | Type | Req | Description |
|---|---|---|---|
| container_id | string | yes | Container number (e.g. MRKU5004867) or B/L number (e.g. SEGU3103001) |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | On an empty result: NOT_FOUND (no record after asking) or NO_EVENTS (record, nothing filed). |
| data | object | – | – |
| message | string | – | On an empty result: what the emptiness means. |
| ok | boolean | yes | False never appears here — failures arrive as tool errors. |
| result | string | yes | "empty" means the query succeeded and there is nothing to report. |
No examples provided.
get_demurrage_free_time ~264
Free time (days) before demurrage, detention or storage charges start, for a carrier at a port or country. Returns the carrier's OWN published figure when available, otherwise an INDICATIVE cross-carrier average (flagged is_estimate, shown without prejudice). Use for 'how many free days does <carrier> give at <port>'.
| Name | Type | Req | Description |
|---|---|---|---|
| carrier_code | string | – | SCAC, e.g. CMDU (CMA CGM), MAEU (Maersk), HLCU (Hapag), ZIMU (ZIM). Omit to get the indicative cross-carrier average directly. |
| category | string | – | demurrage (in-port), detention (out-of-port), combined_dd, or free_time_storage |
| container_type | string | – | e.g. 20GP, 40GP, 40HC, 20RF |
| country_iso2 | string | – | ISO-3166 alpha-2, e.g. FR. Used when no port is given, or as fallback grain. |
| direction | string | – | – |
| port_unlocode | string | – | 5-char UN/LOCODE, e.g. FRMRS (Marseille). Provide this or country_iso2. |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | On an empty result: NOT_FOUND (no record after asking) or NO_EVENTS (record, nothing filed). |
| data | object | – | – |
| message | string | – | On an empty result: what the emptiness means. |
| ok | boolean | yes | False never appears here — failures arrive as tool errors. |
| result | string | yes | "empty" means the query succeeded and there is nothing to report. |
No examples provided.
get_demurrage_report ~276
Demurrage and detention risk report: which containers are near or past their free days, the daily rates, and the projected cost. Call this when asked about demurrage risk or detention fees. Free days are resolved per shipment from the customer's own contract terms first, then the carrier's published tariff, then a cross-carrier benchmark — `terms_source` and `confidence` on each item say which was used, so an estimated tariff figure must be reported as estimated, not as their contract. Read the counters before drawing a conclusion: `unassessable_containers` are boxes whose free time could not be resolved at all (an empty item list alongside a non-zero count means "cannot assess", NEVER "no risk"), `uncosted_containers` are at risk with no daily rate on file (so `total_at_risk_usd` is a floor, not the exposure), and `truncated: true` means the fleet is larger than the report. Pass container_id to assess a single shipment: `scope_container.verdict` is one of at_risk / within_free_time / not_discharged / no_terms / no_destination / not_demurrage_eligible.
| Name | Type | Req | Description |
|---|---|---|---|
| container_id | string | – | Optional: scope to a single container ID. Omit for portfolio-wide report. |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | On an empty result: NOT_FOUND (no record after asking) or NO_EVENTS (record, nothing filed). |
| data | object | – | – |
| message | string | – | On an empty result: what the emptiness means. |
| ok | boolean | yes | False never appears here — failures arrive as tool errors. |
| result | string | yes | "empty" means the query succeeded and there is nothing to report. |
No examples provided.
get_port_congestion ~95
Current congestion level at one or more ports: average wait hours, vessels at anchor, and congestion level (low/moderate/high/severe). Provide UN/LOCODE codes like NLRTM, GBFXT, DEHAM, CNSHA.
| Name | Type | Req | Description |
|---|---|---|---|
| port_codes | array | yes | UN/LOCODE port codes (e.g. ["NLRTM", "GBFXT"]). Get them from container details if unsure. |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | On an empty result: NOT_FOUND (no record after asking) or NO_EVENTS (record, nothing filed). |
| data | object | – | – |
| message | string | – | On an empty result: what the emptiness means. |
| ok | boolean | yes | False never appears here — failures arrive as tool errors. |
| result | string | yes | "empty" means the query succeeded and there is nothing to report. |
No examples provided.
get_shipment_summary ~69
Overview of your entire container portfolio: total active, exceptions, arriving soon, demurrage risk. Use this as the starting point for any shipment question.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | Focus on a specific subset: all (default), exceptions, arriving_soon, demurrage_risk |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | On an empty result: NOT_FOUND (no record after asking) or NO_EVENTS (record, nothing filed). |
| data | object | – | – |
| message | string | – | On an empty result: what the emptiness means. |
| ok | boolean | yes | False never appears here — failures arrive as tool errors. |
| result | string | yes | "empty" means the query succeeded and there is nothing to report. |
No examples provided.
get_vessel_position ~205
Last known AIS position for a vessel: lat/lng, speed, heading, navigation status, and how old the fix is. Use the vessel IMO from get_container_detail. IMPORTANT: an AIS position is a LAST KNOWN fix, not a live feed. Read `position_age_hours` and `position_freshness` (live <6h, recent <24h, stale <72h, outdated >=72h, unknown = no fix time recorded) and state the age when you report the location. Terrestrial AIS cannot see a ship mid-ocean, so an outdated fix is normal and is still useful evidence of where the vessel was — but never present it as where the vessel is now. `position_updated_at` is the time WE last wrote the row and is NOT the fix age; do not use it to answer "how current is this?".
| Name | Type | Req | Description |
|---|---|---|---|
| imo | string | yes | IMO number of the vessel (e.g. 9463297) |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | On an empty result: NOT_FOUND (no record after asking) or NO_EVENTS (record, nothing filed). |
| data | object | – | – |
| message | string | – | On an empty result: what the emptiness means. |
| ok | boolean | yes | False never appears here — failures arrive as tool errors. |
| result | string | yes | "empty" means the query succeeded and there is nothing to report. |
No examples provided.
How do I install the Container Tracking MCP server?
Container Tracking MCP is a hosted endpoint at https://mcp.trackingmcp.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.trackingmcp.com
claude mcp add --transport http lxxmng-container-tracking 'https://mcp.trackingmcp.com/mcp'
What is the Container Tracking MCP server?
Container Tracking MCP is listed in the public MCP registry as io.github.lxxmng/container-tracking. DCSA container tracking across 228 ocean carriers: live vessel positions, ETAs, demurrage alerts. This page covers its hosted endpoint (https://mcp.trackingmcp.com/mcp).
Is the Container Tracking MCP server safe to use?
Container Tracking MCP scores 31 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Container Tracking MCP server expose?
Container Tracking MCP exposes 7 tools: get_shipment_summary, get_container_detail, get_vessel_position, get_demurrage_report, get_port_congestion, and 2 more. Their descriptions and schemas cost roughly 1,093 tokens of context every time the server is loaded.
Does the Container Tracking MCP server require authentication?
Yes. Container Tracking MCP asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Container Tracking MCP server still maintained?
Container Tracking MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Container Tracking MCP server?
VerifyMCP ran 4 checks on Container Tracking MCP, covering TLS certificate, Authorization, HSTS header and DNSSEC. 7 items could not be completed, a gap on our side rather than a finding about Container Tracking MCP: HTTPS, Transport, Schema quality, Stability and 3 more. 6 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.