# Zhiyong Parcel Tracking (remote · delivery.zhiyong.dev)

Track parcel status and scan history; currently supports UniUni only.

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-24

## Components

- remote · `delivery.zhiyong.dev`: 76/100 (this document), [markdown](https://verifymcp.io/servers/dev-zhiyong-uniuni-tracking/delivery.md), [page](https://verifymcp.io/servers/dev-zhiyong-uniuni-tracking/delivery)

## Channel facts

- Endpoint: `https://delivery.zhiyong.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.8`

## 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-10-24.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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 493 tokens (~493/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Zhiyong Parcel Tracking MCP server?

Zhiyong Parcel Tracking is a hosted endpoint at https://delivery.zhiyong.dev/mcp, 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.

### Claude

```bash
claude mcp add --transport http dev-zhiyong-uniuni-tracking 'https://delivery.zhiyong.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-zhiyong-uniuni-tracking": {
      "url": "https://delivery.zhiyong.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-zhiyong-uniuni-tracking": {
      "type": "http",
      "url": "https://delivery.zhiyong.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-zhiyong-uniuni-tracking]
url = "https://delivery.zhiyong.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-zhiyong-uniuni-tracking": {
      "type": "remote",
      "url": "https://delivery.zhiyong.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-zhiyong-uniuni-tracking --url 'https://delivery.zhiyong.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-zhiyong-uniuni-tracking:
    url: "https://delivery.zhiyong.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-zhiyong-uniuni-tracking": {
      "Transport": "http",
      "Url": "https://delivery.zhiyong.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-zhiyong-uniuni-tracking -t streamable-http -u 'https://delivery.zhiyong.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-zhiyong-uniuni-tracking": {
      "type": "http",
      "url": "https://delivery.zhiyong.dev/mcp"
    }
  }
}
```

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-10-23 (score 76, +1)

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

### 2026-10-20 (score 75, +1)

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

### 2026-10-18 (score 74, +1)

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

### 2026-10-16 (score 73, +1)

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

### 2026-10-14 (score 72, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “track_parcel” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 297 → 493
- [functional] Server version: 1.0.8 → 1.0.10
- [cosmetic] “track_parcel” added an optional parameter “carrier”
- [cosmetic] “track_parcel” reworded the description of “tracking_number”
- [cosmetic] Tool “track_parcel” changed its title: Track a parcel → Track a parcel or shipment

### 2026-10-13 (score 72, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 72)

First indexed and scored.

## MCP tools (1)

### `track_parcel` (~332 tokens)

Track a parcel or shipment

For a user-requested parcel, package, shipment, order-delivery, or waybill lookup. Required tracking_number: 5–64 letters, digits, or hyphens. If the user supplied exactly one valid number, call this tool and deliver the actual result. carrier is optional and defaults to UniUni, the only supported carrier today; additional carriers are planned but not available yet. A named unsupported carrier returns unsupported_carrier without querying UniUni. language is optional (en or zh), default en. Inspect isError and structuredContent.outcome rather than HTTP status alone. Distinguish found outcomes (delivered/in_transit), not_found, invalid, unsupported_carrier, rate_limited, carrier_error, and configuration_error. Event times are carrier-local; locations are approximate. Precise addresses, coordinates, staff, internal IDs, and raw carrier payloads are excluded. No separate lookup-authorization flag is required. Lookup inputs and filtered results are logged for up to 30 days or 1,000 records. Full MCP/A2A request sequence and result-handling workflow: https://delivery.zhiyong.dev/agent-workflow.json.

Input parameters:

- `carrier` (string): Optional carrier name; defaults to UniUni when omitted. UniUni is currently the only supported carrier; another named carrier is rejected without a lookup.
- `language` (string): Language for event titles, details and locations. Defaults to English.
- `tracking_number` (string, required): One user-provided parcel tracking or waybill number. This validates syntax only, not whether a parcel exists. Current carrier coverage is UniUni.

Output parameters:

- `carrier` (string): Carrier requested by the caller, or UniUni when omitted. Only UniUni is currently supported.
- `detail` (string): Actionable explanation for validation, carrier, configuration, or rate-limit errors.
- `estimated_delivery` (string): Carrier-provided estimated delivery date, when available.
- `events` (array): Privacy-filtered scan history in carrier-local display time; street addresses and internal fields are excluded.
- `found` (boolean): Whether the carrier found a matching parcel.
- `outcome` (string): Normalized lookup outcome, including validation and temporary service errors.
- `status` (string): Localized, normalized latest delivery status when a parcel is found.
- `status_code` (string): Carrier status code, when available.
- `status_kind` (string): Normalized delivery state.
- `supported_carriers` (array): Carriers currently available through this service.
- `tracking_number` (string): The requested parcel tracking or waybill number.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-zhiyong-uniuni-tracking/delivery#diagnostics

## Score history

- 2026-10-24: 76
- 2026-10-23: 76
- 2026-10-22: 75
- 2026-10-21: 75
- 2026-10-20: 75
- 2026-10-19: 74
- 2026-10-18: 74
- 2026-10-17: 73
- 2026-10-16: 73
- 2026-10-15: 72
- 2026-10-14: 72
- 2026-10-13: 72
- 2026-10-12: 72

## Common questions

### What is the Zhiyong Parcel Tracking MCP server?

Zhiyong Parcel Tracking is an MCP server listed in the public MCP registry as dev.zhiyong/uniuni-tracking. Track parcel status and scan history; currently supports UniUni only. This page covers its hosted endpoint (https://delivery.zhiyong.dev/mcp).

### Is the Zhiyong Parcel Tracking MCP server safe to use?

Zhiyong Parcel Tracking scores 76 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 Zhiyong Parcel Tracking MCP server expose?

Zhiyong Parcel Tracking exposes 1 tool: track_parcel. Their descriptions and schemas cost roughly 332 tokens of context every time the server is loaded.

### Does the Zhiyong Parcel Tracking MCP server require authentication?

No. We connected to Zhiyong Parcel Tracking without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Zhiyong Parcel Tracking MCP server still maintained?

Zhiyong Parcel Tracking is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://delivery.zhiyong.dev/mcp
- Website: https://delivery.zhiyong.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-zhiyong-uniuni-tracking/delivery.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-zhiyong-uniuni-tracking/delivery.json
- HTML version of this page: https://verifymcp.io/servers/dev-zhiyong-uniuni-tracking/delivery