track_package

4 registry entries were observed exposing a tool named track_package — none of them flagged as a privileged capability.

Every row is point-in-time scan output, dated below. Forge has an observed tool surface for 8,491 of 26,663 scannable entries (32%) — an entry that has not been scanned cannot appear here, so absence from this list is not evidence that an entry does not expose this tool.

1. 24htrack-mcp
   trust 60/100 · BMCP serverobserved 2026-08-09 · static extraction
   MCP server for 24hTrack — track packages across 3,200+ carriers (USPS, UPS, FedEx, DHL, China Post, UniUni, SpeedX and more). Multi-carrier
2. @codespar/mcp-correios
   trust 60/100 · BMCP serverobserved 2026-08-10 · static extraction
   MCP server for Correios — package tracking, shipping rates, CEP lookup
3. @vayacore/mcp
   trust 60/100 · BMCP serverobserved 2026-08-10 · static extraction
   Model Context Protocol server for VayaPin — VayaPin pin resolution, Google Maps, and AfterShip tools over a single MCP namespace, future-pro
4. io.github.guptaprakhariitr/multi-carrier-tracking-mcp
   trust 60/100 · BMCP serverobserved 2026-06-14 · static extraction
   Auto-detect carrier from tracking number: USPS, UPS, FedEx, DHL, India Post, more.

All indexed toolsSearch the registry for track_package