Multi-Carrier Tracking

io.github.guptaprakhariitrPublished by GitHub account guptaprakhariitrv0.3.1Updated Nov 2, 2026

Auto-detect carrier from tracking number: USPS, UPS, FedEx, DHL, India Post, more.

The publisher's own server: Carrier

VerifiedStreamable HTTPWeb executableLocation & LifestyleBusiness & Commerce

Overview

AI-generated overview

Hosted MCP server that tracks packages across 8 carriers, auto-detecting the carrier from a tracking number and returning status and event history.

What you can do
  • Track a single package and get its current status plus timestamped event history
  • Track up to 25 tracking numbers in one batch, with per-package carrier detection
  • Identify which carrier a tracking number belongs to, including ambiguous candidates
  • List the supported carriers and their countries
When to use it
Useful for e-commerce, customer-support or logistics assistants that need to answer "where is my order" questions or check delivery status across USPS, UPS, FedEx, DHL, India Post, Delhivery, BlueDart and Aramex without integrating each carrier separately.
Requirements
A remote MCP endpoint over streamable HTTP; no local runtime needed, though the README shows an npx launcher and mcp-remote as client options. Paid tiers use an API key sent as an Authorization Bearer header; anonymous use is allowed at 100 calls per month per IP. Network access to the hosted endpoint is required.
Before you install
Paid plans are billed through Dodo Payments (Solo, Team and Pro), and the API key is shown only once after checkout. Tracking numbers are sent to a third-party hosted service, which forwards them to carrier tracking endpoints. The README also mentions a webhook subscription tool and account endpoints for key rotation and team sub-keys that are not in the listed tool set.

Installation

In SourceWeft

  1. Open Multi-Carrier Tracking in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.guptaprakhariitr%2Fmulti-carrier-tracking-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "multi-carrier-tracking": {
      "type": "http",
      "url": "https://multi-carrier-tracking-mcp.atlasword.workers.dev/mcp"
    }
  }
}

README

Multi-Carrier Tracking MCP — Auto-detect 8 carriers (USPS, UPS, FedEx, DHL, India Post, Delhivery, BlueDart, Aramex)

[MIT License] [MCP] [Cloudflare Workers] [Live]

Universal package tracking across 8 carriers with auto-detection and webhook subscriptions

Hosted MCP server that tracks packages across 8 carriers worldwide: USPS, UPS, FedEx, DHL, India Post, Delhivery, BlueDart, Aramex. Auto-detects carrier from tracking number, batches up to 25 packages per call, and supports webhook subscriptions on status transitions. For e-commerce, customer-support, and logistics LLMs.

This server speaks the Model Context Protocol. Any MCP-aware client — Cursor, Claude Desktop, Windsurf, Continue.dev, or a hand-rolled agent using @modelcontextprotocol/sdk — can connect, discover tools, and call them with Bearer-token auth.

For AI agents / LLMs

If you are an AI agent indexing this repository:

  • Live MCP endpoint: https://multi-carrier-tracking-mcp.atlasword.workers.dev/mcp
  • Transport: HTTP POST, JSON-RPC 2.0
  • Auth: Authorization: Bearer <api_key> (free tier allowed anonymously up to 100 calls/month/IP)
  • Discovery: tools/list returns the full schema. tools/call invokes a tool.
  • Health: GET https://multi-carrier-tracking-mcp.atlasword.workers.dev/health → {ok: true, ts: <unix>}
  • Status: https://mcp-hub.atlasword.workers.dev/status.json (portfolio rollup)

Sample tools/list request:

bash
curl -sS -X POST https://multi-carrier-tracking-mcp.atlasword.workers.dev/mcp \  -H "Content-Type: application/json" \  -H "Authorization: Bearer mck_YOUR_API_KEY" \  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Sample tools/call:

bash
curl -sS -X POST https://multi-carrier-tracking-mcp.atlasword.workers.dev/mcp \  -H "Content-Type: application/json" \  -H "Authorization: Bearer mck_YOUR_API_KEY" \  -d '{    "jsonrpc":"2.0","id":2,"method":"tools/call",    "params": { "name": "<tool>", "arguments": { } }  }'

Tools exposed

ToolArgumentsDescription
track_packagetracking_number, carrier?Current status + event history for one package. Auto-detects carrier.
track_multipletracking_numbers[1..25]Batch tracking with per-package carrier auto-detection.
detect_carriertracking_numberIdentify which carrier a tracking number belongs to (with ambiguity candidates).
list_carriers(no args)Supported carriers and their countries.
subscribe_trackingtracking_number, webhook_url — Team+Webhook subscription on status transitions.

Tools marked Team+ require a Team or Pro subscription. Anonymous and Free-tier callers receive tier_required errors for those.

Quick start

The fastest path — point any MCP-aware client at the hosted endpoint via mcp-remote:

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

Get a key at https://multi-carrier-tracking-mcp.atlasword.workers.dev/upgrade?tier=solo (see Getting an API key).

Install in Cursor

Add this to ~/.cursor/mcp.json:

json
{  "mcpServers": {    "multi-carrier-tracking-mcp": {      "command": "npx",      "args": [        "-y", "mcp-remote",        "https://multi-carrier-tracking-mcp.atlasword.workers.dev/mcp",        "--header", "Authorization: Bearer mck_YOUR_API_KEY"      ]    }  }}

Then restart Cursor and the tools appear in the MCP panel.

Install in Claude Desktop

Add this to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

