A side-by-side look at the Eu Reg MCP and Sovereign AI Act MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Eu Reg MCP for legal work as a local process; choose Sovereign AI Act MCP for legal as a local process. You can also run both side by side in one mcpServers block.
search_micar_register, micar_register_summary, micar_register_changes.SOVEREIGN_API_BASE.classify_ai_system, lookup_article, search_eu_ai_act.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 55/100 · Good | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | SOVEREIGN_API_BASE |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 5 | 4 |
| Full listing | View Eu Reg MCP | View Sovereign AI Act MCP |
search_micar_registerLook up an entity by name or LEI in the ESMA interim MiCAR registermicar_register_summaryRegister totals and white paper format coveragemicar_register_changesNew filings, changed entries, removalslint_micar_whitepaperDeterministic Annex I–III lint of a draft white paperclassify_eu_ai_act_systemAI Act risk tier with pinpoint citationsclassify_ai_systemClassify an AI system under the EU AI Act (Regulation (EU) 2024/1689 as amended by Regulation (EU) 2026/1744). Give a plain-language description of what the system does and it returns the risk tier (prohibited / high_risk / limited / minimal), the exact Annex III category where applicable, and the binding Articles — every reference grounded verbatim in the law. USE THIS when the user asks whether an AI system is high-risk or prohibited, what obligations apply to it, or which Articles bind a specific AI use-case. For looking up one known Article use lookup_article; for keyword search use search_eu_ai_act.lookup_articleReturn the verbatim text of one specific EU AI Act Article (1–113), exactly as published in the Official Journal of the EU. USE THIS when the user names or asks for a known Article number (e.g. 'show me Article 6', 'what does Article 5 say'). For keyword/topic search across the whole law use search_eu_ai_act; to classify a system use classify_ai_system.search_eu_ai_actFull-text keyword search across the entire EU AI Act corpus — all Articles (1–113), Recitals (1–180) and Annexes (I–XIII) — returning the provisions that match your terms, each grounded verbatim in the law. USE THIS when you want to find where a topic, term or obligation is addressed but do not know the Article number (e.g. 'where does the law cover human oversight?', 'find biometric categorisation', 'rules for GPAI'). To fetch one known Article use lookup_article; to assess a specific system's risk tier use classify_ai_system.get_compliance_deadlinesReturn the canonical EU AI Act application timeline (the staggered dates each obligation starts to apply, as amended by Regulation (EU) 2026/1744, the Digital Omnibus on AI, in force 27 July 2026) together with the penalty/fine tiers under Article 99. Takes no arguments. USE THIS when the user asks when the EU AI Act (or a specific obligation) applies, what the key compliance deadlines are, or how large the fines can be.Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
{
"mcpServers": {
"sebastianfoerste-eu-reg-mcp": {
"command": "uvx",
"args": [
"eu-reg-mcp"
]
}
}
}
{
"mcpServers": {
"sovereign-ai-act-mcp": {
"command": "npx",
"args": [
"-y",
"sovereign-ai-act-mcp"
],
"env": {
"SOVEREIGN_API_BASE": "YOUR_SOVEREIGN_API_BASE_HERE"
}
}
}
}