mcp server
EuroComply — EU Regulatory Compliance
EU regulatory compliance data: 17 regulations, deadlines, enforcement actions. EU-hosted.
Description as published by the maintainer. Source
- version 0.3.0
- active
- security
active — Registry entry last updated 2026-05-19. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
4 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
get_enforcement_actions(limit, country, urgency, regulation)- Return recent EU enforcement actions ingested from official DPA publications (CNIL, Garante, ICO, AEPD, APD, Dutch AP, BfDI, EDPB, ESMA, EBA, EIOPA, CJEU, BSI, ANSSI). Filter by country, regulation, or urgency. Each result includes source authority, regulation, title, summary, urgency (high/medium/low), publication date, and official source URL. Data is sourced directly from supervisory authority RSS feeds and updated continuously.
list_regulations- List all EU regulations tracked by EuroComply with their short name, regulation number, CELEX, status, in-force date, application date, and a one-paragraph summary. Useful when the user wants an overview or to discover what regulations exist.
regulation_lookup(name)- Look up a single EU regulation tracked by EuroComply. Returns the canonical structured entry: full name, regulation number, CELEX, summary, scope, status, in-force/application dates, all key dates with Article references, max fine with tier breakdown, supervising authorities, applies-to, sector applicability, primary articles map, EUR-Lex URL, and EuroComply hub URL. Accepts the short name (e.g. 'GDPR'), full name, or slug. Required: name.
upcoming_deadlines(within_days)- Return upcoming regulatory deadlines across all tracked EU regulations within the next N days (default 365). Each result includes regulation shortName, date, event description, and Article reference. Sorted ascending by date.
Last successful function declaration observed on . Source: https://eurocomply.app/api/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://eurocomply.app/api/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 0.3.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-05-19 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-05-19 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 4 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | eurocomply.app | |
| mcp endpoint status | ok | The server listed 4 functions when asked. | as of probe | eurocomply.app |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json