sebastianfoerste/eu-reg-mcp

**Let your AI assistant answer MiCAR and EU AI Act questions with citations instead of guesses — every finding flagged for human legal review.**
Scope today: the ESMA interim MiCAR register (search, summary, change tracking), MiCAR white paper linting, and EU AI Act risk-tier classification. Other EU regulation is not covered.
> *Screenshot/GIF placeholder — to be added*
Who it's for
- **Crypto-asset compliance and legal teams** looking up entities on the ESMA interim MiCAR register (white papers, authorised CASPs, non-compliant entities) and tracking what changes on it, including removals.
- **Teams preparing MiCAR white papers** who want a deterministic Annex I–III check of a draft that returns cited candidate findings.
- **Teams assessing AI systems under the EU AI Act** who want a first-pass risk-tier classification with pinpoint Art. 5 / Annex III / GPAI citations.
It does not replace legal review: its outputs are register facts or candidate flags for a human to assess (see Guardrails).
Try it now
There is no hosted playground. eu-reg-mcp is a Model Context Protocol (MCP) server, so you try it by adding it to your own MCP client — the Quick start has the configuration for Claude Code and Claude Desktop. Then ask your assistant:
- "Is on the MiCAR register, and what format is its white paper?"
- "What changed on the MiCAR register recently — any removals?"
- "Classify this AI system under the EU AI Act" (paste a system profile; call with an empty string to get the schema).
The first two work without extras; the third needs the classify extra.
Quick start
eu-reg-mcp is on PyPI and requires Python 3.13 or newer. With uv installed, uvx fetches and runs it.
**Claude Code**
The register tools need no API key. For all five tools, add the lint and classify extras instead:
Claude Desktop ( claude_desktop_config.json )
For the extras, use "args": ["--from", "eu-reg-mcp[lint,classify]", "eu-reg-mcp"].
Without uv, run pip install 'eu-reg-mcp[lint,classify]' in a Python 3.13+ virtual environment and register its eu-reg-mcp by full path, e.g. claude mcp add eu-reg -- /path/to/.venv/bin/eu-reg-mcp; the environment need not be active. Install options and network use: docs/tools.md.
Example output
> **Synthetic data.** Produced on 2026-10-14 by running this repo's register code (register.search_entries / register.recent_changes) against the **synthetic test fixtures** in tests/fixtures/, not the live register. The entity and its LEI are test data. Output shape is what a live call returns; values are not.
search_micar_register(query="skygate"):
micar_register_changes(change_type="removed") returns the same kind of cited record (snapshot date, register, entity) and notes that *"the register itself does not state why"* an entry was removed. With the extras installed, the lint and classify tools cite the provision behind each finding, for example Anhang I Teil A MiCAR (MiCAR Annex I, Part A), Art. 5(1)(f) AIA, Annex III(4)(a) AIA, and Art. 51 AIA for a general-purpose AI model with systemic risk. Sample output from synthetic inputs: docs/tools.md.