Databases
lexiara.org
Provides legal research tools for searching legislation, accessing provision text with amendments, and defining legal terms.
ENDPOINT 1
https://lexiara.org/mcp
MCP server metadata
- Name
- lexiara
- Version
- 0.1.0
Lexiara serves authoritative legislation text with provenance. Every provision payload carries an `authoritative` flag and a `provenance` block (source URL, retrieval date, licence, content hash); cite the source URL, and treat `authoritative: false` text as a reading aid, never as the operative law. Derived data (transposition links, concept tags) carries method and confidence — anything not method='human' is a lead to verify. Works are identified by ELI URIs, provisions by eIds such as 'sec_4' (UK section 4), 'art_2__para_1' (article 2(1)), or 'sch_8__part_ii__grp_1__para_1' (UK Schedule 8 Part II Group 1 item 1).
Known tools 18
lookup_provisionAuthoritative text of one provision, with in-force window, repealed/prospective status, concept tags, transposition edges and full provenance.
Inferred read-onlyprovision_contextThe cross-reference neighbourhood of a provision plus its amendment history.
Inferred read-onlywork_glossaryThe act's glossary: every term it defines, alphabetical, with the publisher's own wording verbatim and the provision that defines each one.
Inferred read-onlyterm_languagesHow an act words one of its defined terms in each language version held.
Inferred read-onlyprovisions_by_conceptCross-jurisdiction view of one legal concept: every provision tagged with the given EuroVoc concept, with tagging method and confidence.
Inferred read-onlyrelated_worksEdges between instruments: which national laws transpose a directive (direction 'in'), or what an instrument implements/amends (direction 'out').
Inferred read-onlywork_mentionsThe act-level overview: every provision of every instrument in this corpus that names the given act, grouped by citing instrument, with the article of the act each citation resolved to (`targetEId`, null where the citation is act-level — which is most of them, and is not a defect).
Inferred read-onlyprovision_historyPrior and successor versions of one provision across consolidations — how the text got to its current form.
Inferred read-onlyfind_national_implementationsNational provisions implementing one EU provision, with method and confidence per link.
Inferred read-onlylist_topicsCurated obligation topics ('Pre-contract information') under a subject head, each with a one-paragraph orientation and per-jurisdiction anchor counts.
Inferred read-onlyget_topicEverything a topic page shows: the orientation paragraph (with its draft/published editorial status), per-jurisdiction legal-status notes (GB notes carry the assimilated-law caveat), anchored provisions with anchor provenance, article-level transposition links (method, confidence, review verdict — anything not method='human' is evidence, not a finding), and related instruments from the graph.
Inferred read-onlyrecent_changesChange feed: provisions added or modified, filterable by jurisdiction, concept and date.
Inferred read-onlylist_review_queueThe AUTO-GATED backlog from one place, newest first: unreviewed article-level transposition links with BOTH provision texts side by side and the stored reasoning, model/low-confidence concept tags, draft topic descriptions and jurisdiction notes, and recorded findings (gaps and divergences a round could not decide).
Inferred read-onlylist_followsThe instruments, provisions, subjects, jurisdictions and verticals this API key follows.
Inferred read-onlyfollow_updatesThe digest: every change the corpus observed on followed law, each with a SIGNIFICANCE grade and the reasoning behind it — 'major' (a new consolidation whose version point advanced, a provision appearing, a provision now repealed), 'minor' (wording changed, or the stored text moved while the publisher's version point did not), 'housekeeping' (first ingest, bulk churn from a version substitution).
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.lexiara]
url = "https://lexiara.org/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"lexiara": {
"type": "http",
"url": "https://lexiara.org/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: lexiara
Remote MCP URL: https://lexiara.org/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"lexiara": {
"url": "https://lexiara.org/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"lexiara": {
"type": "http",
"url": "https://lexiara.org/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "lexiara",
"transport": "streamable-http",
"url": "https://lexiara.org/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.