Legislation Uk
NPM · @PIPEWORX/MCP-LEGISLATION-UK · 2 COMPONENTS
legislation.gov.uk MCP — the UK's official legislation database.
Available components
Last scanned (9 hours ago)
Scores higher than 68% of npm servers
Category Education and Research
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-legislation-uk). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2239 tokens (~373/item across 6 items; 6 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 Management23
- Stability observed for 7 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
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.
- 3 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −13
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.13 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 78
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-legislation-uk@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-legislation-uk |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-legislation-uk/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3649663762 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:07104a0b3c282e73fc45e21c06b647e72009d934574405ee5c8bc8c8f718d5b6f1d173e45df8cc7ada2c564779aec0261bda5ff8ef797733e1da7a0b4 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
get_explanatory_notes ~316
Read the Explanatory Notes for a UK Act — plain-language commentary written by the government department responsible, explaining what a section is meant to do and why. NOT part of the law and not endorsed by Parliament — use for context on intent, never as the text of the law itself (use get_legislation_section for that). Pass section to get the commentary for just that section; omit it for an overview plus the notes' own table of contents. Not every Act has notes (Appropriation, Consolidated Fund, Finance and Consolidation Acts never get them) and not every section gets its own paragraph — some are grouped or unremarked. Notes are written for the Act AS ENACTED and are not updated for later amendments. Source: legislation.gov.uk (HTML only — there is no XML/data feed for notes).
| Name | Type | Req | Description |
|---|---|---|---|
| number | number | yes | Item number within that year/type, e.g. 12 for the Data Protection Act 2018. |
| section | string | – | Optional: section number, e.g. "5", to get just that section's commentary. Omit for an overview. |
| type | string | yes | Document type, e.g. "ukpga". One of: ukpga (UK Public General Acts), uksi (UK Statutory Instruments), asp (Scottish Parliament Acts), anaw/asc (Wales), nia (Northern Ireland), ukla (UK Local Acts). |
| year | number | yes | Year, e.g. 2018. |
No output schema declared.
No examples provided.
get_legislation ~187
Get metadata for one specific piece of UK legislation by type + year + number (e.g. ukpga/2010/15 = Equality Act 2010). Returns title, type, year, number, status, extent, enactment date, a long-title summary, and the full-text URL. Content is XML; fields are best-effort parsed and a raw excerpt is included.
| Name | Type | Req | Description |
|---|---|---|---|
| number | number | yes | Item number within that year/type, e.g. 15. |
| type | string | yes | Document type, e.g. "ukpga". One of: ukpga (UK Public General Acts), uksi (UK Statutory Instruments), asp (Scottish Parliament Acts), anaw/asc (Wales), nia (Northern Ireland), ukla (UK Local Acts). |
| year | number | yes | Year, e.g. 2010. |
No output schema declared.
No examples provided.
get_legislation_section ~528
Read the actual WORDS of one section of a UK Act or statutory instrument — "what does section 5 of the Data Protection Act 2018 say", "quote section 1 of the Human Rights Act", "text of s.170 DPA 2018". Returns the full text of that section alone, so a specific provision does not cost a whole statute. Identify the legislation by type + year + number (Data Protection Act 2018 = ukpga/2018/12) and give the section number. UK law exists in VERSIONS and they differ in substance: pass version to choose "current" (default — the law as amended and in force today), "enacted" (the original text as passed), or a date YYYY-MM-DD for the text as it stood on that day. as_at is an alias for a date version (e.g. as_at: "2019-01-01") — the same date is also accepted via version. legislation.gov.uk serves the NEAREST EARLIER version for a date with no amendment on it rather than erroring, so every response states the version it actually served (version_valid_from) alongside the date asked for, even when they differ. Source: legislation.gov.uk, the official database. Use search_uk_legislation or get_legislation first if you need the year and number.
| Name | Type | Req | Description |
|---|---|---|---|
| as_at | string | – | YYYY-MM-DD — the law as it stood on this date. Alias for a date "version"; the response states the actual served version date, which may be earlier than this if nothing changed on the exact date give… |
| number | number | yes | Item number within that year/type, e.g. 12 for the Data Protection Act 2018. |
| section | string | yes | Section number, e.g. "5", "170", or "5A" for an inserted section. |
| type | string | yes | Document type, e.g. "ukpga". One of: ukpga (UK Public General Acts), uksi (UK Statutory Instruments), asp (Scottish Parliament Acts), anaw/asc (Wales), nia (Northern Ireland), ukla (UK Local Acts). |
| version | string | – | Which version of the text: "current" (default — the law as amended and in force today), "enacted" (the original text as passed), or a date YYYY-MM-DD for the text as it stood on that day. |
| year | number | yes | Year, e.g. 2018. |
No output schema declared.
No examples provided.
get_legislation_text ~434
Read the text of a whole UK Act or statutory instrument — the body of the law rather than a catalogue entry. Use for short instruments and for reading an Act end to end; for one provision prefer get_legislation_section, which returns just that section. Large Acts run to megabytes, so this reads a bounded amount and says plainly when it stopped short rather than returning a silently clipped statute. UK law exists in VERSIONS that differ in substance: pass version to choose "current" (default — the law as amended and in force today), "enacted" (the original text as passed), or a date YYYY-MM-DD for the text as it stood on that day. as_at is an alias for a date version (e.g. as_at: "2019-01-01"). legislation.gov.uk serves the NEAREST EARLIER version for a date with no amendment on it rather than erroring, so every response states the version it actually served (version_valid_from) alongside the date asked for, even when they differ. Source: legislation.gov.uk, the official database.
| Name | Type | Req | Description |
|---|---|---|---|
| as_at | string | – | YYYY-MM-DD — the law as it stood on this date. Alias for a date "version"; the response states the actual served version date, which may be earlier than this if nothing changed on the exact date give… |
| number | number | yes | Item number within that year/type, e.g. 12. |
| type | string | yes | Document type, e.g. "ukpga". One of: ukpga (UK Public General Acts), uksi (UK Statutory Instruments), asp (Scottish Parliament Acts), anaw/asc (Wales), nia (Northern Ireland), ukla (UK Local Acts). |
| version | string | – | Which version of the text: "current" (default — the law as amended and in force today), "enacted" (the original text as passed), or a date YYYY-MM-DD for the text as it stood on that day. |
| year | number | yes | Year, e.g. 2018. |
No output schema declared.
No examples provided.
legislation_amendments ~378
What has amended this UK Act or instrument, and (in the other direction) what this legislation itself amends — "what has changed the Data Protection Act 2018", "has section 13A been amended", "what does the Victims and Prisoners Act 2024 amend". Each row names the amending/amended instrument, the affected and affecting provisions, the type of change (inserted/substituted/repealed/omitted/amended etc.), whether it has actually been APPLIED (some amendments are made but not yet in force), and the commencement date. PAGED AT 50 — the response states total_results and total_pages; 50 rows is a page, never the whole change history (some Acts have thousands of recorded effects), pass page for more. direction "affected" (default) = changes made TO this legislation by others; "affecting" = changes this legislation makes TO others. Source: legislation.gov.uk /changes/ Atom feed.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | "affected" (default) — changes made TO this legislation by other instruments. "affecting" — changes this legislation makes TO other instruments. |
| number | number | yes | Item number within that year/type, e.g. 12 for the Data Protection Act 2018. |
| page | number | – | Results page (default 1). 50 rows per page — see total_pages in the response. |
| type | string | yes | Document type, e.g. "ukpga". One of: ukpga (UK Public General Acts), uksi (UK Statutory Instruments), asp (Scottish Parliament Acts), anaw/asc (Wales), nia (Northern Ireland), ukla (UK Local Acts). |
| year | number | yes | Year, e.g. 2018. |
No output schema declared.
No examples provided.
search_uk_legislation ~341
Search UK legislation by title words (and optional year), returning matching Acts/instruments with their full-text URLs. UK legislation only. Source: legislation.gov.uk Atom feed. Document types: ukpga (UK Public General Acts), uksi (UK Statutory Instruments), asp (Scottish Parliament Acts), anaw/asc (Wales), nia (Northern Ireland), ukla (UK Local Acts). "type" is optional: give an exact code (e.g. "ukpga"), a plain category ("act", "si", "ssi"), or omit it entirely — omitted defaults to "ukpga" and the response says so. A zero-match result carries a "hint" explaining why (legislation.gov.uk's own search is CDN-cached for up to an hour, so a genuine no-match and a stale cached page look identical) — never a bare empty "results".
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | Results page (default 1). 20 results per page. |
| title | string | yes | Words to match in the title, e.g. "equality". |
| type | string | – | Document type code (e.g. "ukpga") or category ("act", "si", "ssi"). Optional — defaults to "ukpga" if omitted. Full code list: ukpga (UK Public General Acts), uksi (UK Statutory Instruments), asp (Sc… |
| year | number | – | Optional year to restrict results, e.g. 2010. |
No output schema declared.
No examples provided.
How do I install the Legislation Uk MCP server?
Legislation Uk runs locally as an npm package, launched with npx -y @pipeworx/mcp-legislation-uk. 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-legislation-uk
claude mcp add pipeworx-io-legislation-uk -- npx -y @pipeworx/mcp-legislation-uk
What is the Legislation Uk MCP server?
Legislation Uk is an MCP server listed in the public MCP registry as io.github.pipeworx-io/legislation-uk. legislation.gov.uk MCP, the UK's official legislation database. This page covers its npm package (@pipeworx/mcp-legislation-uk).
Is the Legislation Uk MCP server safe to use?
Legislation Uk scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 Legislation Uk MCP server expose?
Legislation Uk exposes 6 tools: search_uk_legislation, get_legislation, get_legislation_section, get_legislation_text, legislation_amendments, get_explanatory_notes. Their descriptions and schemas cost roughly 2,184 tokens of context every time the server is loaded.
Is the Legislation Uk MCP server still maintained?
Legislation Uk is still listed as active in the MCP registry. We last reached this channel on 5 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 Legislation Uk MCP server under?
Legislation Uk declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.