Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Legal is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
3
tools declared
remote
at its publisher
—
calls last 7d
What it does
MCP server for Chinese law lookup: statutes, regulations and articles by keyword or law name.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http pianam-legal-mcp https://pianam.cn/legal-mcp/mcp
# 2 — ask your agent for something these tools do
# labor_calc, court_fee_calc, law_search
Legal costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
PIAll 14 servers
pianam14 servers
9 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http pianam-legal-mcp https://pianam.cn/legal-mcp/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
3 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
劳动法计算器（纯本地计算）。用 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（累计
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action | string | yes | severance=经济补偿/赔偿金；overtime=加班费；annual_leave=年休假；double_wage=二倍工资 |
| years | no | （severance）本单位工作年限，年，3.5 表示3年6个月 | |
| monthly_salary | no | 月工资（离职前12个月平均）或加班费计算基数 | |
| local_avg_salary | no | （severance，可选）当地上年度职工月平均工资 | |
| termination_type | string | no | （severance）N / N+1 / 2N |
| workday_hours | number | no | — |
| restday_hours | number | no | — |
| holiday_hours | number | no | — |
| hours | no | — | |
| overtime_type | no | — | |
| total_years | no | （annual_leave）累计工作年限 | |
| months_since_entry | no | （double_wage）入职至未签合同状态持续月数 |
诉讼费计算器（纯本地计算，依据《诉讼费用交纳办法》国务院令第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%；超100
| Parameter | Type | Required | Notes |
|---|---|---|---|
| case_type | string | yes | property=财产案件；divorce=离婚案件；execution=申请执行 |
| amount | no | 标的额/执行金额（元） | |
| property_amount | no | （divorce）离婚财产分割总额（元） |
常用法律条文全文检索（本地 SQLite FTS5，共收录6部法律1796条）：《民法典》1260条、《劳动法》107条、《劳动合同法》98条、《消费者权益保护法》63条、《道路交通安全法》124条、《治安管理处罚法（2025修订，2026年施行）》144条。三种用法：① keyword 关键词全文检索（如『经济补偿』『三倍工资』『醉酒驾驶』，可加 law 限定法律）；② law + article_no 按法律名与条号直取条文（如 law=劳动合同法, article_no=47；条号可传阿拉伯数字或中文）；③ 不传参数返回收录法律目录。返回法律名、条号与条文原文。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| keyword | no | 检索关键词，如 经济补偿、带薪年休假、消费者、醉驾 | |
| law | no | 限定法律（简称即可）：民法典/劳动法/劳动合同法/消费者权益保护法/道路交通安全法/治安管理处罚法 | |
| article_no | no | 条号，如 47 或 第四十七条（与 law 同时使用） | |
| limit | integer | no | 返回条数上限，1-50，默认10 |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Legal or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.0.0 · scanned 10 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest68cbdbd29f566e94b05152cfcb4bcec52003323a573cf0b5b3dc72cf25cf495c
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| labor_calc | no tags | |
| court_fee_calc | no tags | |
| law_search | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest68cbdbd29f566e94
Scanned2026-11-10
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Legal can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.