Connect Lexiara and your agent gets 25 tools, among them define_term, fetch, find_national_implementations. It answers at https://lexiara.org/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 12 September 2026; the last check, on 24 October 2026, succeeded.
Provenance-backed EU and UK legislation for AI agents, addressable to the individual provision.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
define_term | The definition of a term of art, and the provision that gives it. Ask this BEFORE search_legislation whenever the question is what a phrase means ('durable medium', 'taxable person'): search returns provisions that USE a phrase, this return Inputs: term, jurisdiction, work, limit |
fetch | Retrieve one search result by its opaque id, including provision text, canonical URL, authority status and source provenance. metadata.structure provides parent/child addresses; an empty container text does not mean the law is absent. Use c Inputs: id |
find_national_implementations | National provisions implementing one EU provision, with method and confidence per link. DERIVED data, not published by any authority: treat links not marked method='human' as leads to verify, and say so when citing. Lexiara Nexus data requi Inputs: work, eId, jurisdiction, minConfidence |
follow_updates | The 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' Inputs: since, minSignificance, limit |
get_coverage | Per-source coverage and freshness. Call this first when unsure whether Lexiara holds the law you need — absence of coverage means 'not here', never 'does not exist'. Pass `work` to ask about ONE instrument. The answer then says which kind o Inputs: work, language |
get_ingestion_request | State, stage, reason code and the time to wait before asking again, for one request you made. States: already_available, queued, running, available, partial, needs_clarification, needs_source_approval, failed, confirmed_unavailable. A fetch Inputs: request_id |
get_ingestion_result | The published handles — expression id, work ELI, the /v1/works/text and /v1/provisions addresses — plus the source manifest (publisher URL, content hash, bytes, retrieval time, parser version) and the expectation results. Repeat your origin Inputs: request_id |
get_topic | Everything 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 Inputs: conceptId |
guidance_for_provision | Sections of official GUIDANCE that discuss one provision — Commission notices and guidelines on the act, quoted verbatim with the section number the publisher prints, so an answer can cite '§2.8 of the UCPD Guidance' and be checked. EVERY R Inputs: work, eId, includeActLevel |
list_follows | The instruments, provisions, subjects, jurisdictions and verticals this API key follows. READ-ONLY: creating or removing a follow is an HTTP POST/DELETE to /v1/follows, and no tool here dispatches one. (The one tool in this catalogue that w |
list_ingestion_requests | List up to the latest 50 ingestion requests belonging to your account, newest first. Each row includes private status fields such as `intent`, `created_at` and `origin`; another account's requests are never returned. This is read-only and d |
list_review_queue | The 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 Inputs: kind, vertical, jurisdiction, limit, offset, chars |
list_topics | Curated obligation topics ('Pre-contract information') under a subject head, each with a one-paragraph orientation and per-jurisdiction anchor counts. Descriptions with editorialStatus='draft' are UNREVIEWED model drafts — say so if you quo Inputs: subject |
lookup_provision | Authoritative text of one provision, with in-force window, repealed/prospective status, concept tags, transposition edges and full provenance. `stand` says what date the served text speaks as of (`consolidated` with a date, `as-adopted`, or Inputs: work, eId, expression, sourceLang, asAt |
provision_context | The cross-reference neighbourhood of a provision plus its amendment history. Use this when a provision's relevance is not on its face: a duty that says 'the information referred to in Article 6(1)' is silent about what that information now Inputs: work, eId |
provision_history | Prior and successor versions of one provision across consolidations — how the text got to its current form. Lexiara Nexus data requires an API key on a signed-in account. The free plan carries a monthly Nexus allowance; the legislative text Inputs: work, eId |
provisions_by_concept | Cross-jurisdiction view of one legal concept: every provision tagged with the given EuroVoc concept, with tagging method and confidence. E.g. 'eurovoc:4585' (VAT), 'eurovoc:4392' (VAT rate). The language-neutral way to line up EU and nation Inputs: conceptId, jurisdiction, minConfidence |
recent_changes | Change feed: provisions added or modified, filterable by jurisdiction, concept and date. `detectedAt` is when Lexiara observed the change — legal in-force dates come only from the provision itself. Inputs: jurisdiction, concept, since, limit |
related_works | Edges between instruments: which national laws transpose a directive (direction 'in'), or what an instrument implements/amends (direction 'out'). Instrument-level; for article-level links use find_national_implementations. Inputs: eli, direction |
request_ingestion | When a lookup returns `coverage` with `requestable: true`, ask for the missing instrument instead of stopping or guessing. Give the CELEX (or an EU ELI), the language and the version point; say WHY in one or two sentences; state any testabl Inputs: celex, eli, language, version, role, intent |
search | Search Lexiara's bounded EU and UK legislation corpus. Returns compact, citable results with opaque ids; pass an id unchanged to fetch for the provision text and provenance. Inputs: query |
search_legislation | Ranked full-text search over provision text. Results carry work, eId, status and provenance — feed a hit's work+eId to lookup_provision for the complete payload. Inputs: query, jurisdiction, language, limit |
term_languages | How an act words one of its defined terms in each language version held. NOT a translation: an EU instrument is equally authentic in all 24 official languages (Regulation No 1/1958, article 4), so each wording is the law in that language. U Inputs: term, work, jurisdiction, limit |
work_glossary | The act's glossary: every term it defines, alphabetical, with the publisher's own wording verbatim and the provision that defines each one. Use it to orient in an unfamiliar instrument, or to check what a term means IN THIS ACT rather than Inputs: work |
work_mentions | The 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 — wh Inputs: eli, limit |
Every block below points at https://lexiara.org/mcp. Pick your client and copy.
claude mcp add --transport http lexiara https://lexiara.org/mcp
{
"mcpServers": {
"lexiara": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://lexiara.org/mcp"]
}
}
}{
"mcpServers": {
"lexiara": {
"url": "https://lexiara.org/mcp"
}
}
}{
"servers": {
"lexiara": {
"type": "http",
"url": "https://lexiara.org/mcp"
}
}
}{
"context_servers": {
"lexiara": {
"url": "https://lexiara.org/mcp"
}
}
}{
"mcpServers": {
"lexiara": {
"serverUrl": "https://lexiara.org/mcp"
}
}
}{
"mcpServers": {
"lexiara": {
"url": "https://lexiara.org/mcp"
}
}
}name: Lexiara
version: 0.0.1
schema: v1
mcpServers:
- name: Lexiara
type: streamable-http
url: https://lexiara.org/mcp{
"mcpServers": {
"lexiara": {
"httpUrl": "https://lexiara.org/mcp"
}
}
}{
"mcpServers": {
"lexiara": {
"type": "http",
"url": "https://lexiara.org/mcp"
}
}
}{
"mcpServers": {
"lexiara": {
"url": "https://lexiara.org/mcp"
}
}
}goose://extension?url=https%3A%2F%2Flexiara.org%2Fmcp&type=streamable_http&id=lexiara&name=Lexiara
It answered our last check on 24 October 2026 in 381 ms. Over 6 checks since 12 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by lexiara.org and served from lexiara.org, the vendor's own domain: https://lexiara.org/mcp.
25, as returned by the server's own tools/list on 23 September 2026: define_term, fetch, find_national_implementations, follow_updates, get_coverage, get_ingestion_request, get_ingestion_result, get_topic, and 17 more.
It answered our last check on 24 October 2026 in 381 ms. Over 6 checks since 12 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://lexiara.org/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: org.lexiara. Endpoint host: lexiara.org. ARD identifier: urn:air:org.lexiara:mcp:lexiara.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.