EU Regulatory Grounding
PYPI · EU-REG-MCP
Cited ESMA MiCAR register search and change tracking, white paper linting, EU AI Act classification
Available components
Last scanned (3 hours ago)
Scores higher than 61% of PyPI servers
Category Crypto and Web3
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 28 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 382 tokens (~76/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 18 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 17 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Security disclosure: fail → pass ▲ functional
- 16 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 15 Oct 26 66
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 18 Oct 2026 · Analysed pypi/eu-reg-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| 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 →
classify_eu_ai_act_system ~67
Classify an AI system's EU AI Act risk tier with pinpoint citations. Pass a SystemProfile as JSON; pass an empty string to get the schema. Requires the optional `classify` extra; degrades to an install hint.
| Name | Type | Req | Description |
|---|---|---|---|
| profile_json | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
lint_micar_whitepaper ~64
Lint a draft MiCAR white paper (JSON) against Annex I-III rules. Returns cited candidate findings pending human review. Requires the optional `lint` extra; degrades to an install hint when absent.
| Name | Type | Req | Description |
|---|---|---|---|
| whitepaper_json | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
micar_register_changes ~49
Recent register movement: new filings, changed entries, removals. change_type: all | added | changed | removed.
| Name | Type | Req | Description |
|---|---|---|---|
| change_type | string | – | – |
| limit | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
micar_register_summary ~22
Current totals per MiCAR register and white paper format coverage.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
search_micar_register ~104
Search the ESMA interim MiCAR register by entity name or LEI. query: entity-name substring (case-insensitive) or an exact LEI. register_slug: all | other-wp | emt-wp | art-wp | casps | ncasp. member_state: optional two-letter code (DE, IE, MT, ...).
| Name | Type | Req | Description |
|---|---|---|---|
| member_state | string | – | – |
| query | string | yes | – |
| register_slug | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the EU Regulatory Grounding MCP server?
EU Regulatory Grounding runs locally as a PyPI package, launched with uvx eu-reg-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · eu-reg-mcp
claude mcp add sebastianfoerste-eu-reg-mcp -- uvx eu-reg-mcp
What is the EU Regulatory Grounding MCP server?
EU Regulatory Grounding is an MCP server listed in the public MCP registry as io.github.sebastianfoerste/eu-reg-mcp. Cited ESMA MiCAR register search and change tracking, white paper linting, EU AI Act classification. This page covers its PyPI package (eu-reg-mcp).
Is the EU Regulatory Grounding MCP server safe to use?
EU Regulatory Grounding scores 51 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 18 October 2026. 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 Regulatory Grounding MCP server expose?
EU Regulatory Grounding exposes 5 tools: search_micar_register, micar_register_summary, micar_register_changes, lint_micar_whitepaper, classify_eu_ai_act_system. Their descriptions and schemas cost roughly 306 tokens of context every time the server is loaded.
Is the EU Regulatory Grounding MCP server still maintained?
EU Regulatory Grounding is still listed as active in the MCP registry. We last reached this channel on 18 October 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 Regulatory Grounding MCP server under?
EU Regulatory Grounding declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.