# Ship24 Tracking Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Ship24 Tracking

Track packages across 2,500+ carriers with live delivery status and event history.

- Record: https://musedirectory.ai/connector/ship24-tracking
- Category: Shopping & Commerce
- Developer: Ship24 (https://docs.ship24.com)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 1938ms, checked 2026-09-28T07:31:09Z
- Endpoint: https://api.ship24.com/mcp
- Auth: Needs an access key; Pricing: unknown
- Screening: Screened, no issues found (2026-09-24T19:26:04Z)
- Source: Found in the official MCP Registry (com.ship24/tracking-mcp) https://registry.modelcontextprotocol.io/v0/servers?search=com.ship24%2Ftracking-mcp

Connects to Ship24's tracking service to monitor shipments across 2,500+ carriers and 3PLs. Muse can look up tracking numbers, get delivery status and event history, set up ongoing monitoring, and retrieve webhook notifications for package updates.

Example request: "Where is my package and when will it arrive?"

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Ship24 Tracking to help me. It is a free service with an MCP server at https://api.ship24.com/mcp. It needs an API key from Ship24; ask me to enter it through your secure credential prompt. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- 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 crea
- list_trackers: Returns a paginated list of all trackers. Supports offset (page/limit) or cursor-based pagination. Filter by subscription status with isSubscribed.
- 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 fail
- 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 shipm
- 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.
- 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 | fai
- 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 u
- 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 hand
- 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 w
- 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 cal
- 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,

Screening checks:
- MCP handshake: pass (Answered in 864ms)
- Domain against threat feeds (Cloudflare security DNS): pass (api.ship24.com, docs.ship24.com not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (12 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (Domain registered 7675 days ago)
- AI review of purpose and tool behavior: pass (No concerns)