Home / MCP registry index / org.lexiara/lexiara
Lexiara
org.lexiara/lexiara in the official MCP registry.
Endpoint https://lexiara.org/mcp. Source: github.com/thomasmackie/legal-landscape.
The registry describes it as: Provenance-backed EU and UK legislation for AI agents, addressable to the individual provision.
We read its 31 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
search fetch lookup_provision list_work_versions search_legislation explore_role_requirements list_saved_role_views get_saved_role_view provision_context define_term work_glossary term_languages list_concepts concept_family provisions_by_concept related_works work_mentions provision_history find_national_implementations guidance_for_provision list_topics get_topic recent_changes list_review_queue list_follows follow_updates get_coverage request_ingestion list_ingestion_requests get_ingestion_request get_ingestion_result
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/org-lexiara-lexiara)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.