Legiscan vs Legislation Uk — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Legiscan vs Legislation Uk
In-depth architectural comparison of the Legiscan and Legislation Uk MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Legiscan
Legal · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Legislation Uk
Legal · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Verdict Summary: Choose Legiscan if you need specialized Legal tools running via a local process. Choose Legislation Uk if your workspace requires Legal integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Legiscan when:
You need dedicated capabilities in the Legal domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Full-text search US state (and federal) legislation to find out what bills are about a given topic. Searches one state or nationwide (ALL) and returns matching bills with number, title, state, last action, and a LegiScan bill_id you can pass to get_bill. Example: search_bills({ query: "data privacy…
get_bill
Get the full detail for a single US legislative bill — status, sponsors (name/party/role), subjects, and links to the bill text. Use the bill_id returned by search_bills. Example: get_bill({ bill_id: 1234567 })
list_sessions
List the legislative sessions for a US state (regular and special), with start/end years and session IDs. Useful to scope which session to track bills in. Example: list_sessions({ state: "NY" })
Legislation Uk Tools (6)
search_uk_legislation
Search by title words (and optional year) → matching Acts/instruments with full-text URLs. `type` is optional — an exact code, a plain category (`"act"`, `"si"`, `"ssi"`), or omit it to default to `ukpga`. (Renamed from `search_legislation` — the old name still resolves.)
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Legiscan is categorized under Legal and uses a local stdio subprocess. In contrast, Legislation Uk belongs to Legal using local stdio subprocess. Select Legiscan when you need capabilities focused on legal and Legislation Uk when you require tools for legal.
Metadata for one Act/instrument by type + year + number: title, status, extent, enactment date, full-text URL
get_legislation_section
The actual text of ONE section — e.g. section 5 of the Data Protection Act 2018 (`ukpga/2018/12`) — without paying for the whole statute. Takes `as_at` (or `version`) for a point-in-time date.
get_legislation_text
The text of a whole Act/instrument, byte-bounded: large Acts are truncated with an explicit note pointing at the section-level tool. Takes `as_at` (or `version`).
legislation_amendments
What has amended this legislation (`direction: "affected"`, default) or what it amends (`direction: "affecting"`) — amending/amended instrument, affected/affecting provisions, change type, whether applied, commencement date. **Paged at 50** — always states `total_results`/`total_pages`.
get_explanatory_notes
Plain-language commentary written by the responsible government department, explaining what a section is meant to do. NOT part of the law. Pass `section` for one section's commentary, or omit for an overview + table of contents.