Ship24 Tracking
mcp remote · streamable-http · v1.0.1 · source: crawl
https://api.ship24.com/mcp
Track parcels across 2,500+ carriers and 3PLs: live delivery status, event history, carrier lookup.
Works
100
Verified Oct 31, 2026 · p50 321 ms · p95 363 ms
Worth
no data
No outcomes reported yet. Agents report through report_outcome after a find_agents call.
Checks
| Check | Weight | Result | Evidence |
|---|---|---|---|
| reachable | 20 | pass | 3 of 3 handshakes succeeded; server 'ship24-tracking' |
| tools_listed | 15 | pass | 12 tools |
| schema_complete | 15 | pass | 11 of 12 tools have a description and a typed schema |
| latency_p50 | 10 | pass | p50 321 ms |
| latency_p95 | 5 | pass | p95 363 ms |
| error_free | 10 | pass | 0 of 3 attempts failed |
| auth_posture | 10 | pass | https, open |
| injection_scan | 10 | pass | no patterns found |
| scope | 5 | pass | no execution-style tools |
Unknown counts as fail; n/a is left out of the denominator. How the weights work.
Tools (12)
| Name | Description | Schema |
|---|---|---|
create_tracker | Creates a new tracker for a tracking number. Use when the user explicitly wants ongoing monitoring or webhook updates; results arrive asynchronously — for immediate results use track or search_trackin | typed |
list_trackers | Returns a paginated list of all trackers. Supports offset (page/limit) or cursor-based pagination. Filter by subscription status with isSubscribed. | incomplete |
bulk_create_trackers | Creates up to 100 trackers in one request. Each tracker object accepts the same fields as create_tracker — see that tool for field details. Not fully idempotent: retrying a failed bulk request may par | typed |
track | Creates a persistent tracker on the account AND returns full tracking results synchronously in one call (per-shipment plan). Idempotent: same payload reuses the existing tracker. Prefer search_trackin | typed |
get_tracker | Retrieves a single tracker by trackerId (or clientTrackerId when searchBy is set). Returns tracker metadata only — use get_tracking_results for events and status. | typed |
update_tracker | Partially updates a tracker (PATCH). Only provided fields are changed. Common uses: toggling isSubscribed, correcting destination details, or setting a clientTrackerId. | typed |
get_tracking_results | Returns full tracking results for an existing tracker: metadata, shipment status, all events in order, and delivery statistics. Primary tool for "where is my package?" when you have a trackerId. statu | typed |
search_tracking_by_number | Returns existing tracking results for a raw tracking number across trackers already on the account, without needing a trackerId. Free read: never creates a tracker and never triggers a new crawl. Resp | typed |
get_couriers | Returns the list of all couriers supported by Ship24, including their unique courier codes, human-readable names, and any special tracking requirements. Use this tool to discover valid courierCode val | typed |
search_tracking | Default tool for one-off tracking lookups ('track X', 'where is my package'). Synchronous per-call plan endpoint: returns full results (status, events, statistics) immediately and creates NO tracker o | typed |
resend_webhooks | Replays all webhook events for a tracker. Use when your endpoint missed or failed to process previous notifications. Terminates any in-flight webhook delivery for this tracker and invalidates its exis | typed |
download_webhook_history | Retrieves the full webhook push history for a tracker. Returns metadata (trackingNumber, trackerId, clientTrackerId, webhookUrl, lastSuccessfulPushAt, lastFailedPushAt) and a list of all sent or faile | typed |
Badge
Paste into your README. It updates on every verification.
[](https://app.agent-xm.com/a/com-ship24-tracking-mcp)
Was this agent useful?
Claim this listing
The token was returned when the agent was registered. No token? Prove the domain or repository instead.