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.

Law Commission

NPM · @PIPEWORX/MCP-LAW-COMMISSION · 2 COMPONENTS

Law Commission of England & Wales — publications and law-reform projects.

+3 this week 91 Trust /100

Last scanned (14 hours ago)

Scores higher than 88% of npm servers

Category Education and Research

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-law-commission). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 19 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 519 tokens (~173/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 Management80
  • Stability observed for 24 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
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 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

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.

  • 21 Nov 26 +1

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

  • 19 Nov 26 +1

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

  • 17 Nov 26 +1

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

  • 15 Nov 26 +1

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

  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 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 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

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

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

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 22 Nov 2026 · Analysed npm/@pipeworx/mcp-law-commission@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-law-commission
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-law-commission/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3649638117
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:d2981b9fb5962eb7f45fead7a9dc90db40020ac1b94f6dfc5f5d507681738a3fd8d44ce326fffda8c4ab599dd4190f31565e7a97dd52d26a2373ce335

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~465 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
get_law_commission_publication ~137

Fetch one Law Commission of England & Wales publication (a consultation paper, report, summary or terms-of-reference) by its id (from search_law_commission_publications) or its lawcom.gov.uk link. Returns the law-reform project it belongs to and links to any attached PDF documents — the actual report text is the PDF; the WordPress record itself typically carries only a project link, not report prose.

NameTypeReqDescription
idnumber–Publication id, from search_law_commission_publications.
linkstring–A lawcom.gov.uk/publication/... link, as an alternative to id.

No output schema declared.

No examples provided.

list_law_commission_projects ~130

List law-reform projects run by the Law Commission of England & Wales (lawcom.gov.uk/project) — the workstreams under which its consultation papers and reports are published, e.g. "Commercial leasehold" or "Consumer class actions". Optionally narrow by status. Welsh-language duplicates are filtered out, one row per project.

NameTypeReqDescription
limitnumber–Projects to return, 1-50 (default 20).
statusstring–Filter by project status: "current", "completed", "upcoming", or "other". Omit to list all statuses.

No output schema declared.

No examples provided.

search_law_commission_publications ~198

Search consultation papers, reports, summaries and terms-of-reference published by the Law Commission of England & Wales (lawcom.gov.uk) — the independent statutory body that reviews the law and recommends reform. Returns title, link and date for each match (excerpt is usually empty upstream — the publication record itself carries only a project link, not a summary; call get_law_commission_publication for the project and any attached PDF report). Welsh-language duplicates of an English publication are filtered out automatically (the Commission republishes the same report under a separate id in Welsh), so results are one row per report. Omit query to get the most recent publications.

NameTypeReqDescription
limitnumber–Publications to return, 1-50 (default 10).
querystring–Free-text search over publication titles and content, e.g. "leasehold" or "surrogacy". Omit for the most recent publications.

No output schema declared.

No examples provided.

Install

How do I install the Law Commission MCP server?

Law Commission runs locally as an npm package, launched with npx -y @pipeworx/mcp-law-commission. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-law-commission

# add to Claude Code
claude mcp add pipeworx-io-law-commission -- npx -y @pipeworx/mcp-law-commission
Common questions

What is the Law Commission MCP server?

Law Commission is an MCP server listed in the public MCP registry as io.github.pipeworx-io/law-commission. Law Commission of England & Wales, publications and law-reform projects. This page covers its npm package (@pipeworx/mcp-law-commission).

Is the Law Commission MCP server safe to use?

Law Commission scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Law Commission MCP server expose?

Law Commission exposes 3 tools: search_law_commission_publications, get_law_commission_publication, list_law_commission_projects. Their descriptions and schemas cost roughly 465 tokens of context every time the server is loaded.

Is the Law Commission MCP server still maintained?

Law Commission is still listed as active in the MCP registry. We last reached this channel on 22 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Law Commission MCP server under?

Law Commission declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Law Commission MCP server?

VerifyMCP ran 16 checks on Law Commission, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.