Multi-Carrier Tracking MCP
guptaprakhariitr/multi-carrier-tracking-mcp
Rastreamento multi-transportadora com auto-detecção e histórico de eventos
Ver no GitHubServidor MCP que detecta automaticamente a transportadora de um número de rastreamento e retorna eventos estruturados de entrega. Integra USPS, UPS, FedEx, DHL, India Post, Delhivery, BlueDart e Aramex em uma única interface. Essencial para agentes de e-commerce, logística e suporte ao cliente.
Instalação
npx convez-ai guptaprakhariitr/multi-carrier-tracking-mcp1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Agentes de e-commerce consultarem status de entrega em tempo real
- Sistemas de suporte ao cliente automático responderem sobre pacotes
- Integrações de fintech e marketplaces rastrearem múltiplas encomendas
- Aplicações de logística buscarem posição de entregas
Veredito

Projeto bem pensado que resolve um problema real e horizontal — todo agente de shopping/logística precisa disso. Status é de scaffold, mas a arquitetura está clara e as APIs de carriers são maduras. Recomendado para quem precisa de rastreamento confiável multi-operador.
README
A tradução para o português deste README ainda está na fila.
multi-carrier-tracking-mcp — SCAFFOLD
Auto-detect shipping carrier from a tracking number, return structured tracking events. Wraps USPS, UPS, FedEx, DHL, India Post, Delhivery, BlueDart, Aramex. Universal pain across every shopping/logistics agent.
Status: scaffolded. Build this second (after sec-edgar-mcp). Idea #17 from ../../../ai-as-customer-ideas.md.
Why this is the warm-up
- No domain edge needed — every dev has hit "the agent couldn't track my package" once.
- Each carrier API is small; the integration cost is in volume (8 carriers), not depth.
- Broad horizontal install — fintech, e-commerce, customer-support agents, personal-life agents.
- Low support load: one input (tracking #), one output (events).
Planned tools
| Tool | What it does |
|---|---|
track_package(tracking_number, carrier?) | Auto-detect carrier; return latest status + event timeline. |
track_multiple(tracking_numbers[]) | Batch (up to 25). |
subscribe_tracking(tracking_number, webhook_url) | Premium tier: webhook on status change. |
Carrier auto-detection
Each carrier has a tracking-number format signature. Build a regex table — most carriers have unique enough patterns that 90% of detections are deterministic. Fallback: query 2-3 most-likely carriers in parallel and use whichever responds with a non-404.
| Carrier | Pattern (rough) | API |
|---|---|---|
| USPS | 20 or 22 digit | USPS Web Tools (free key) |
| UPS | 1Z + 16 char | UPS Tracking API (free tier 10k/mo) |
| FedEx | 12, 15, 20 digit | FedEx Track API (free tier) |
| DHL | 10 digit | DHL Express API (free tier 250/day) |
| India Post | 13-char EE...IN | IndiaPost JSON (scrapable) |
| Delhivery | 12-14 digit | Delhivery public tracking |
| BlueDart | 11-digit | BlueDart public tracking page |
Pricing (proposed)
| Tier | Price | Calls / mo |
|---|---|---|
| Free | $0 | 100 |
| Solo | $9 | 2,000 |
| Team | $29 | 10,000 (incl. subscribe_tracking) |
| Pro | $79 | 50,000 |
Build steps
- Fork
../sec-edgar-mcp/tomulti-carrier-tracking-mcp/. - Replace
src/edgar.tswithsrc/carriers/containing one client per carrier. - Build
src/detect.tsfor tracking-number routing. - Tests: one fixture per carrier (real shipped packages, anonymize the addressee).
- Deploy + list on registries.
Open / closed split
- Open: tracking-number regex detection table, carrier list, basic per-carrier client stubs.
- Closed: optimized parallel-fallback logic, webhook subscription engine, address-anonymization for shareable links (privacy moat).
Notes / gotchas
- Several carriers ban "tracking aggregators" in their ToS. Use only carrier-published APIs; do not scrape consumer-facing pages.
- USPS and India Post have explicit retail-volume free tiers; commercial use may require their paid tier — read each carrier's ToS line by line before launch.
- Cache aggressively (1h for "in transit", 5min for "out for delivery"). Tracking events are append-only so caching is safe.
See also
../sec-edgar-mcp/— reference implementation.../README.md— Category 1 pipeline.
Sister MCPs
All from the same operator, all live on <product>.prakhar-cognizance.workers.dev, all free-tier friendly:
| Group | Products |
|---|---|
| Research | sec-edgar · arxiv · world-bank-economic · uspto-patents · fda-approvals |
| Verification + Utility | verification ⭐ · unit-converter |
| India | indic-normalize · indian-regulatory |
| Real-time | hn-trending · wikipedia-recent-changes · gdelt-events · crypto-prices |
| Healthcare | drug-interaction |
| Logistics | multi-carrier-tracking |
Full catalog: https://github.com/guptaprakhariitr · ⭐ = empty-quadrant / highest-conviction pick.