Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

cn.pianam/legal-mcp

REMOTE · PIANAM.CN

MCP server for Chinese law lookup: statutes, regulations and articles by keyword or law name.

Available components

+3 this week 69 Trust /100

Last scanned (13 hours ago)

Scores higher than 53% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Health and Science

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability61
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1111 tokens (~370/item across 3 items; 3 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 Coverage92
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 74% of tool parameters carry a description.Partial
  • 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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
What we tested

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 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.

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 →

Changelog

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 +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.

  • 11 Nov 26 +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.

  • 10 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 9 Nov 26 64

    First indexed and scored.

Diagnostics

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/legal-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/legal-mcp/mcp Verified 200
http (plaintext) http://pianam.cn/legal-mcp/mcp HTTPS enforced 301 https://pianam.cn/legal-mcp/mcp
MCP tools · 3 exposed · ~1,111 tokens

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 →

Tool Tokens
court_fee_calc ~332

诉讼费计算器(纯本地计算,依据《诉讼费用交纳办法》国务院令第481号)。用 case_type 区分:case_type=property 财产案件受理费:传 amount(标的额,元),按分段累计输出明细(≤1万每件50元;1-10万部分2.5%;10-20万2%;20-50万1.5%;50-100万1%;100-200万0.9%;200-500万0.8%;500-1000万0.7%;1000-2000万0.6%;超2000万0.5%);case_type=divorce 离婚案件:基础受理费50-300元/件,可选传 property_amount(财产分割总额,元),超20万元部分按0.5%加收;case_type=execution 申请执行费:传 amount(执行金额,元),分段累计(≤1万每件50元;1-50万1.5%;50-500万1%;500-1000万0.5%;超1000万0.1%),不传金额时说明50-500元/件。

NameTypeReqDescription
amount––标的额/执行金额(元)
case_typestringyesproperty=财产案件;divorce=离婚案件;execution=申请执行
property_amount––(divorce)离婚财产分割总额(元)

Structured output declared, but exposes no named fields.

No examples provided.

labor_calc ~484

劳动法计算器(纯本地计算)。用 action 区分子功能:action=severance 经济补偿/赔偿金:传 years(工作年限,年,可为小数)、monthly_salary(离职前12个月平均月工资)、local_avg_salary(可选,当地上年度职工月平均工资,用于三倍封顶与12年封顶)、termination_type(N=协商/法定经济补偿;N+1=无过失性辞退加代通知金;2N=违法解除赔偿金);action=overtime 加班费:传 monthly_salary(月工资或约定基数)及 workday_hours(工作日延时小时)、restday_hours(休息日小时)、holiday_hours(法定节假日小时),或用 hours+overtime_type(1.5/2/3)单次计算;action=annual_leave 年休假:传 total_years(累计工作年限)返回应享年假天数(5/10/15天);action=double_wage 未签合同二倍工资:传 months_since_entry(入职月数)与可选 monthly_salary,返回最多11个月的二倍工资差额规则说明与估算。

NameTypeReqDescription
actionstringyesseverance=经济补偿/赔偿金;overtime=加班费;annual_leave=年休假;double_wage=二倍工资
holiday_hoursnumber––
hours–––
local_avg_salary––(severance,可选)当地上年度职工月平均工资
monthly_salary––月工资(离职前12个月平均)或加班费计算基数
months_since_entry––(double_wage)入职至未签合同状态持续月数
overtime_type–––
restday_hoursnumber––
termination_typestring–(severance)N / N+1 / 2N
total_years––(annual_leave)累计工作年限
workday_hoursnumber––
years––(severance)本单位工作年限,年,3.5 表示3年6个月

Structured output declared, but exposes no named fields.

No examples provided.

law_search ~295

常用法律条文全文检索(本地 SQLite FTS5,共收录6部法律1796条):《民法典》1260条、《劳动法》107条、《劳动合同法》98条、《消费者权益保护法》63条、《道路交通安全法》124条、《治安管理处罚法(2025修订,2026年施行)》144条。三种用法:① keyword 关键词全文检索(如『经济补偿』『三倍工资』『醉酒驾驶』,可加 law 限定法律);② law + article_no 按法律名与条号直取条文(如 law=劳动合同法, article_no=47;条号可传阿拉伯数字或中文);③ 不传参数返回收录法律目录。返回法律名、条号与条文原文。

NameTypeReqDescription
article_no––条号,如 47 或 第四十七条(与 law 同时使用)
keyword––检索关键词,如 经济补偿、带薪年休假、消费者、醉驾
law––限定法律(简称即可):民法典/劳动法/劳动合同法/消费者权益保护法/道路交通安全法/治安管理处罚法
limitinteger–返回条数上限,1-50,默认10

Structured output declared, but exposes no named fields.

No examples provided.

Install

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

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

# add to Claude Code
claude mcp add --transport http cn-pianam-legal-mcp 'https://pianam.cn/legal-mcp/mcp'
Common questions

What is the cn.pianam/legal-mcp server?

cn.pianam/legal-mcp is listed in the public MCP registry as cn.pianam/legal-mcp. MCP server for Chinese law lookup: statutes, regulations and articles by keyword or law name. This page covers its hosted endpoint (https://pianam.cn/legal-mcp/mcp).

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

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

cn.pianam/legal-mcp exposes 3 tools: labor_calc, court_fee_calc, law_search. Their descriptions and schemas cost roughly 1,111 tokens of context every time the server is loaded.

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

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

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

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

VerifyMCP ran 12 checks on cn.pianam/legal-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/legal-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.