Ship24 Order Tracking
https://server.smithery.ai/ship24/tracking/mcp# Ship24 Order Tracking Track parcels across **2,500+ carriers and 3PLs worldwide** — create trackers, pull live delivery status and full event history, search couriers, and replay webhook deliveries, all from one MCP server backed by the [Ship24](https://www.ship24.com) tracking API. No account is required to explore the server: every tool is discoverable and its schema readable with no API key. You only need a key ([get one free](https://dashboard.ship24.com/integrations/api-keys)) once you want a tool to actually return tracking data. ## What you can do with it - **Track a shipment in one call.** Give it a tracking number and get back current status, full event history, and delivery estimates — no need to know the carrier in advance. Ship24 auto-detects the courier from 2,500+ supported carriers and postal operators. - **Manage trackers at scale.** Create trackers one at a time or in bulk, list and paginate through everything on the account, update tracker settings, or look one up by your own reference ID instead of the tracking number. - **Search without creating a tracker.** Run a one-off lookup or search by tracking number when you just want an answer, not a persistent tracker. - **Look up courier metadata.** Get the full list of supported couriers, their codes, and what additional fields (postcode, country, account number) each one needs for accurate tracking. - **Debug and replay webhooks.** Pull the full webhook delivery history for a tracker, or trigger a resend if your endpoint missed a push. ## Tools (12) | Tool | What it does | |---|---| | `create_tracker` | Register a new tracker for a tracking number and start monitoring it. | | `list_trackers` | List and paginate trackers on the account. | | `bulk_create_trackers` | Create many trackers in a single call, with per-item success/error reporting. | | `track` | Create a tracker and return its tracking results in one round trip. | | `get_tracker` | Fetch a single tracker by ID. | | `update_tracker` | Update a tracker's reference, settings, or subscription state. | | `get_tracking_results` | Full event history and delivery statistics for a tracker. | | `search_tracking_by_number` | Look up existing tracking results by tracking number, no tracker ID needed. | | `search_tracking` | One-off tracking lookup without creating a persistent tracker. | | `get_couriers` | List all supported couriers, their codes, and required fields. | | `resend_webhooks` | Replay webhook deliveries for a tracker. | | `download_webhook_history` | Full webhook push history for a tracker, newest first. | ## Example prompts - *"Track this DHL package: 1234567890 and tell me if it's delayed."* - *"Create trackers for these 40 order numbers and flag any that fail."* - *"What couriers does Ship24 support in Germany, and which ones need a postcode to track accurately?"* - *"Show me the full delivery history for tracker `abc123`, including every status change."* - *"Did the webhook for order #4471 actually get delivered to our endpoint? Show me the last few pushes."* ## Authentication Connect with your Ship24 API key (starts with `apik_`) — paste it into the `ship24ApiKey` field when configuring the connection. Leave it blank to browse the tool list first; a key is only required once a tool needs to return real data. Keys are issued from the [Ship24 dashboard](https://dashboard.ship24.com/integrations/api-keys). ## Links - Docs: [docs.ship24.com](https://docs.ship24.com) - API reference: [docs.ship24.com/api-reference](https://docs.ship24.com/api-reference) - Get an API key: [dashboard.ship24.com/integrations/api-keys](https://dashboard.ship24.com/integrations/api-keys)
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B, 74.8/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 25/25 | Endpoint answers the MCP initialize handshake (1690 ms). |
| Protocol revision | 8/10 | Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 30/30 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 12 tool(s) with descriptions. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 0/5 | not seen in a source for over 30 days. |
| Auth declaration | 2/5 | Declares credential scheme: smithery_api_key. |
Compared with peers
Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 60% of peers
- This listing 83 · peer median 81
- Latency
- Faster than 29% of peers
- This listing 517 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
- Freshness + modern flags −5
— Keep the listing current in the registry or source it comes from.
Now: not seen in a source for over 30 days.
- Auth declaration −3
— State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
Listed in
Directories this entry was found in.
How to connect
https://server.smithery.ai/ship24/tracking/mcpcurl -X POST https://server.smithery.ai/ship24/tracking/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'