Acquis MCP server
{
"mcpServers": {
"acquis": {
"type": "http",
"url": "https://api.acquislaw.com/mcp"
}
}
}{
"mcpServers": {
"acquis": {
"type": "http",
"url": "https://api.acquislaw.com/mcp"
}
}
}{
"mcpServers": {
"acquis": {
"type": "http",
"url": "https://api.acquislaw.com/mcp"
}
}
}{
"servers": {
"acquis": {
"type": "http",
"url": "https://api.acquislaw.com/mcp"
}
}
}{
"mcpServers": {
"acquis": {
"type": "http",
"url": "https://api.acquislaw.com/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.0.0
What it does
Acquis provides MCP-enabled assistants with verbatim, verifiable access to current EU digital regulations including the AI Act, GDPR, DSA, DMA, and others. Every legal text is cryptographically signed and linked to EUR-Lex, allowing assistants to quote exact provisions with full citations rather than paraphrase from training data.
- Look up the exact wording of a specific EU regulation article by act name and article number, with current in-force status and EUR-Lex link.
- Search semantically across EU digital law to find relevant provisions matching a keyword or concept.
- Verify the authenticity and signing provenance of any legal citation returned by the assistant.
Tools this server exposes
| Tool | Does |
|---|---|
| search_eu_law | Semantic search over the EU law corpus returning ranked verbatim provisions with citations. |
| get_provision | Exact lookup of a provision by legal anchor (act name, article, paragraph, point, annex, or recital). |
| get_act_status | Retrieve an act's CELEX number, latest consolidation date, in-force information and coverage details. |
| list_versions | Show all stored versions of an article with their validity windows to see how text changed over time. |
| verify_fragment | Verify the content hash and ed25519 signing provenance of any returned legal citation. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.