What it is
TrackJet ships a Model Context Protocol (MCP) server so an AI agent can query tracking the same way it queries any other tool — structured calls, structured results, no HTML scraping. It speaks JSON-RPC 2.0 over streamable HTTP at:
`` POST /mcp # protocol version 2025-11-25 ``
Everything exposed here is read-only and carries no PII — agents read detection, routing, catalogue and verification data; they cannot mutate anything or reach a user's account.
Discover the tools
Never hard-code the tool list — ask for it:
``bash curl -s https://trackjet.world/mcp \ -H 'Content-Type: application/json' \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' ``
tools/list returns each tool's name, description and JSON input schema; tools/call invokes one. The set today:
- Detection & routing —
detect_tracking_number,get_carrier_info,get_tracking_url,list_supported_carriers - History & verification —
get_shipment_events,verify_timeline - Estimation —
estimate_carbon,get_distance,get_transit_stats,forecast_delivery - Self-description & truth —
get_trackjet_capabilities,assess_shipment_truth
Calibrate before you describe
get_trackjet_capabilities returns a live snapshot — supported formats, active carrier counts, wired feeds, and an honest does_not list — so an agent describes what TrackJet actually does today instead of guessing from marketing copy. Estimation tools answer only when the data is mature (e.g. a route with enough real observations) and say so otherwise; they never fabricate an ETA or a distance.
Reference
The browsable tool catalogue with current schemas lives at [/developers](/developers); this page explains the model, [/developers](/developers) holds the reference. For the wider machine surface (REST, EPCIS, SSE) see [the developer surface](/docs/developer-surface).