
Ship24 Tracking
io.github.ship24-officialPublished by GitHub account ship24-officialv1.0.0Updated Oct 28, 2026
Track any parcel by tracking number — real-time status, event history, and carrier detection.
The publisher's own server: Ship24 Tracking
Overview
Ship24 Tracking lets an assistant look up parcel tracking numbers for real-time status, event history and carrier detection via the Ship24 API.
- What you can do
- Track parcels by tracking number, retrieving current status and event history.
- Detect the carrier automatically from a tracking number.
- List available couriers, cached locally for a configurable period.
- Choose between per-call search and per-shipment tracker endpoints depending on the subscription plan.
- When to use it
- Useful when you want an assistant to answer questions about shipments, delivery progress or carrier identification without opening a tracking website. Suited to support, order-status and logistics workflows that already rely on Ship24.
- Requirements
- Runs locally as an npm package over stdio, so Node.js is needed. Requires a Ship24 API key in SHIP24_API_KEY. Optional variables set the plan mode (PLAN_PER_CALL, PLAN_PER_SHIPMENT), request timeout, courier cache lifetime and API base URL. Network access to the Ship24 API is required.
Installation
In SourceWeft
- Open Ship24 Tracking in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
25% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.