Multi-Carrier Tracking

io.github.guptaprakhariitrv0.3.1更新於 Oct 7, 2026

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

已驗證Streamable HTTP可網頁執行Business & CommerceProductivity & Workflow

概覽

AI 產生的概覽

讓助理跨八家貨運業者查詢包裹物流，並依單號自動辨識貨運業者。

功能
這是一個託管型 MCP 伺服器，可查詢 USPS、UPS、FedEx、DHL、India Post、Delhivery、BlueDart 與 Aramex 的包裹。工具包括：track_package 查詢單一包裹的目前狀態與事件歷程；track_multiple 批次查詢最多 25 個單號；detect_carrier 辨識單號所屬業者並列出可能的候選；list_carriers 列出支援的貨運業者。狀態變更的 webhook 訂閱工具僅限 Team 與 Pro 方案使用。
適用情境
適合電商、客服或物流類助理回答「包裹到哪了」或批次核對配送狀態。當物流查詢是經常性任務而非一次性需求時，值得接入。
執行需求
遠端 streamable HTTP 端點，不需要本機執行環境；README 也提供 npm 啟動器與 mcp-remote 的接入方式。付費方案需要 API key，透過 Authorization Bearer 標頭傳送；匿名呼叫有免費額度，每個 IP 每月 100 次。需要能連線至該託管端點的網路。
安裝前請注意
付費方案透過第三方商户記錄方計費，安裝可能產生週期性訂閱費用。API key 僅在結帳後的頁面顯示一次，需妥善保存，可於帳戶頁面輪換或匯出。單號與 webhook 網址會傳送到該託管服務及其上游貨運業者介面，服務會保存電子郵件、金鑰、用量計數與帳務中繼資料。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Multi-Carrier Tracking，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "multi-carrier-tracking-mcp": {
      "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).

來源：README.md，提交 6491967

工具

0
工具後設資料尚未被收錄。

版本歷史

1
  1. v0.3.1最新Sep 16, 2026