Ship24 Tracking
warningsapi.ship24.com
Ship24 tracking API as MCP tools: manage trackers, fetch results, list couriers.
https://api.ship24.com/mcpWebsiteNo authMCP 2025-11-25v1.0.0last checked 24 Aug 2026spoke MCP on 3 of 3 checks (30 days)initialize in 376 msHow to authenticate
Checked against the endpoint by our probe on 24 Aug 2026. These are the capabilities the server advertises, not a prediction about any particular client.
| Scheme | No auth |
|---|---|
| Protected-resource metadata | ✕Not found Without it a client has to guess where the authorization server lives. |
| Anonymous access | Handshake succeeds; 12 tools listable |
| Credentials demanded in prose | ✕search_tracking These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error. |
What the probe found
1 of the 12 tools listed anonymously say in their own descriptions that they need an account or a key (search_tracking), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.
A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.
Tools
Contract history
Get alerted when this contract changes
Depend on this server? Leave an email and get a message when a probe records a change — a tool removed, an argument newly required, an enum narrowed. Alerts are being built; signing up is what tells us to hurry.
Prefer a feed reader? This page's contract changes are also an Atom feed.
Status badge
Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.
[](https://mcpi.app/servers/ship24-tracking)Own this server?
Sign in to claim this listing by proving control of the endpoint.