Eur Lex
NPM · @PIPEWORX/MCP-EUR-LEX · 2 COMPONENTS
EUR-Lex MCP — official EU law, article-level.
Available components
Last scanned (12 hours ago)
Scores higher than 81% 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-eur-lex). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1164 tokens (~145/item across 8 items; 8 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.10 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 +8
- Known CVEs: unverified → pass ▲ security
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 73
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-eur-lex@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-eur-lex |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-eur-lex/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3635932363 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:242454fd033f67fd6ffe90687dd2bf04186a40008c3b7564de46c219fb54334f83e8d7c75b7fada6fcb5bee1bfffff74579ddc7ff7f7628329cf83942 |
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 →
cjeu_judgment ~170
Get the FULL TEXT of an EU court judgment from its case number — "C-97/23", "T-144/25" — or its CELEX id. Resolves the case number people actually cite into the document. Use after cjeu_search, or whenever a case number appears in a filing or article.
| Name | Type | Req | Description |
|---|---|---|---|
| case_number | string | yes | As cited, e.g. "C-97/23" (Court of Justice) or "T-144/25" (General Court). A CELEX id like "62023CJ0097" also works. |
| max_chars | number | – | Max characters to return (default 12000, max 40000). |
| offset | number | – | Character offset, for paging through a long judgment (default 0). |
No output schema declared.
No examples provided.
cjeu_search ~208
Search EU COURT JUDGMENTS — the case law of the Court of Justice (CJEU) and the General Court — by subject. Returns the case, the court, the date and the CELEX id to read it with. Use for "what has the CJEU said about data protection", "EU court rulings on gatekeepers", or to find the judgment interpreting a Regulation. This is case law; search_legislation covers the Regulations and Directives themselves.
| Name | Type | Req | Description |
|---|---|---|---|
| court | string | – | Limit to a court: "cjeu" (Court of Justice) or "general" (General Court). Default: both. |
| include_notices | boolean | – | Include short Official Journal notices about judgments as well as the judgments themselves (default false). |
| limit | number | – | Maximum results (1-25, default 10). |
| query | string | yes | Words appearing in the case title, e.g. "data protection", "state aid", "trade mark". |
No output schema declared.
No examples provided.
compliance_index ~132
Resolve a common EU regulation name to its CELEX id. Returns the curated map of the EU digital/compliance corpus (GDPR, NIS2, DORA, AI Act, DSA, DMA, eIDAS, Cyber Resilience Act, Data Act, …) with CELEX ids, types, dates and one-line summaries. Use this first to turn a name like "GDPR" into the CELEX id the other tools need.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Optional filter — name/alias/keyword (e.g. "AI Act", "data"). Omit to list the whole corpus. |
No output schema declared.
No examples provided.
get_article ~156
Full text of one or more Articles of an act, with a verifiable EUR-Lex citation URL for each. THE article-level grounding tool: quote GDPR Art. 17, AI Act Art. 6, etc. Accepts a single number ("17"), a comma list ("5,6,17") or a range ("5-9").
| Name | Type | Req | Description |
|---|---|---|---|
| article | string | yes | Article selector: "17", "5,6,17", or "5-9". Suffixed numbers like "9a" are supported. |
| celex | string | yes | CELEX id or a known alias (e.g. "GDPR"). |
| lang | string | – | ISO 639-2/B language code (default "eng"). |
No output schema declared.
No examples provided.
get_document ~128
Plain-text of a whole act (recitals + enacting terms), paged. Use for short acts or to read recitals/definitions; for a specific Article prefer get_article. Returns up to max_chars from offset.
| Name | Type | Req | Description |
|---|---|---|---|
| celex | string | yes | CELEX id or a known alias. |
| lang | string | – | ISO 639-2/B language code (default "eng"). |
| max_chars | number | – | Max characters to return (default 8000, max 40000). |
| offset | number | – | Character offset to start from, for paging (default 0). |
No output schema declared.
No examples provided.
get_metadata ~127
Fetch title, document date, legal type, in-force status hint, and EUR-Lex citation URL for one EU act by CELEX id (e.g. "32016R0679") or alias (e.g. "GDPR"); does not download full text.
| Name | Type | Req | Description |
|---|---|---|---|
| celex | string | yes | CELEX id, e.g. "32016R0679", or a known alias like "GDPR". |
| lang | string | – | ISO 639-2/B language code for the title (default "eng": eng, fra, deu, spa, ita, …). |
No output schema declared.
No examples provided.
list_articles ~75
Table of contents for an act: every Article number and its heading. Use to discover which Article to quote before calling get_article.
| Name | Type | Req | Description |
|---|---|---|---|
| celex | string | yes | CELEX id or a known alias (e.g. "DORA"). |
| lang | string | – | ISO 639-2/B language code (default "eng"). |
No output schema declared.
No examples provided.
search_legislation ~113
Full-text search of EU legislation titles via the EUR-Lex SPARQL endpoint. Returns CELEX id, English title and document date. Use when the act is not in compliance_index, or to find related/amending acts.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default 10, max 25). |
| query | string | yes | Keyword(s) that must appear in the English title, e.g. "cybersecurity certification". |
| type | string | – | Optional: restrict to a legal act type. |
No output schema declared.
No examples provided.
How do I install the Eur Lex MCP server?
Eur Lex runs locally as an npm package, launched with npx -y @pipeworx/mcp-eur-lex. 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-eur-lex
claude mcp add pipeworx-io-eur-lex -- npx -y @pipeworx/mcp-eur-lex
What is the Eur Lex MCP server?
Eur Lex is an MCP server listed in the public MCP registry as io.github.pipeworx-io/eur-lex. EUR-Lex MCP, official EU law, article-level. This page covers its npm package (@pipeworx/mcp-eur-lex).
Is the Eur Lex MCP server safe to use?
Eur Lex scores 84 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 Eur Lex MCP server expose?
Eur Lex exposes 8 tools: compliance_index, search_legislation, get_metadata, list_articles, get_article, and 3 more. Their descriptions and schemas cost roughly 1,109 tokens of context every time the server is loaded.
Is the Eur Lex MCP server still maintained?
Eur Lex 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 Eur Lex MCP server under?
Eur Lex declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.