Home / MCP registry index / one.clevsec/eu-compliance

ClevSec EU compliance tools

one.clevsec/eu-compliance in the official MCP registry. Endpoint https://mcp.clevsec.one/mcp.

The registry describes it as: Deterministic, sourced EU compliance checks: NIS2, DORA, GDPR and the Cyber Resilience Act.

We read its 28 tools on 2026-10-30. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http eu-compliance https://mcp.clevsec.one/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "eu-compliance": {
      "url": "https://mcp.clevsec.one/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"eu-compliance","type":"http","url":"https://mcp.clevsec.one/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

reporting_deadlines nis2_scope_check nis2_gap_assessment dora_classify_incident dora_checklist dora_gap_assessment gdpr_breach_decision gdpr_fine_estimate gdpr_checklist_assessment gdpr_dpia_screening privacy_notice_requirements data_flow_record_check cookie_consent_check cra_reporting_check iso27001_gap_assessment vendor_risk_assessment maturity_assessment cyber_risk_score nis2_remediation_plan dora_remediation_plan gdpr_remediation_plan gdpr_dpia_report data_flow_review cookie_consent_fix_plan iso27001_remediation_plan vendor_due_diligence_plan maturity_improvement_plan cyber_risk_action_plan

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-30): 30a3aaa9d9aeaa2f. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/one-clevsec-eu-compliance/badge.svg)](https://lazaretto.dev/mcp-registry/one-clevsec-eu-compliance)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.