com.ship24/tracking-mcp

MCPcommunitylive
v1.0.1com.ship24UnknownUpdated 18d ago

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

Endpoint healthlive
checked 16h ago · 99ms
100% of the last 4 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
18d agoLast update
Package
Authorcom.ship24
LicenseUnknown
Version1.0.1
Sourcemcp-registry
Trust Status
B
60/100Good
Listed in Forge index+10/10
Publisher identity verified+0/30
Publisher: this listing has no repository on file, so `forge publish` cannot verify ownership automatically. Use "Claim this listing" above — Forge reviews these by hand.
Domain verification+0/10
Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
Prompt-injection scan · clean+30/30
Obfuscation / exfil scan · clean+20/20
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain
Provenance
DependenciesNot audited
Tool surface12 tools · none privileged
Security scan✓ Cleanvlive · todayHow well does this scan work?
EvalsNone
IndexedJul 17, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

12 tools · none privileged
Observed live from the vendor's endpoint16h ago

Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.

  • https://api.ship24.com/mcp12 tools · 99ms
create_trackerCreates 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. Subs…

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. Subs…

ParameterTypeDescription
trackingNumber*stringTracking number to monitor.
shipmentReferencestringInternal reference for the shipment.
clientTrackerIdstringYour unique identifier for this tracker, for lookup via searchBy=clientTrackerId.
originCountryCodestringOrigin country code (ISO alpha-2, e.g. US).
destinationCountryCodestringDestination country code (ISO alpha-2).
destinationPostCodestringDestination postal/ZIP code.
shippingDatestringDate the package was shipped (YYYY-MM-DD or ISO 8601).
courierCodearrayCourier codes for this tracker (max 3). Use get_couriers for valid codes. IMPORTANT: Check each courier's requiredFields array — any listed fields should be pr…
courierNamestringCourier name (informational).
trackingUrlstringCourier tracking URL.
orderNumberstringAssociated order number.
settingsobject
list_trackersReturns a paginated list of all trackers. Supports offset (page/limit) or cursor-based pagination. Filter by subscription status with isSubscribed.

Returns a paginated list of all trackers. Supports offset (page/limit) or cursor-based pagination. Filter by subscription status with isSubscribed.

ParameterTypeDescription
pageintegerPage number (1-indexed).
limitintegerResults per page (max 500).
sortSort order by createdAt. 1 = ascending (oldest first, default), -1 = descending (newest first).
bulk_create_trackersCreates 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 pe…

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 pe…

ParameterTypeDescription
trackers*arrayArray of tracker objects to create (minimum 1, maximum 100).
trackCreates 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 pendin…

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 pendin…

ParameterTypeDescription
trackingNumber*string
shipmentReferencestring
clientTrackerIdstring
originCountryCodestring
destinationCountryCodestring
destinationPostCodestring
shippingDatestring
courierCodearrayCourier codes for this tracker (max 3). Use get_couriers for valid codes. IMPORTANT: Check each courier's requiredFields array — any listed fields should be pr…
courierNamestring
trackingUrlstring
orderNumberstring
settingsobject
get_trackerRetrieves a single tracker by trackerId (or clientTrackerId when searchBy is set). Returns tracker metadata only — use get_tracking_results for events and status.

Retrieves a single tracker by trackerId (or clientTrackerId when searchBy is set). Returns tracker metadata only — use get_tracking_results for events and status.

ParameterTypeDescription
trackerId*stringShip24 trackerId, or clientTrackerId when searchBy="clientTrackerId".
searchBystringHow to interpret trackerId: default is Ship24 trackerId, use "clientTrackerId" for your own reference.
update_trackerPartially updates a tracker (PATCH). Only provided fields are changed. Common uses: toggling isSubscribed, correcting destination details, or setting a clientTrackerId.

Partially updates a tracker (PATCH). Only provided fields are changed. Common uses: toggling isSubscribed, correcting destination details, or setting a clientTrackerId.

ParameterTypeDescription
trackerId*stringThe tracker to update (Ship24 trackerId or clientTrackerId).
searchBystringHow to interpret trackerId: default is Ship24 trackerId, use "clientTrackerId" for your own reference.
isSubscribedbooleantrue to subscribe to webhooks, false to unsubscribe.
courierCodearrayCourier codes for this tracker (max 3). Use get_couriers for valid codes. IMPORTANT: Check each courier's requiredFields array — any listed fields should be pr…
originCountryCodestringOrigin country code (ISO alpha-2). Immutable once tracking data exists.
destinationCountryCodestringDestination country code (ISO alpha-2). Immutable once tracking data exists.
destinationPostCodestring
shippingDatestringShip date (YYYY-MM-DD or ISO 8601). Immutable once tracking data exists.
settingsobject
get_tracking_resultsReturns 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 | avail…

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 | avail…

ParameterTypeDescription
trackerId*stringShip24 trackerId, or clientTrackerId when searchBy="clientTrackerId".
searchBystringHow to interpret trackerId: default is Ship24 trackerId, use "clientTrackerId" for your own reference.
search_tracking_by_numberReturns 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…

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…

ParameterTypeDescription
trackingNumber*stringThe raw shipment tracking number to search for (e.g. 1Z999AA10123456784).
get_couriersReturns 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 tr…

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 tr…

No input schema was published for this tool.

search_trackingDefault 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_subsc…

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_subsc…

ParameterTypeDescription
trackingNumber*stringTracking number to look up. 5-50 alphanumeric characters, hyphens, underscores, dots, or slashes.
originCountryCodestringOrigin country code (ISO alpha-2).
destinationCountryCodestringDestination country code (ISO alpha-2).
destinationPostCodestringDestination postal/ZIP code.
shippingDatestringDate the package was shipped (YYYY-MM-DD or ISO 8601).
courierCodearrayCourier codes for this tracker (max 3). Use get_couriers for valid codes. IMPORTANT: Check each courier's requiredFields array — any listed fields should be pr…
resend_webhooksReplays 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 qui…

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 qui…

ParameterTypeDescription
trackerId*stringShip24 trackerId, or clientTrackerId when searchBy="clientTrackerId".
searchBystringHow to interpret trackerId: default is Ship24 trackerId, use "clientTrackerId" for your own reference.
download_webhook_historyRetrieves 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 responseStatus…

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 responseStatus…

ParameterTypeDescription
trackerId*stringShip24 trackerId, or clientTrackerId when searchBy="clientTrackerId".
searchBystringHow to interpret trackerId: default is Ship24 trackerId, use "clientTrackerId" for your own reference.

12 of 12 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

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

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.