cn.pianam/adcheck-mcp
REMOTE · PIANAM.CN
MCP server for China advertising-law compliance check: flag prohibited wording in marketing copy.
Available components
Last scanned (14 hours ago)
Scores higher than 59% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Marketing and SEO
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation 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.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 +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.
- 18 Nov 26 +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.
- 16 Nov 26 +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.
- 14 Nov 26 +29
- TLS certificate: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- 13 Nov 26 −28
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- 12 Nov 26 +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.
- 10 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 9 Nov 26 67
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://pianam.cn/adcheck-mcp/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pianam.cn | CN=YR1,O=Let's Encrypt,C=US | 11 Nov 2026 | 9 Feb 2027 | RSA 2048 | SHA256-RSA | 52faeb2a8c950aa4b834de3ec969b579723 |
| SANs: pianam.cn, www.pianam.cn | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of pianam.cn. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| cn. | DS published | 33094 | 8 | Verified |
| pianam.cn. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | frame-ancestors 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pianam.cn/adcheck-mcp/mcp | Verified | 200 | |
| http (plaintext) | http://pianam.cn/adcheck-mcp/mcp | HTTPS enforced | 301 | https://pianam.cn/adcheck-mcp/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ad_banned_words Ad Banned Words ~103
查看广告法违禁词库:返回全部词条或指定 category 类别下的词表(词、类别、风险级别)。可选类别:绝对化用语、医疗功效、权威背书、诱导抢购、封建迷信、投资承诺、教育培训、房产违规、虚假夸大。
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | 可选类别名,省略返回全部类别样本 |
Structured output declared, but exposes no named fields.
No examples provided.
ad_compliance_check Ad Compliance Check ~225
广告法违禁词/极限词检测。输入广告文案 text(商品标题、详情页、宣传语等),纯本地词库匹配返回:总体风险结论(通过/需修改/不通过)、命中违禁词清单(词、类别、风险级别、风险说明、法律依据、修改建议、原文上下文)、高中低风险数量统计、类别统计,以及自动打码后的安全文案。覆盖绝对化用语(国家级/最佳/第一/顶级)、医疗功效(治疗/根治/减肥)、权威背书(特供/免检)、诱导抢购(秒杀/万人疯抢)、封建迷信、投资承诺(保本/零风险)、教育培训(保过)、房产违规等9类约560词。
| Name | Type | Req | Description |
|---|---|---|---|
| mask | boolean | – | 是否返回打码替换后的安全文案,默认 True |
| text | string | yes | 待检测的广告文案全文 |
Structured output declared, but exposes no named fields.
No examples provided.
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.
remote · pianam.cn
claude mcp add --transport http cn-pianam-adcheck-mcp 'https://pianam.cn/adcheck-mcp/mcp'
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.