Multi Carrier Tracking

What Multi-Carrier Tracking MCP server does

The Multi-Carrier Tracking MCP server gives an AI agent one MCP tool surface for tracking packages across eight named carriers: USPS, UPS, FedEx, DHL, India Post, Delhivery, BlueDart, and Aramex. It uses each carrier’s public tracking endpoint as an upstream source and presents the results through a hosted Cloudflare Workers service.

Agents can request the current status and event history for one shipment, or submit up to 25 tracking numbers in a batch. When a number could match more than one carrier, the detection tool returns ambiguity candidates. The service also exposes the supported carriers and their countries.

The Multi-Carrier Tracking MCP server supports webhook subscriptions for shipment status transitions. This capability is available through subscribe_tracking, which accepts a tracking number and webhook URL.

How it works

The live MCP endpoint is:

https://multi-carrier-tracking-mcp.atlasword.workers.dev/mcp

Clients send MCP JSON-RPC 2.0 requests with HTTP POST. The main operations are tool discovery through tools/list and execution through tools/call. Authentication uses an Authorization: Bearer <api_key> header. Anonymous access is available for up to 100 calls per month per IP; paid tiers provide higher monthly and per-minute limits.

The hosted service is implemented on Cloudflare Workers. It acts as a transport, authentication, and caching layer over the carrier tracking sources. The repository states that tool arguments and upstream responses are not logged beyond short cache time-to-live periods.

Setup and configuration

The simplest connection method uses mcp-remote with the hosted endpoint:

npx -y mcp-remote https://multi-carrier-tracking-mcp.atlasword.workers.dev/mcp \
  --header "Authorization: Bearer mck_YOUR_API_KEY"

Cursor and Claude Desktop can use the same command in their MCP configuration files. Windsurf, Continue.dev, and other MCP-aware clients can connect using their supported HTTP or remote-server configuration. A client can also call the endpoint directly with JSON-RPC over HTTP.

An API key can be obtained through the service’s Solo, Team, or Pro checkout flow. The free tier does not require signup.

Tools and capabilities

The available tools are:

• track_package: Retrieves current status and event history for one tracking number, with optional carrier input.
• track_multiple: Tracks one to 25 numbers in a single call and detects each carrier independently.
• detect_carrier: Identifies the likely carrier and returns candidate matches when detection is ambiguous.
• list_carriers: Lists supported carriers and their countries; it takes no arguments.
• subscribe_tracking: Creates a webhook subscription for status transitions using a tracking number and webhook URL.

The webhook subscription tool requires a Team or Pro subscription. Anonymous and Free-tier callers receive a tier_required error for that operation.

Limitations and notes

Coverage is limited to the eight carriers named by the project. Tracking data depends on the availability and behavior of each carrier’s public endpoint. The service is not described as a universal carrier adapter beyond those sources.

Usage limits vary by tier. Free allows 100 monthly calls and 10 calls per minute; Solo allows 2,000 monthly calls and 60 per minute; Team allows 10,000 monthly calls and 200 per minute; Pro allows 50,000 monthly calls and 600 per minute. Team and Pro also enable webhook subscriptions, with team seats available on those plans.

Its health endpoint is available at /health, while the MCP tool surface is available at /mcp.