Skip to content
EuroComply logo

EuroComply MCP server

Which servers in the official MCP registry are EuroComply's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-14

← Back to EuroComply

Whose server it is
  • Registry nameapp.eurocomply/complianceverified in the MCP registry

The registry name sits under eurocomply.app. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-14
  • Stateanswerschecked 2026-10-14
  • Tools12
  • Server calls itselfeurocomply
  • Server version0.5.0
  • Protocol version2024-11-05

On 2026-10-14 the server answered initialize and tools/list without a sign-in. First answer in 158 ms.

Tools it offers12 tools · read 2026-10-14
  • regulation_lookup

    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…

  • 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…

  • upcoming_deadlines

    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.

  • get_enforcement_actions

    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…

  • audit_local_ai_stack

    Audit an AI application architecture for EU AI Act risk classification, GDPR Chapter V international transfer exposure, and data sovereignty compliance. Checks provider, inference region, zero-retention flags, and use case against…

  • generate_executive_trust_dossier

    Generate an Executive Trust & Compliance Dossier (ETD) for B2B enterprise procurement and vendor onboarding. Includes Executive Passport, vector data flow diagram, tripartite evidence grid, and procurement approval memo. When no license…

  • answer_procurement_question

    Answer an enterprise procurement, security questionnaire, or RFP question regarding EU AI Act, GDPR, or data sovereignty. Returns an authoritative, legally and technically grounded response ready to paste into OneTrust, Whistic, or client…

  • autofill_security_questionnaire

    Auto-fill a batch of enterprise security, GDPR, and EU AI Act vendor questionnaire / RFP questions (e.g. OneTrust, SIG, Whistic, CAIQ, custom Excel). Returns structured answers with EUR-Lex statutory citations, technical proofs, and…

  • audit_repo_pull_request

    Audit a code diff, package.json dependencies, or source code snippet for EU AI Act obligations, non-EEA cloud data transfers, and prompt retention exposure. Generates a review-ready GitHub PR comment or CI/CD compliance report.

  • list_compliance_packs

    List all EuroComply commercial packs, emergency deal bundles, and statutory workbooks available for instant purchase via Polar. Returns price in EUR, key deliverables, and instant 1-click checkout URLs. Commercial packs unlock premium…

  • get_pack_checkout_link

    Generate an instant 1-click checkout link for any EuroComply compliance pack, emergency deal bundle, or dataset. Pre-fills customer email for zero-friction purchase. Returns direct payment URL (Polar MoR with EU VAT/reverse-charge…

  • verify_pack_license

    Verify a Polar license key or order transaction ID. Checks activation status and shows which premium MCP capabilities (e.g. Executive Trust Dossier, RFP Questionnaire Copilot) are active.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "compliance": {
      "type": "http",
      "url": "https://eurocomply.app/api/mcp"
    }
  }
}

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.