convez.ai
MCP ServerIntegração & APIsIntermediário
guptaprakhariitr

Multi-Carrier Tracking MCP

guptaprakhariitr/multi-carrier-tracking-mcp

Rastreamento multi-transportadora com auto-detecção e histórico de eventos

Ver no GitHub
InicialPluginScore · de 0 a 100

Servidor 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-mcp

1 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

Estrelas
0
Forks
0
Acompanhando
0
Saúde
42%
Último commit
há 5 meses
Versão
—
Issues abertas
0
Contribuidores
1

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

ToolWhat 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.

CarrierPattern (rough)API
USPS20 or 22 digitUSPS Web Tools (free key)
UPS1Z + 16 charUPS Tracking API (free tier 10k/mo)
FedEx12, 15, 20 digitFedEx Track API (free tier)
DHL10 digitDHL Express API (free tier 250/day)
India Post13-char EE...INIndiaPost JSON (scrapable)
Delhivery12-14 digitDelhivery public tracking
BlueDart11-digitBlueDart public tracking page

Pricing (proposed)

TierPriceCalls / mo
Free$0100
Solo$92,000
Team$2910,000 (incl. subscribe_tracking)
Pro$7950,000

Build steps

  1. Fork ../sec-edgar-mcp/ to multi-carrier-tracking-mcp/.
  2. Replace src/edgar.ts with src/carriers/ containing one client per carrier.
  3. Build src/detect.ts for tracking-number routing.
  4. Tests: one fixture per carrier (real shipped packages, anonymize the addressee).
  5. 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


Sister MCPs

All from the same operator, all live on <product>.prakhar-cognizance.workers.dev, all free-tier friendly:

GroupProducts
Researchsec-edgar · arxiv · world-bank-economic · uspto-patents · fda-approvals
Verification + Utilityverification ⭐ · unit-converter
Indiaindic-normalize · indian-regulatory
Real-timehn-trending · wikipedia-recent-changes · gdelt-events · crypto-prices
Healthcaredrug-interaction
Logisticsmulti-carrier-tracking

Full catalog: https://github.com/guptaprakhariitr · ⭐ = empty-quadrant / highest-conviction pick.

Ver o original no GitHub

Bom para

Relacionados