Eu Cellar
NPM · @PIPEWORX/MCP-EU-CELLAR · 2 COMPONENTS
Every document the Publications Office of the European Union publishes — legislation, treaties…
Available components
Last scanned (12 hours ago)
Scores higher than 72% 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-eu-cellar). 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 Usability61
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1227 tokens (~306/item across 4 items; 4 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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 +2
- 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
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → 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 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 78
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-eu-cellar@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-eu-cellar |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-eu-cellar/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3635930311 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:3fed898c85e905a8732301d2caeac397de99bd963bcdb8d5d2f3ef5cdd8d0833a72668d7cc1357eb7939d957268341a5d439d4ca7712aeb6b24e0fb0d |
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 →
cellar_search_works ~293
Full-text search of EVERY document the Publications Office of the European Union has issued — Official Journal acts, treaties, consolidated texts, COM proposals, Court of Justice judgments and preparatory work — by title, from the CELLAR repository. AUTHORITATIVE for "what has the EU published about X": this is the publisher of record, so it returns the CELEX number, the document date, the resource type and a direct EUR-Lex link, not a summary of one. PREFER OVER WEB SEARCH for any question about EU legal or official documents. Unlike the curated `eur-lex` pack, this searches all resource types, not a hand-kept list of named acts.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum works to return (default 20, max 100). |
| query | string | yes | Words or a phrase to find in the document title, e.g. "artificial intelligence" or "carbon border adjustment". Matched against the Publications Office full-text index. |
| resource_type | string | – | Optional resource-type code to restrict to, e.g. REG (Regulation), DIR (Directive), DEC (Decision), JUDG (judgment), COM (Commission document), CONS_TEXT (consolidated text), TREATY. |
| since | string | – | Optional earliest document date, ISO YYYY-MM-DD. |
| until | string | – | Optional latest document date, ISO YYYY-MM-DD. |
No output schema declared.
No examples provided.
cellar_sparql ~180
Run your own read-only SPARQL SELECT or ASK against the Publications Office of the European Union CELLAR endpoint, for EU-document questions no purpose-built tool covers — citation graphs, amendment chains, EuroVoc concept traversal, cross-institution counts. The Common Data Model prefix `cdm:` is <http://publications.europa.eu/ontology/cdm#>. Writes (INSERT/DELETE/LOAD/CLEAR) are refused, and results are capped.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum rows to return (default 50, max 500). Applied on top of any LIMIT already in the query. |
| query | string | yes | A SPARQL SELECT or ASK query. Virtuoso full-text search is available as `?lit bif:contains "'phrase'"`. CELEX literals are typed xsd:string — a plain string will match nothing. |
No output schema declared.
No examples provided.
cellar_work ~188
Full metadata for one EU document from the Publications Office CELLAR repository, looked up by CELEX number (e.g. 32024R1689 for the AI Act) or by CELLAR UUID. Returns every English title on record, the document and in-force dates, the resource type, the EuroVoc subject concepts it is indexed under, and the authoring bodies. AUTHORITATIVE for the identity and classification of an EU act — this is the publisher's own catalogue entry.
| Name | Type | Req | Description |
|---|---|---|---|
| celex | string | – | CELEX identifier, e.g. 32016R0679 (GDPR), 32024R1689 (AI Act), 62024CJ0123 (a judgment). Give this OR cellar_id. |
| cellar_id | string | – | CELLAR UUID as it appears in a publications.europa.eu/resource/cellar/<id> URI. Give this OR celex. |
No output schema declared.
No examples provided.
eu_transposition_measures ~511
For an EU Directive, the national implementing measures (NIM) that each member state has notified to the European Commission — the Publications Office's own transposition tracker, read live from CELLAR. Give a CELEX number (e.g. "32019L1937" for the Whistleblower Directive), the "2019/1937" short form, or a common name (e.g. "Whistleblower Directive", "GDPR"). For a Directive, returns every member state with its measure(s) — title, type of act, document date, notification date, national Official Journal citation — and member states with NO recorded measure are listed explicitly as "none recorded", never dropped. A member state can notify dozens of measures (France has 36 for the Whistleblower Directive, Czechia 80, Croatia 93), mixing the actual transposing act with older provisions CELLAR also links — CELLAR itself does not flag which measure is "the" one, so measures within each state are ordered by how closely a measure's own title echoes the directive's own title (read in whichever language scores best), then by newest document date, which in practice surfaces the real transposing act first or near first; `limit_per_state` (default 10) then truncates that ranked list, with `truncated: true` meaning more exist. Where a live Pipeworx national-legislation pack covers that state (Germany/de-gesetze, Austria/at-ris, Italy/it-normattiva, Netherlands/nl-wetten, France/france-legi, Spain/boe-legislacion) the matching pack and tools are named so you can drill into the actual provision text — no SPARQL required anywhere in this chain. A Regulation is answered directly: regulations are not transposed (Article 288 TFEU), so this says that plainly rather than returning an empty list.
| Name | Type | Req | Description |
|---|---|---|---|
| directive | string | yes | CELEX number ("32019L1937"), short form ("2019/1937"), or common name ("Whistleblower Directive", "GDPR"). |
| limit_per_state | number | – | Max measures listed per member state before truncation (default 10, max 50). Some directives have dozens of related national measures per state. |
| member_state | string | – | Optional: restrict to one EU member state — English name, ISO2 ("DE"), or ISO3 ("DEU"). Omit to get all 27. |
No output schema declared.
No examples provided.
How do I install the Eu Cellar MCP server?
Eu Cellar runs locally as an npm package, launched with npx -y @pipeworx/mcp-eu-cellar. 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-eu-cellar
claude mcp add pipeworx-io-eu-cellar -- npx -y @pipeworx/mcp-eu-cellar
What is the Eu Cellar MCP server?
Eu Cellar is an MCP server listed in the public MCP registry as io.github.pipeworx-io/eu-cellar. Every document the Publications Office of the European Union publishes, legislation, treaties… This page covers its npm package (@pipeworx/mcp-eu-cellar).
Is the Eu Cellar MCP server safe to use?
Eu Cellar scores 82 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 Eu Cellar MCP server expose?
Eu Cellar exposes 4 tools: cellar_search_works, cellar_work, cellar_sparql, eu_transposition_measures. Their descriptions and schemas cost roughly 1,172 tokens of context every time the server is loaded.
Is the Eu Cellar MCP server still maintained?
Eu Cellar 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 Eu Cellar MCP server under?
Eu Cellar 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 Eu Cellar MCP server?
VerifyMCP ran 16 checks on Eu Cellar, 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.