Looks up a parcel's status, courier and event history from a tracking code via spokepackagetracker.com, and identifies which courier issued a code.
What you can do
Track one package from its tracking code: current status, courier, dates, event history and a link to its page
Identify which couriers may have issued a given tracking code, returning their IDs and names
Resolve ambiguity by returning courier candidates or required fields for the assistant to ask the user about
When to use it
Useful when a user has a shipment tracking code and wants its current status or delivery history, or wants to know which courier a code belongs to. It is meant for single, user-supplied shipments rather than bulk tracking.
Requirements
A remote streamable HTTP endpoint at spokepackagetracker.com; no packages, environment variables, headers or authentication are declared. Network access to that host is needed.
Before you install
Tracking codes are sent to spokepackagetracker.com. The server instructs assistants to track only shipments the user sends or expects, one per call, never in bulk, and not to guess postal codes, countries or statuses; replies should link to the returned tracking page. Usage limits apply and should not be retried automatically.
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/com.spokepackagetracker%2Fpackage-tracker/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.
Gets one package's current status, courier, dates and event history from its tracking code, as spokepackagetracker.com shows them, with a link to that page. Without carrierId, it identifies the courier first: one match is tracked, several are returned as candidates without tracking, and none tries every tracking provider. Some couriers need the destination postal code or country, and the result lists them when they're missing. Every result has a trackingUrl; share it as a link in your reply so the user can follow the package.
Identifies which couriers may have issued a package tracking code, from the code's format and a courier database. Returns each matching courier's ID and name, or an empty list when none matches. Does not look up the package's status.
ParameterstrackingCoderequired
Version history
1
v1.0.0LatestNov 7, 2026
Score
72%
72% 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
Publish an icon in the registry entry.
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.