Skip to main content
Glama
conformi-eu

conformi-search

Official
by conformi-eu
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

conformi-search — EU Legal Research MCP Server

Verifiable EU law for AI agents — every answer carries a CELEX number and an EUR-Lex deep link.

Language: English · Deutsch · Français

MCP Registry Wikidata License: MIT Corpus

MCP server for EU legal research with verifiable CELEX citations from the EUR-Lex corpus (German, English, French — each a native-language index, not machine translations). It exposes selected EU legal research tools to any MCP client and can optionally use a conformi API key for extended semantic search.

Research tool with primary-source citations — not legal advice, no attorney-client relationship.

Why this exists

LLMs answer EU-law questions plausibly but unverifiably. conformi-search returns answers that are checkable against the primary source: each result carries the CELEX number and a direct EUR-Lex link, so an agent (or a human) can verify the citation instead of trusting a hallucination. Works in Claude Code, Claude Desktop, Cursor, and any other MCP-capable harness.

Related MCP server: cellar-wrapper

Two ways to use it

1. Run it locally (stdio) — installable MCP server, no key needed for the free tools:

npm install && npm run build
node dist/index.js

Or with Docker:

docker build -t conformi-search-mcp .
docker run -i conformi-search-mcp

Add to an MCP client (e.g. Claude Desktop) config:

{
  "mcpServers": {
    "conformi-search": {
      "command": "node",
      "args": ["/path/to/conformi-search-mcp/dist/index.js"],
      "env": { "CONFORMI_API_KEY": "cfm_live_…  (optional, enables search_eu_law)" }
    }
  }
}

Without CONFORMI_API_KEY the two free tools are available. Setting the key adds the metered search_eu_law tool.

2. Use the hosted remote endpoint directly (Streamable HTTP, stateless):

https://conformi.eu/api/mcp

Registered in the official MCP Registry as eu.conformi/conformi-search. Wikidata: Q140166658

Tools

Tool

Auth

Billing

search_eu_law — semantic search across EU secondary law, results carry CELEX numbers + EUR-Lex deep links; optional valid_at time-travel filter

API key

metered per query

get_knowledge_article — curated report for one legal act (GDPR, AI Act, NIS2, DORA, CRA …) incl. legal-status (Rechtsstand) metadata

none

free

get_legal_timeline — application-date timeline for major acts (e.g. AI Act high-risk deadlines)

none

free

Getting an API key (machine-friendly)

The full contract incl. pricing and a machine-driven purchase flow is in the OpenAPI document:

https://conformi.eu/api/v1/openapi.json

7-day free trial on the Professional plan, €0 due today, cancel anytime before trial end.

Quick test (no key needed)

curl -X POST https://conformi.eu/api/mcp \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_knowledge_article","arguments":{"celex":"32024R1689"}}}'

Troubleshooting

Symptom

Cause & fix

search_eu_law returns isError with a purchase hint

No Authorization: Bearer key was sent. Free tools work without a key; search is metered — get a key via https://conformi.eu/api/v1/openapi.json

401 UNAUTHORIZED on search

Key invalid or revoked. Check the key in your conformi.eu account (Account → API Keys)

403 PLAN_REQUIRED / TRIAL_LIMIT_REACHED

Subscription inactive or the 50-query trial allowance is used up — activate the subscription

404 for a CELEX in get_knowledge_article

No curated report exists for that act yet. Try search_eu_law instead — the full corpus is searchable

Connection fails

The server speaks Streamable HTTP only (no SSE). POST JSON-RPC to https://conformi.eu/api/mcp; GET returns 405 by design

Anything else

Open an issue: https://github.com/conformi-eu/conformi-search-mcp/issues or mail info@conformi.eu

License

This repository documents the public endpoint. The hosted service, its source code and its data products are proprietary and governed by the conformi.eu terms — only the contents of this repository are MIT-licensed.

About

Built by conformi.eu — EU compliance research with verifiable sources.

Available Tools

2 tools
get_knowledge_articleA
Read-only

Pre-generated knowledge report for one EU legal act (CELEX number), including Rechtsstand (legal-status date) metadata. Free — no API key required. Research tool with primary-source citations (CELEX/EUR-Lex) — not legal advice, no attorney-client relationship.

ParametersJSON Schema
NameRequiredDescriptionDefault
celexYesCELEX number, e.g. 32024R1689 (AI Act)

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already mark readOnlyHint true. Description adds value by noting it's free, requires no API key, pre-generated, and not legal advice, which are behavioral traits not covered by annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no redundancy. First sentence states core purpose and content; second adds free usage and disclaimer. Every word serves a purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given one parameter, no output schema, and ample annotations, description sufficiently explains tool purpose, parameter meaning, output type, and behavioral context. Could briefly mention output format (e.g., whether text or URL) but still complete enough.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema provides pattern and example for celex parameter (100% coverage). Description enhances by clarifying it's 'for one EU legal act' and that output includes Rechtsstand metadata, adding context beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it provides a pre-generated knowledge report for one EU legal act using a CELEX number, including Rechtsstand metadata. Distinguishes from sibling tool 'get_legal_timeline' by focusing on report content rather than timeline.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies usage for research via 'Research tool' and 'Free — no API key required', but does not explicitly contrast with sibling or specify when not to use. No direct guidance on alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 2 tool updatesv1.0.0
    • First observedget_knowledge_article
    • First observedget_legal_timeline
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4/5.0
Disambiguation5/5

The two tools have clearly distinct purposes: one retrieves a knowledge report for a specific CELEX number, the other provides a timeline for a major EU act. No overlap in functionality.

Naming Consistency5/5

Both tools follow a consistent 'get_<descriptor>_<noun>' pattern: get_knowledge_article and get_legal_timeline. The naming is predictable and clear.

Tool Count3/5

With only 2 tools, the set is thin for a research server, but it may be acceptable given the focused scope on pre-generated reports and timelines. It falls below the typical 3-15 range.

Completeness2/5

The surface is incomplete for EU legal research: there is no way to search or list available acts, nor to get details beyond the two specific functions. Significant gaps exist for an agent working with EU law.

Maintenance

ActivityMaintained
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/conformi-eu/conformi-search-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server