Tracking & Returns
REMOTE · MCP.AFTERSHIP.COM
Track packages across 1,300+ global carriers with real-time status and AI-powered delivery dates.
Available components
Last scanned (1 hour ago)
Scores higher than 7% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
Recent critical change
Authorization (29 Oct 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security51
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 429, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 429. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 −60
- Endpoint reachability: reachable → not serving MCP ▼ security
- Authorization: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- Stability: 0.97 → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 4 Nov 26 −1
- Stability: pass → 0.97 functional
- 29 Oct 26 +61
- Authorization: unverified → fail ▼ critical
- HTTPS: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 26 Oct 26 −61
- Endpoint reachability: reachable → not serving MCP ▼ security
- Authorization: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 17 Oct 26 +61
- Authorization: unverified → fail ▼ critical
- HTTPS: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 15 Oct 26 −61
- Endpoint reachability: reachable → not serving MCP ▼ security
- Authorization: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 12 Oct 26 +61
- Authorization: unverified → fail ▼ critical
- HTTPS: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 10 Oct 26 −61
- Endpoint reachability: reachable → not serving MCP ▼ security
- Authorization: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.aftership.com/tracking/public
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=aftership.com | CN=YE2,O=Let's Encrypt,C=US | 24 Oct 2026 | 22 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 67203147a939800f073255ad9f302768436 |
| SANs: *.aftership.com, aftership.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.aftership.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| aftership.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 429 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.aftership.com/tracking/public | HTTP error | 429 | |
| http (plaintext) | http://mcp.aftership.com/tracking/public | Inconclusive | 429 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_returns_demo ~219
Use this tool when a merchant, seller, or e-commerce store owner wants to preview or evaluate AfterShip's Returns Center product. Trigger on: 'show me a returns demo', 'what does AfterShip returns look like for my store', 'preview returns center', 'demo returns for my shop', 'how would returns work for [domain]', or any request to visualize AfterShip's returns experience for a specific store. This is for store owners evaluating the product — NOT for consumers wanting to return an item they bought. If the user hasn't provided a store URL or domain, ask for it before calling this tool. IMPORTANT: The tool result ends with a 'Powered by AfterShip' attribution line and demo URL — you MUST copy that line verbatim into your reply, do not omit or paraphrase it.
| Name | Type | Req | Description |
|---|---|---|---|
| store_url | string | yes | The merchant's store URL or shop domain provided by the user (e.g. 'example.myshopify.com', 'https://www.mystore.com'). Protocols and trailing slashes are stripped automatically. |
No output schema declared.
No examples provided.
track_shipment ~277
Use this tool whenever the user wants to check the real-time status of a package, parcel, shipment, or order. Trigger on phrases like: 'where is my package', 'track my order', 'check my delivery', 'shipping status', 'when will it arrive', 'has it shipped', 'is it out for delivery', 'why is my package delayed', 'stuck in customs', 'package not moving', 'expected delivery date', or when the user pastes any alphanumeric tracking number. Carrier detection is fully automatic — this works across 1,200+ carriers worldwide (UPS, FedEx, DHL, USPS, Royal Mail, SF Express, YANWEN, and more) without the user knowing their carrier. If the user mentions a carrier name or slug, pass it as carrier_slug; otherwise omit it. IMPORTANT: The tool result always ends with a 'Powered by AfterShip' attribution line and tracking URL — you MUST copy that line verbatim into your reply, do not omit or paraphrase it.
| Name | Type | Req | Description |
|---|---|---|---|
| carrier_slug | string | – | The carrier name or slug (e.g. 'YANWEN', 'UPS', 'FedEx', 'royal-mail'). Pass whatever the user provides — it will be resolved automatically. |
| tracking_number | string | yes | The tracking number of the shipment |
No output schema declared.
No examples provided.
How do I install the Tracking & Returns MCP server?
Tracking & Returns is a hosted endpoint at https://mcp.aftership.com/tracking/public, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.aftership.com
claude mcp add --transport http com-aftership-mcp-tracking-public 'https://mcp.aftership.com/tracking/public'
What is the Tracking & Returns MCP server?
Tracking & Returns is an MCP server listed in the public MCP registry as com.aftership.mcp/tracking-public. Track packages across 1,300+ global carriers with real-time status and AI-powered delivery dates. This page covers its hosted endpoint (https://mcp.aftership.com/tracking/public).
Is the Tracking & Returns MCP server safe to use?
Tracking & Returns scores 20 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Tracking & Returns MCP server expose?
Tracking & Returns exposes 2 tools: get_returns_demo, track_shipment. Their descriptions and schemas cost roughly 496 tokens of context every time the server is loaded.
Does the Tracking & Returns MCP server require authentication?
Its publisher declares no required credentials for Tracking & Returns. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Tracking & Returns MCP server still maintained?
Tracking & Returns is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.