# cn.pianam/express-mcp (remote · pianam.cn)

MCP server for Chinese express delivery tracking: query parcel status by tracking number across

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

## Components

- remote · `pianam.cn`: 73/100 (this document), [markdown](https://verifymcp.io/servers/cn-pianam-express-mcp/express-mcp-mcp.md), [page](https://verifymcp.io/servers/cn-pianam-express-mcp/express-mcp-mcp)

## Channel facts

- Endpoint: `https://pianam.cn/express-mcp/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - 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**: 78/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 478 tokens (~159/item across 3 items; 3 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the cn.pianam/express-mcp server?

cn.pianam/express-mcp is a hosted endpoint at https://pianam.cn/express-mcp/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 cn-pianam-express-mcp 'https://pianam.cn/express-mcp/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "cn-pianam-express-mcp": {
      "url": "https://pianam.cn/express-mcp/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cn-pianam-express-mcp": {
      "type": "http",
      "url": "https://pianam.cn/express-mcp/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.cn-pianam-express-mcp]
url = "https://pianam.cn/express-mcp/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cn-pianam-express-mcp": {
      "type": "remote",
      "url": "https://pianam.cn/express-mcp/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cn-pianam-express-mcp --url 'https://pianam.cn/express-mcp/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  cn-pianam-express-mcp:
    url: "https://pianam.cn/express-mcp/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "cn-pianam-express-mcp": {
      "Transport": "http",
      "Url": "https://pianam.cn/express-mcp/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add cn-pianam-express-mcp -t streamable-http -u 'https://pianam.cn/express-mcp/mcp'
```

### Other

```json
{
  "mcpServers": {
    "cn-pianam-express-mcp": {
      "type": "http",
      "url": "https://pianam.cn/express-mcp/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-11-21 (score 73, +1)

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

### 2026-11-19 (score 72, +1)

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

### 2026-11-17 (score 71, +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-11-14 (score 70, +1)

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

### 2026-11-12 (score 69, +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-11-10 (score 68, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-09 (score 67)

First indexed and scored.

## MCP tools (3)

### `query_logistics` (~232 tokens)

Query Logistics

查询快递物流轨迹：输入快递单号 number（必填），可传 carrier 指定快递公司（支持编码如 shunfeng/zhongtong/yuantong/shentong/yunda/jd/ems，或中文名如 顺丰/中通/圆通/申通/韵达/京东/EMS；不传则按单号规则自动推测）。顺丰、中通部分单号需补充 phone_tail=收件人手机号后4位。返回物流状态、是否签收、轨迹时间轴（时间+内容）。数据源为快递100公开免费接口。

Input parameters:

- `carrier` (string): 快递公司编码或中文名（可选，不传自动推测），如 shunfeng/顺丰
- `number` (string): 快递单号，如 SF0218947552508、YT7460266600081、773170861031705
- `phone_tail` (string): 收件人手机号后4位（顺丰/中通部分单号必填，可选）

### `list_couriers` (~127 tokens)

List Couriers

列出支持的快递公司：返回编码、中文名、英文名、快递鸟编码、客服电话、官网与常用别名。可传 keyword 按名称/编码/别名过滤（如 '顺丰'、'SF'），limit 控制返回数量（默认50）。

Input parameters:

- `keyword` (string): 过滤关键词（中文名/编码/别名/英文名），如 顺丰、SF、jd；空则返回全部
- `limit` (integer): 返回数量上限，1-100，默认 50

### `detect_carrier` (~119 tokens)

Detect Carrier

按单号规则自动推测快递公司（本地规则库，离线可用）：输入快递单号，返回可能的公司列表（含编码、中文名、匹配规则与置信度高/中/低）。带字母前缀的单号（SF/YT/STO/JD/DPK/UPS 1Z 等）置信度最高。

Input parameters:

- `number` (string): 快递单号，如 SF0218947552508、YT7460266600081

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/cn-pianam-express-mcp/express-mcp-mcp#diagnostics

## Score history

- 2026-11-21: 73
- 2026-11-20: 72
- 2026-11-19: 72
- 2026-11-18: 71
- 2026-11-17: 71
- 2026-11-16: 70
- 2026-11-15: 70
- 2026-11-14: 70
- 2026-11-13: 69
- 2026-11-12: 69
- 2026-11-11: 68
- 2026-11-10: 68
- 2026-11-09: 67

## Common questions

### What is the cn.pianam/express-mcp server?

cn.pianam/express-mcp is listed in the public MCP registry as cn.pianam/express-mcp. MCP server for Chinese express delivery tracking: query parcel status by tracking number across. This page covers its hosted endpoint (https://pianam.cn/express-mcp/mcp).

### Is the cn.pianam/express-mcp server safe to use?

cn.pianam/express-mcp scores 73 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 cn.pianam/express-mcp server expose?

cn.pianam/express-mcp exposes 3 tools: query_logistics, list_couriers, detect_carrier. Their descriptions and schemas cost roughly 478 tokens of context every time the server is loaded.

### Does the cn.pianam/express-mcp server require authentication?

No. We connected to cn.pianam/express-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the cn.pianam/express-mcp server still maintained?

cn.pianam/express-mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the cn.pianam/express-mcp server?

VerifyMCP ran 12 checks on cn.pianam/express-mcp, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about cn.pianam/express-mcp: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://pianam.cn/express-mcp/mcp
- Changelog RSS feed: https://verifymcp.io/servers/cn-pianam-express-mcp/express-mcp-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/cn-pianam-express-mcp/express-mcp-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cn-pianam-express-mcp/express-mcp-mcp.json
- HTML version of this page: https://verifymcp.io/servers/cn-pianam-express-mcp/express-mcp-mcp