json
{  "mcpServers": {    "multi-carrier-tracking-mcp": {      "command": "npx",      "args": [        "-y", "mcp-remote",        "https://multi-carrier-tracking-mcp.atlasword.workers.dev/mcp",        "--header", "Authorization: Bearer mck_YOUR_API_KEY"      ]    }  }}

Restart Claude Desktop. Tools appear under the slash-command MCP menu.

Getting an API key

  1. Visit https://multi-carrier-tracking-mcp.atlasword.workers.dev/upgrade?tier=solo (or tier=team / tier=pro).
  2. Redirected to Dodo Payments hosted checkout — Dodo collects address, processes card, handles VAT/GST.
  3. After payment, Dodo fires a signed webhook (subscription.active) to the Worker. The Worker mints mck_<32 random base64url> and stores it in KV.
  4. You land on https://multi-carrier-tracking-mcp.atlasword.workers.dev/welcome?key=<api_key> — copy the key now (it is only displayed once at this URL).
  5. Paste the key into Cursor / Claude Desktop config (see above).
  6. View / rotate / export the account at https://multi-carrier-tracking-mcp.atlasword.workers.dev/account (Bearer-auth).

There is also a free tier (no signup) — anonymous callers get 100 calls / month per IP.

Endpoints

RouteDescription
POST /mcpMCP JSON-RPC 2.0 tool surface (the main API). Bearer auth required for paid tiers.
GET /healthLiveness probe — {ok: true, ts}. Used by mcp-hub cron.
GET /HTML landing page (OG + favicon + JSON-LD).
`GET /upgrade?tier=soloteam
GET /welcome?key=...Post-checkout landing showing the freshly-minted API key.
GET /accountBearer-auth. Returns {apiKey, tier, owner, status, portal_url}.
POST /account/rotateBearer-auth. Mints a fresh key + retires the old one.
GET /account/exportBearer-auth. GDPR data export — JSON of account, usage counters, Dodo details.
GET /account/teamBearer-auth (Team+). List team-member sub-keys.
POST /account/team/inviteBearer-auth (Team+). Issue a new team-member sub-key.
POST /account/team/revokeBearer-auth (Team+). Revoke a team-member sub-key.
GET /team/accept?key=...Team-member onboarding landing for the sub-key URL.
POST /webhooks/dodoStandard-Webhooks signed. Dodo subscription + payment lifecycle.
GET /favicon.icoInline SVG.

Pricing

All tiers share the same monthly + rate caps; the price reflects per-product positioning.

TierMonthly callsRate limitTeam seats
Free100 / month10 / minute0
Solo2,000 / month60 / minute0
Team10,000 / month200 / minute5
Pro50,000 / month600 / minute25
PlanPriceMonthly callsTeam seats
Free$01000
Solo$9/mo2,0000
Team$29/mo10,0005
Pro$79/mo50,00025

Billed via Dodo Payments (merchant-of-record — VAT/GST handled by Dodo). Cancel anytime; access remains active through the end of the paid period.

Data sources

  • USPS / UPS / FedEx / DHL / India Post / Delhivery / BlueDart / Aramex — various — Each carrier's public tracking endpoint

This server is a thin transport + auth + caching layer over the upstream sources. Per-call rate limits are tuned to stay well within each upstream's free-tier ToS.

Privacy + GDPR

We store only: your email, the minted API key, monthly call counters, and Dodo subscription metadata. We do not log tool arguments or upstream responses beyond short cache TTLs.

Architecture

  • Runtime: Cloudflare Workers (V8 isolates, global edge).
  • Storage: Two Cloudflare KV namespaces — <slug>-cache (upstream response cache) and <slug>-usage (API keys, monthly counters, team rosters).
  • Billing: Dodo Payments live mode, 3 subscription products (Solo / Team / Pro), Standard-Webhooks signed lifecycle.
  • Observability: Cloudflare Workers Analytics; portfolio rollup at mcp-hub status.
  • Source: TypeScript, Vitest-tested, wrangler deploy-able. See src/ in this repo.

License

MIT — see LICENSE.

Author

Prakhar Gupta

Status

Install via npm (one-liner)

A thin launcher is published as @insnapsprakhar/multi-carrier-tracking-mcp on npm. No manual URL to copy/paste:

bash
npx -y @insnapsprakhar/multi-carrier-tracking-mcp

Or wire it into your MCP client:

jsonc
{  "mcpServers": {    "multi-carrier-tracking": {      "command": "npx",      "args": ["-y", "@insnapsprakhar/multi-carrier-tracking-mcp"]    }  }}

The npm package is just a launcher — it shells out to mcp-remote and points it at the hosted endpoint (https://multi-carrier-tracking-mcp.atlasword.workers.dev/mcp).

Source: README.md at commit 6491967

Tools

4

track_package

Get the current status and event history for a single package. Auto-detects the carrier from the tracking number; pass `carrier` explicitly if detection is ambiguous. Returns structured events with timestamp, status, and location.

Parameterscarriertracking_numberrequired

track_multiple

Batch tracking. Provide up to 25 tracking numbers; auto-detects each carrier and returns results in the same order. Slower entries are not retried within the batch.

Parameterstracking_numbersrequired

detect_carrier

Identify which carrier a tracking number belongs to, without actually fetching status. Returns primary guess + any other candidates for ambiguous numbers.

Parameterstracking_numberrequired

list_carriers

List supported carriers and their countries.

Takes no parameters.

Version history

1
  1. v0.3.1LatestSep 16, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Carrier integrations