Connect Ship24 Tracking and your agent gets 12 tools, among them bulk_create_trackers, create_tracker, download_webhook_history. It answers at https://api.ship24.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 10 September 2026; the last check, on 19 October 2026, succeeded.
Track parcels across 2,500+ carriers and 3PLs: live delivery status, event history, carrier lookup.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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 o Inputs: trackers |
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 Inputs: trackingNumber, shipmentReference, clientTrackerId, originCountryCode, destinationCountryCode, destinationPostCode |
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, req Inputs: trackerId, searchBy |
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 |
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. Inputs: trackerId, searchBy |
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_receiv Inputs: trackerId, searchBy |
list_trackers | Returns a paginated list of all trackers. Supports offset (page/limit) or cursor-based pagination. Filter by subscription status with isSubscribed. Inputs: page, limit, sort |
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 rege Inputs: trackerId, searchBy |
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 Inputs: trackingNumber, originCountryCode, destinationCountryCode, destinationPostCode, shippingDate, courierCode |
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 Inputs: trackingNumber |
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 Inputs: trackingNumber, shipmentReference, clientTrackerId, originCountryCode, destinationCountryCode, destinationPostCode |
update_tracker | Partially updates a tracker (PATCH). Only provided fields are changed. Common uses: toggling isSubscribed, correcting destination details, or setting a clientTrackerId. Inputs: trackerId, searchBy, isSubscribed, courierCode, originCountryCode, destinationCountryCode |
Every block below points at https://api.ship24.com/mcp. Pick your client and copy.
claude mcp add --transport http ship24-tracking https://api.ship24.com/mcp
{
"mcpServers": {
"ship24-tracking": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.ship24.com/mcp"]
}
}
}{
"mcpServers": {
"ship24-tracking": {
"url": "https://api.ship24.com/mcp"
}
}
}{
"servers": {
"ship24-tracking": {
"type": "http",
"url": "https://api.ship24.com/mcp"
}
}
}{
"context_servers": {
"ship24-tracking": {
"url": "https://api.ship24.com/mcp"
}
}
}{
"mcpServers": {
"ship24-tracking": {
"serverUrl": "https://api.ship24.com/mcp"
}
}
}{
"mcpServers": {
"ship24-tracking": {
"url": "https://api.ship24.com/mcp"
}
}
}name: Ship24 Tracking
version: 0.0.1
schema: v1
mcpServers:
- name: Ship24 Tracking
type: streamable-http
url: https://api.ship24.com/mcp{
"mcpServers": {
"ship24-tracking": {
"httpUrl": "https://api.ship24.com/mcp"
}
}
}{
"mcpServers": {
"ship24-tracking": {
"type": "http",
"url": "https://api.ship24.com/mcp"
}
}
}{
"mcpServers": {
"ship24-tracking": {
"url": "https://api.ship24.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fapi.ship24.com%2Fmcp&type=streamable_http&id=ship24-tracking&name=Ship24%20Tracking
It answered our last check on 19 October 2026 in 350 ms. Over 6 checks since 10 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by ship24.com and served from api.ship24.com, the vendor's own domain: https://api.ship24.com/mcp.
12, as returned by the server's own tools/list on 11 September 2026: bulk_create_trackers, create_tracker, download_webhook_history, get_couriers, get_tracker, get_tracking_results, list_trackers, resend_webhooks, and 4 more.
It answered our last check on 19 October 2026 in 350 ms. Over 6 checks since 10 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://api.ship24.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.ship24. Endpoint host: api.ship24.com. ARD identifier: urn:air:com.ship24:mcp:tracking-mcp.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.