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

MCP server for China advertising-law compliance check: flag prohibited wording in marketing copy.

- 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-adcheck-mcp/adcheck-mcp-mcp.md), [page](https://verifymcp.io/servers/cn-pianam-adcheck-mcp/adcheck-mcp-mcp)

## Channel facts

- Endpoint: `https://pianam.cn/adcheck-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 2 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**: 79/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 328 tokens (~164/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**: 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 2 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 current MCP spec version (2026-07-28).

## Install

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

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

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

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

- [security improvement] TLS certificate: unverified → pass
- [security improvement] Transport: fail → pass

### 2026-11-13 (score 41, −28)

- [security regression] TLS certificate: pass → unverified
- [security regression] Transport: pass → fail

### 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 (2)

### `ad_compliance_check` (~225 tokens)

Ad Compliance Check

广告法违禁词/极限词检测。输入广告文案 text（商品标题、详情页、宣传语等），纯本地词库匹配返回：总体风险结论（通过/需修改/不通过）、命中违禁词清单（词、类别、风险级别、风险说明、法律依据、修改建议、原文上下文）、高中低风险数量统计、类别统计，以及自动打码后的安全文案。覆盖绝对化用语（国家级/最佳/第一/顶级）、医疗功效（治疗/根治/减肥）、权威背书（特供/免检）、诱导抢购（秒杀/万人疯抢）、封建迷信、投资承诺（保本/零风险）、教育培训（保过）、房产违规等9类约560词。

Input parameters:

- `mask` (boolean): 是否返回打码替换后的安全文案，默认 True
- `text` (string, required): 待检测的广告文案全文

### `ad_banned_words` (~103 tokens)

Ad Banned Words

查看广告法违禁词库：返回全部词条或指定 category 类别下的词表（词、类别、风险级别）。可选类别：绝对化用语、医疗功效、权威背书、诱导抢购、封建迷信、投资承诺、教育培训、房产违规、虚假夸大。

Input parameters:

- `category`: 可选类别名，省略返回全部类别样本

## Diagnostics

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

## Score history

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

## Common questions

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

cn.pianam/adcheck-mcp is listed in the public MCP registry as cn.pianam/adcheck-mcp. MCP server for China advertising-law compliance check: flag prohibited wording in marketing copy. This page covers its hosted endpoint (https://pianam.cn/adcheck-mcp/mcp).

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

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

cn.pianam/adcheck-mcp exposes 2 tools: ad_compliance_check, ad_banned_words. Their descriptions and schemas cost roughly 328 tokens of context every time the server is loaded.

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

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

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

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

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