# Tracking & Returns (remote · mcp.aftership.com)

Track packages across 1,300+ global carriers with real-time status and AI-powered delivery dates.

- Trust score: 66/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.aftership.com`: 66/100 (this document), [markdown](https://verifymcp.io/servers/com-aftership-mcp-tracking-public/tracking-public.md), [page](https://verifymcp.io/servers/com-aftership-mcp-tracking-public/tracking-public)

## Channel facts

- Endpoint: `https://mcp.aftership.com/tracking/public`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (get_returns_demo).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-aftership-mcp-tracking-public https://mcp.aftership.com/tracking/public
```

### Codex

```toml
[mcp_servers.com-aftership-mcp-tracking-public]
url = "https://mcp.aftership.com/tracking/public"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-aftership-mcp-tracking-public": {
      "type": "remote",
      "url": "https://mcp.aftership.com/tracking/public",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-aftership-mcp-tracking-public --url https://mcp.aftership.com/tracking/public --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-aftership-mcp-tracking-public:
    url: "https://mcp.aftership.com/tracking/public"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 65, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 63, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 61, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 61)

First indexed and scored.

## MCP tools (2)

### `get_returns_demo` (~219 tokens)

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.

Input parameters:

- `store_url` (string, required): 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.

### `track_shipment` (~277 tokens)

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.

Input parameters:

- `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, required): The tracking number of the shipment

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-aftership-mcp-tracking-public/tracking-public#diagnostics

## Score history

- 2026-08-03: 66
- 2026-08-02: 66
- 2026-08-01: 65
- 2026-07-31: 65
- 2026-07-30: 63
- 2026-07-29: 63
- 2026-07-28: 62
- 2026-07-27: 61
- 2026-07-26: 61

## Links

- Remote endpoint: https://mcp.aftership.com/tracking/public
- Changelog RSS feed: https://verifymcp.io/servers/com-aftership-mcp-tracking-public/tracking-public/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-aftership-mcp-tracking-public/tracking-public/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-aftership-mcp-tracking-public/tracking-public