Skip to content

Ship24 Tracking MCP server

com.ship24/tracking-mcpship24.comstreamable-httpv1.0.1Scanned

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

12 tools: 1 can delete or cancel things, 4 change things and 7 only read.

Tools: 1 delete, 0 irreversible, 4 write, 7 read.
  • Reads private data · 0
  • Reads text others write · 5
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Ship24 Tracking MCP server can do

The Ship24 Tracking MCP server is published by ship24.com, a domain the MCP Registry verified. It has 12 tools. It can delete or cancel things (1 tool: resend_webhooks) and create or change data (4 tools: create_tracker, bulk_create_trackers, track and update_tracker). 7 tools only read.

5 tools bring in text other people can write (create_tracker, bulk_create_trackers, track and 2 more); 1 tool can send data out of your system (resend_webhooks).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 14, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

12 tools

Deletes or cancels 1Claude Code: deny
  • resend_webhooksReplays all webhook events for a tracker.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "resend_webhooks" says "resend": a word for sending, and what is sent cannot be taken back.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "resend_webhooks" says "resend": it sends or publishes something to other people.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
Changes things 4Claude Code: ask
  • bulk_create_trackersCreates up to 100 trackers in one request.Reads text others writeNo findings

    Why it is in this group

    • The name "bulk_create_trackers" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • create_trackerCreates a new tracker for a tracking number.Reads text others writeNo findings

    Why it is in this group

    • The name "create_tracker" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • trackCreates a persistent tracker on the account AND returns full tracking results synchronously in one call (per-shipment plan).Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • update_trackerPartially updates a tracker (PATCH).No findings

    Why it is in this group

    • The name "update_tracker" says "update": a word for a change.
    Description, as the server wrote it
    Partially updates a tracker (PATCH). Only provided fields are changed. Common uses: toggling isSubscribed, correcting destination details, or setting a clientTrackerId.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 7Show 7 read-only tools
  • download_webhook_historyRetrieves the full webhook push history for a tracker.No findings

    Why it is in this group

    • The description's first verb is "retrieve": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_couriersReturns the list of all couriers supported by Ship24, including their unique courier codes, human-readable names, and any special tracking requirements.No findings

    Why it is in this group

    • The name "get_couriers" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_trackerRetrieves a single tracker by trackerId (or clientTrackerId when searchBy is set).No findings

    Why it is in this group

    • The name "get_tracker" says "get": a word for reading.
    Description, as the server wrote it
    Retrieves a single tracker by trackerId (or clientTrackerId when searchBy is set). Returns tracker metadata only — use get_tracking_results for events and status.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_tracking_resultsReturns full tracking results for an existing tracker: metadata, shipment status, all events in order, and delivery statistics.No findings

    Why it is in this group

    • The name "get_tracking_results" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • list_trackersReturns a paginated list of all trackers.No findings

    Why it is in this group

    • The name "list_trackers" says "list": a word for reading.
    Description, as the server wrote it
    Returns a paginated list of all trackers. Supports offset (page/limit) or cursor-based pagination. Filter by subscription status with isSubscribed.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • search_trackingDefault tool for one-off tracking lookups ('track X', 'where is my package').Reads text others writeNo findings

    Why it is in this group

    • The name "search_tracking" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • search_tracking_by_numberReturns existing tracking results for a raw tracking number across trackers already on the account, without needing a trackerId.No findings

    Why it is in this group

    • The name "search_tracking_by_number" says "search": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write5
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:46 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (1 destructive, 4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.ship24.com/mcp: tools/list returned 12 tools to an anonymous client, including resend_webhooks (destructive), create_tracker (write), bulk_create_trackers (write), track (write), update_tracker (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http tracking https://api.ship24.com/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http tracking https://api.ship24.com/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__tracking__list_trackers",
      "mcp__tracking__get_tracker",
      "mcp__tracking__get_tracking_results",
      "mcp__tracking__search_tracking_by_number",
      "mcp__tracking__get_couriers",
      "mcp__tracking__search_tracking",
      "mcp__tracking__download_webhook_history"
    ],
    "ask": [
      "mcp__tracking__create_tracker",
      "mcp__tracking__bulk_create_trackers",
      "mcp__tracking__track",
      "mcp__tracking__update_tracker"
    ],
    "deny": [
      "mcp__tracking__resend_webhooks"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as tracking. Review it before you use it.

Capability tags behind 5 rules
  • mcp__tracking__create_tracker untrusted-input
  • mcp__tracking__bulk_create_trackers untrusted-input
  • mcp__tracking__track untrusted-input
  • mcp__tracking__search_tracking untrusted-input
  • mcp__tracking__resend_webhooks untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.ship24/tracking-mcp/verify?hash=44d9b7001a888b383d5d92c01d96bee7aad5ac7a28bc049fd233db1fcbf35ca0" | jq -e '.changed == false'

Pinned hash 44d9b7001a88, from Nov 14, 2026, 08:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.ship24/tracking-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.ship24/tracking-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/com.ship24/tracking-mcp.svg)](https://radar.anlyon.com/servers/com.ship24/tracking-mcp)

Source: MCP Registry. Synced Oct 21, 2026, 18:04 UTC.

Ship24 Tracking MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Ship24 Tracking MCP server safe?

No scan can promise that. What its definitions show: 12 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Ship24 Tracking MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: resend_webhooks.

Can the Ship24 Tracking MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Ship24 Tracking MCP server have?

12 tools: 1 destructive, 4 write, 7 read. resend_webhooks, create_tracker, bulk_create_trackers, track, update_tracker, list_trackers, get_tracker, get_tracking_results and 4 more.

Does the Ship24 Tracking MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Ship24 Tracking MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): resend_webhooks.

Has the Ship24 Tracking MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 14, 2026.