mcpbeat Sign in

Ship24 Tracking MCP Server

by ship24 Your server? Claim it
answering

Ship24 Tracking is answering right now. Last checked 9 min ago. It exposes 12 tools.

Track parcels across 2,500+ carriers and 3PLs: live delivery status, event history, carrier lookup.

Uptime history 91 days of history
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
12
Tools
read from the server
400 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 27 August 2026. No other catalogue keeps this.

27 Aug a tool changed version

Nothing serious here today

Today is the operative word: we check Ship24 Tracking every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add tracking-mcp --transport http https://api.ship24.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://api.ship24.com/mcp
~/.codex/config.toml
[mcp_servers.tracking-mcp]
url = "https://api.ship24.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "tracking-mcp": {
      "url": "https://api.ship24.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "tracking-mcp": {
      "type": "http",
      "url": "https://api.ship24.com/mcp"
    }
  }
}

Available tools 12

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

tracker
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_tracking. Idempotent: same parameters reuse the existing tracker; any field change creates a new one. Subscribes to webhook updates if configured. Returns the created tracker including its Ship24 trackerId.
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.
update_tracker
Partially updates a tracker (PATCH). Only provided fields are changed. Common uses: toggling isSubscribed, correcting destination details, or setting a clientTrackerId.
tracking
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. statusMilestone values: pending | info_received | in_transit | out_for_delivery | failed_attempt | available_for_pickup | delivered | exception.
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 on the account. Billed per call. Requires an active per-call plan — if it fails with no_active_subscription, use the track tool instead.
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. Responds 404 tracker_not_found if no tracker exists for that number — in that case use search_tracking (per-call) or track (per-shipment). Use this first when a tracker may already exist.
bulk
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 partially create trackers. Returns counts of created, ignored (duplicate), and failed trackers plus per-item details.
couriers
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 values before creating or updating trackers, or to help identify which courier handles a particular tracking number format. Note: this endpoint has a rate limit of 1 request/second; cache results when possible.
download
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 failed pushes with status, pushTimestamp, requestBody, responseBody, responseHeaders, and responseStatusCode. Pending (unsent) webhooks are excluded. Results are sorted newest first. Rate-limited to 1 request/second per tracker.
resend
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 existing webhook payload records before regenerating and resending them — do not call repeatedly in quick succession. Rate-limited to 1 request/second per tracker.
track
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_tracking for one-off lookups when the per-call plan is available. If the returned shipment is still pending with no events, call get_tracking_results once with the returned trackerId before answering. Accepts the same fields as create_tracker — see that tool for field details.
trackers
list_trackers
Returns a paginated list of all trackers. Supports offset (page/limit) or cursor-based pagination. Filter by subscription status with isSubscribed.

Endpoints

URLTransportStateLatencyChecked
https://api.ship24.com/mcp streamable-http answering 400 ms 9 min ago

Alternatives to Ship24 Tracking

same job, measured the same way
S
Ship24 Tracking
by ship24-official

Track any parcel by tracking number — real-time status, event history, and carrier detection.

local only
Tracking & Returns
by aftership-mcp

Track packages across 1,300+ global carriers with real-time status and AI-powered delivery dates.

2 tools answering
17TRACK MCP by usefulapi
by usefulapi

Track parcels across 3000+ carriers with 17TRACK: register numbers, read tracking events and quota.

9 tools answering
TrackingMore MCP by usefulapi
by usefulapi

Track parcels with TrackingMore: detect couriers, create and read trackings, delivery status.

7 tools answering
PackZoo
by iafanasov

Compare parcel and letter delivery prices across 60+ carriers in 27 European countries.

2 tools answering
Zhiyong Parcel Tracking
by zhiyong

Track parcel status and scan history; currently supports UniUni only.

1 tools answering
Australia Post MCP by UnClick
by malamutemayhem

Australia Post parcel tracking, postcode lookup, and delivery times. By UnClick.

42 installs/wk local only
ShipSmarter Shipping
by mescolis

Track parcels, compare live carrier rates and find drop-off points for online sellers.

8 tools answering

Ship24 Tracking — questions

Answers built from our own checks of this server.

What can Ship24 Tracking do?
It exposes 12 tools, read directly from the server on our last check. Among them: bulk_create_trackers, create_tracker, download_webhook_history, get_couriers, get_tracker, get_tracking_results and 6 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Ship24 Tracking mostly used for?
Its tools cluster around tracker and tracking. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Ship24 Tracking working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 400 ms. The bar chart above shows every period we have measured.
How do I connect Ship24 Tracking?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Ship24 Tracking need an API key?
No. Ship24 Tracking completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 12 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Ship24 Tracking?
It answers our handshake in 400 ms on average, which is faster than 33% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.