MCP QUEEN
io.github.lxxmng/container-tracking A
DCSA container tracking across 228 ocean carriers: live vessel positions, ETAs, demurrage alerts.
Dev & Codev1.3.0streamable-httpmcp.trackingmcp.com declared repository
Server identity and mutable locations
| Registry identity | io.github.lxxmng/container-tracking |
| Stable evidence key | https://mcpqueen.com/s/io.github.lxxmng/container-tracking |
| Declared repository | https://github.com/lxxmng/container-tracking-mcp Mutable Registry metadata; not proof of current ownership or availability. Mapping synchronized . |
| Operational endpoint | https://mcp.trackingmcp.com/mcpProbed separately from repository state. |
Repositories can be renamed, transferred, archived, privatized, or deleted. MCP Queen keeps this evidence page and badge keyed to the Registry name. Moved this repository? Follow the maintainer guide.
Research this MCP server inside your agent
Connect MCP Queen to ChatGPT, Claude, or your own agent to retrieve this server's operational evidence, Trust Receipt, caveats, and reviewed field reports without leaving the conversation.
Grade evidence — probed 2026-10-02 00:45 UTC
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 87ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo container-tracking@1.0.0 |
| tooling | 35 / 35 | tools/list OK: 7 tools e.g. "get_shipment_summary"; 7/7 described, 7/7 fully-typed schemas, median description 193 chars |
| latency | 10 / 10 | initialize round-trip 87ms |
| provenance | 15 / 15 | description present; repository linked; version 1.3.0; namespace io.github.lxxmng matches endpoint/repo |
Score 100/100 · latency 87ms · 7 tools · protocol access: open ⓘ
Trust receipt
Security, data integrity, citation quality, and advertised claims are measured separately from protocol uptime. Missing evidence is marked unverified, never converted into a pass.
| Dimension | Metric | Status | Evidence | Source |
|---|---|---|---|---|
| security | authentication_boundary | observed | Live protocol probe observed auth_state=open. This describes discovery/access behavior; it is not by itself a vulnerability finding. Observed value: open | live_probe |
Machine-readable receipt: /api/trust/io.github.lxxmng/container-tracking.json
Connect your agent
Claude Code:
claude mcp add --transport http container-tracking https://mcp.trackingmcp.com/mcp
Generic MCP client config:
{ "mcpServers": { "container-tracking": { "type": "http", "url": "https://mcp.trackingmcp.com/mcp" } } }
MCP Queen is a graded index, not a middleman — your agent connects directly to the server above. Check the grade and evidence first; that's the point.
Share this server: permalink https://mcpqueen.com/s/io.github.lxxmng/container-tracking · referral link https://mcpqueen.com/go/io.github.lxxmng/container-tracking (safe HTTPS redirect; GET does not write state).
Own this server? Embed your grade badge
Live operational-grade badge, re-probed continuously — not a security or data-quality certification. Copy the ready-made Markdown into your README:
[](https://mcpqueen.com/s/io.github.lxxmng/container-tracking)
Think the grade is wrong? Fix the finding the evidence shows, then the next probe cycle picks it up automatically (full cycle ≈ 3 days) — or open a dispute via the MCP endpoint.
Queen Watch
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta. Need recommendations and change review across several servers? Try the Scout + Guard pilot.
Probe history
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-10-02 00:45 | A | 100 | 87ms |
| 2026-09-23 15:20 | C | 62 | 1260ms |
| 2026-09-16 00:00 | C | 62 | 615ms |
| 2026-09-08 21:45 | C | 66 | 167ms |
| 2026-09-02 23:45 | C | 66 | 109ms |
| 2026-08-28 16:00 | C | 66 | 78ms |
| 2026-08-23 15:30 | C | 66 | 80ms |
| 2026-08-18 20:30 | C | 66 | 71ms |
| 2026-08-14 13:45 | C | 66 | 443ms |
| 2026-08-10 14:30 | F | 15 | —ms |