Tracking & Returns
REMOTE · MCP.AFTERSHIP.COM · SCANNED SEP 20
Track packages across 1,300+ global carriers with real-time status and AI-powered delivery dates.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (get_returns_demo). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 496 tokens (~248/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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'
{
"mcpServers": {
"com-aftership-mcp-tracking-public": {
"url": "https://mcp.aftership.com/tracking/public"
}
}
} {
"servers": {
"com-aftership-mcp-tracking-public": {
"type": "http",
"url": "https://mcp.aftership.com/tracking/public"
}
}
} [mcp_servers.com-aftership-mcp-tracking-public] url = "https://mcp.aftership.com/tracking/public"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-aftership-mcp-tracking-public": {
"type": "remote",
"url": "https://mcp.aftership.com/tracking/public",
"enabled": true
}
}
} openclaw mcp add com-aftership-mcp-tracking-public --url 'https://mcp.aftership.com/tracking/public' --transport streamable-http
mcp_servers:
com-aftership-mcp-tracking-public:
url: "https://mcp.aftership.com/tracking/public" {
"McpServers": {
"com-aftership-mcp-tracking-public": {
"Transport": "http",
"Url": "https://mcp.aftership.com/tracking/public"
}
}
} assistant mcp add com-aftership-mcp-tracking-public -t streamable-http -u 'https://mcp.aftership.com/tracking/public'
{
"mcpServers": {
"com-aftership-mcp-tracking-public": {
"type": "http",
"url": "https://mcp.aftership.com/tracking/public"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
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 20 Sept 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=YE1,O=Let's Encrypt,C=US | 26 Aug 2026 | 24 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 62b3c557ae8e8dd82484acc38a12d1bb3ba |
| SANs: *.aftership.com, aftership.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| 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 | Verified | 200 | |
| http (plaintext) | http://mcp.aftership.com/tracking/public | HTTPS enforced |
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.
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 81 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?
No. We connected to Tracking & Returns without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.