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

MCP server for China administrative divisions: province/city/district lookup, adcode resolution and

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

## Components

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

## Channel facts

- Endpoint: `https://pianam.cn/region-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 4 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**: 76/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 617 tokens (~154/item across 4 items; 4 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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/region-mcp server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

- [security improvement] Transport: fail → pass

### 2026-11-18 (score 61, −10)

- [security regression] Transport: pass → fail

### 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-15 (score 70, +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-11-13 (score 69, +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-11-11 (score 68, +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-11-10 (score 67, 0)

- [functional improvement] Stability: unverified → 0.03

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

First indexed and scored.

## MCP tools (4)

### `parse_id_card` (~117 tokens)

Parse Id Card

解析 18 位中国大陆居民身份证号：按 GB 11643-1999 校验位算法验证合法性，返回归属地（省/市/区，含邮编区号）、出生日期、实足年龄、生肖、星座、性别。非法号码返回具体错误原因（校验位错误/格式错误/出生日期非法等）。

Input parameters:

- `id_number` (string, required): 18 位身份证号（末位可为 X），仅做本地算法校验，不联网

### `parse_phone` (~110 tokens)

Parse Phone

解析 11 位中国大陆手机号：返回运营商（中国移动/中国联通/中国电信/中国广电/虚拟运营商，含物联网卡等细分类型）、归属地省/市、邮编与长途区号。号段库含约 49.7 万个号段（2023 年公开数据）。

Input parameters:

- `phone` (string, required): 11 位手机号（支持含空格/连字符输入，自动提取数字）

### `parse_plate` (~139 tokens)

Parse Plate

解析中国大陆机动车号牌：支持普通蓝牌/黄牌（7 位，如 鲁B12345、京A12345）与新能源绿牌（8 位，如 粤BD12345、沪AD12345），返回省份、发牌地市、是否新能源及动力类型（D 纯电动 / F 插混或燃料电池）；内置全国 31 省简称与 392 个地市字母代码表。

Input parameters:

- `plate` (string, required): 车牌号，如 鲁B12345（普通）、粤BD12345（新能源小型）、京A12345

### `lookup_region` (~251 tokens)

Lookup Region

中国行政区划查询（GB/T 2260，省/市/区县三级约 4100 条，含邮政编码与长途区号）：支持按名称关键词（如 南山、青岛、凉山）查、按 6 位区划码精确查（如 440305）、按 6 位邮编反查（如 266001）、按长途区号反查（如 0532）；可用 level 限定省/市/区县层级。

Input parameters:

- `code`: 区划码（2/4/6 位，如 110105），精确查询
- `level`: 可选层级过滤：省 / 市 / 区县
- `limit` (integer): 返回条数上限，默认 20，最大 100
- `query`: 地区名称关键词（省/市/区县名，如 朝阳、深圳、凉山彝族自治州）
- `tel_code`: 长途区号（如 010、0571），反查地区
- `zip_code`: 6 位邮政编码（如 100010），反查地区

## Diagnostics

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

## Score history

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

## Common questions

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

cn.pianam/region-mcp is listed in the public MCP registry as cn.pianam/region-mcp. MCP server for China administrative divisions: province/city/district lookup, adcode resolution and. This page covers its hosted endpoint (https://pianam.cn/region-mcp/mcp).

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

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

cn.pianam/region-mcp exposes 4 tools: parse_id_card, parse_phone, parse_plate, lookup_region. Their descriptions and schemas cost roughly 617 tokens of context every time the server is loaded.

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

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

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

cn.pianam/region-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/region-mcp server?

VerifyMCP ran 12 checks on cn.pianam/region-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/region-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/region-mcp/mcp
- Changelog RSS feed: https://verifymcp.io/servers/cn-pianam-region-mcp/region-mcp-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/cn-pianam-region-mcp/region-mcp-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cn-pianam-region-mcp/region-mcp-mcp.json
- HTML version of this page: https://verifymcp.io/servers/cn-pianam-region-mcp/region-mcp-mcp
