# Eur Lex (npm · @pipeworx/mcp-eur-lex)

EUR-Lex MCP — official EU law, article-level.

- Trust score: 84/100 (high trust)
- Change this week: +11
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 78/100, [markdown](https://verifymcp.io/servers/pipeworx-io-eur-lex/eur-lex-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-eur-lex/eur-lex-mcp)
- npm · `@pipeworx/mcp-eur-lex`: 84/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-eur-lex/pipeworx-mcp-eur-lex.md), [page](https://verifymcp.io/servers/pipeworx-io-eur-lex/pipeworx-mcp-eur-lex)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-eur-lex`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-eur-lex).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add pipeworx-io-eur-lex -- npx -y @pipeworx/mcp-eur-lex
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-eur-lex": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-eur-lex"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-eur-lex": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-eur-lex"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-eur-lex -- npx -y @pipeworx/mcp-eur-lex
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-eur-lex": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-eur-lex"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-eur-lex --command npx --arg -y --arg @pipeworx/mcp-eur-lex
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-eur-lex:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-eur-lex"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-eur-lex": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-eur-lex"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-eur-lex -t stdio -c npx -a -y @pipeworx/mcp-eur-lex
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-eur-lex": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-eur-lex"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 84, +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.

### 2026-11-03 (score 83, +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.

### 2026-11-01 (score 82, +1)

- [security regression] 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.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.10
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-30 (score 81, +8)

- [security improvement] Known CVEs: unverified → pass
- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 73)

First indexed and scored.

## MCP tools (8)

### `compliance_index` (~132 tokens)

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.

Input parameters:

- `query` (string): Optional filter — name/alias/keyword (e.g. "AI Act", "data"). Omit to list the whole corpus.

### `search_legislation` (~113 tokens)

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.

Input parameters:

- `limit` (number): Max results (default 10, max 25).
- `query` (string, required): Keyword(s) that must appear in the English title, e.g. "cybersecurity certification".
- `type` (string): Optional: restrict to a legal act type.

### `get_metadata` (~127 tokens)

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.

Input parameters:

- `celex` (string, required): 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, …).

### `list_articles` (~75 tokens)

Table of contents for an act: every Article number and its heading. Use to discover which Article to quote before calling get_article.

Input parameters:

- `celex` (string, required): CELEX id or a known alias (e.g. "DORA").
- `lang` (string): ISO 639-2/B language code (default "eng").

### `get_article` (~156 tokens)

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").

Input parameters:

- `article` (string, required): Article selector: "17", "5,6,17", or "5-9". Suffixed numbers like "9a" are supported.
- `celex` (string, required): CELEX id or a known alias (e.g. "GDPR").
- `lang` (string): ISO 639-2/B language code (default "eng").

### `get_document` (~128 tokens)

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.

Input parameters:

- `celex` (string, required): 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).

### `cjeu_search` (~208 tokens)

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.

Input parameters:

- `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, required): Words appearing in the case title, e.g. "data protection", "state aid", "trade mark".

### `cjeu_judgment` (~170 tokens)

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.

Input parameters:

- `case_number` (string, required): 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).

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-eur-lex/pipeworx-mcp-eur-lex#diagnostics

## Score history

- 2026-11-05: 84
- 2026-11-04: 83
- 2026-11-03: 83
- 2026-11-02: 82
- 2026-11-01: 82
- 2026-10-31: 81
- 2026-10-30: 81
- 2026-10-29: 73

## Common questions

### 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.

### What did VerifyMCP test on the Eur Lex MCP server?

VerifyMCP ran 16 checks on Eur Lex, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-eur-lex
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-eur-lex
- Repository: https://github.com/pipeworx-io/mcp-eur-lex
- Website: https://pipeworx.io/packs/eur-lex
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-eur-lex/pipeworx-mcp-eur-lex.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-eur-lex/pipeworx-mcp-eur-lex/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-eur-lex/pipeworx-mcp-eur-lex.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-eur-lex/pipeworx-mcp-eur-lex