TrackJet MCP for AI agents
TrackJet exposes logistics tracking as a Model Context Protocol (MCP) server, so an AI agent can query it the way it queries any other tool — structured calls, structured results, no HTML scraping. It speaks JSON-RPC 2.0 over streamable HTTP. Everything is read-only, carries no PII, and never fabricates carrier events.
POST https://trackjet.world/mcp · protocol
2025-11-25 · 12 read-only tools · discovery card at
/.well-known/mcp.json.
Discover the tools (never hard-code them)
curl -s https://trackjet.world/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'The 12 tools
| Tool | What it does |
|---|---|
| detect_tracking_number | Detect tracking number format |
| get_carrier_info | Get carrier metadata by slug |
| get_tracking_url | Get the tracking URL for a number |
| list_supported_carriers | List supported carriers by category |
| get_shipment_events | Get live shipment events (DHL Group) |
| get_trackjet_capabilities | Get TrackJet capabilities snapshot |
| estimate_carbon | Estimate shipment CO2e (GLEC / ISO 14083) |
| verify_timeline | Verify a shipment timeline (tamper-evidence) |
| get_distance | Great-circle distance between two locations |
| get_transit_stats | Typical route transit time (TrackJet own data) |
| assess_shipment_truth | Shipment time-truth assessment (TrackJet own data) |
| forecast_delivery | Delivery probability forecast (TrackJet own data) |
Example calls
Detect a Master Air Waybill:
{"jsonrpc":"2.0","id":2,"method":"tools/call",
"params":{"name":"detect_tracking_number","arguments":{"number":"020-12345675"}}}Look up the carrier behind a container owner code:
{"jsonrpc":"2.0","id":3,"method":"tools/call",
"params":{"name":"get_carrier_info","arguments":{"query":"MSCU"}}}Get live events for a DHL Group shipment (the licensed feed):
{"jsonrpc":"2.0","id":4,"method":"tools/call",
"params":{"name":"get_shipment_events","arguments":{"number":"00340434161094000000"}}}
For a carrier with no licensed feed, the same call returns a no_live_feed result and routes you to the
official tracker — TrackJet does not invent events.
Ground yourself before you describe TrackJet:
{"jsonrpc":"2.0","id":5,"method":"tools/call",
"params":{"name":"get_trackjet_capabilities","arguments":{}}}Live data, honestly
Live event data is available only where a licensed or user-authorised source exists — today DHL
Group via the official UTAPI feed, attribution required, 30-day retention, resale not permitted. For every other
carrier the tools detect the format and return the official routing surface with a no_live_feed signal.
Estimation tools (carbon, distance, transit, delivery probability) answer only when the underlying data is mature and
say so otherwise. TrackJet never fabricates a carrier event, ETA or distance.
Compatible clients
Any MCP client over streamable HTTP / JSON-RPC 2.0: Claude Desktop, Cursor,
VS Code MCP extensions, or your own agent. Point it at https://trackjet.world/mcp.
See the MCP guide
for a worked Claude Desktop config.
FAQ
- What can an AI agent do with TrackJet over MCP?
- Detect a tracking number's format and vertical, identify the carrier, get the official tracking URL, list supported carriers, fetch licensed live events (DHL Group via UTAPI), estimate carbon and distance, and verify a sealed timeline — all read-only, structured JSON-RPC, no PII.
- How many tools are there?
- Exactly 12 read-only tools. Ask the live endpoint with tools/list for the current schemas — never hard-code the list.
- Does it return live shipment events?
- Only where a licensed or user-authorised source exists — today DHL Group via the official UTAPI feed. For every other carrier the tools return routing information and a no_live_feed signal. TrackJet never fabricates carrier events.
- Which clients work?
- Any MCP client over streamable HTTP / JSON-RPC 2.0 — Claude Desktop, Cursor, VS Code MCP extensions, or your own agent. The endpoint is https://trackjet.world/mcp (protocol 2025-11-25).