ClevSec EU compliance tools

Name: ClevSec EU compliance tools
Author: one.clevsec

MCP serverMCP

Deterministic, sourced EU compliance checks: NIS2, DORA, GDPR and the Cyber Resilience Act.

by one.clevsechomepage ↗v1.2.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"clevsec-eu-compliance-tools","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability12/12 checks ok

30 days ago

Endpoints

https://mcp.clevsec.one/mcpmcp streamable http · checked on a schedule

Registry facts

Not distributed through a package registry we index.

when	check	result	http	latency	detail
3 h ago	mcp initialize	ok	200	31 ms	server clevsec 1.2.1 · protocol 2025-06-18 · 28 tools
9 h ago	mcp initialize	ok	200	31 ms	server clevsec 1.2.1 · protocol 2025-06-18 · 28 tools
16 h ago	mcp initialize	ok	200	48 ms	server clevsec 1.2.1 · protocol 2025-06-18 · 28 tools
22 h ago	mcp initialize	ok	200	99 ms	server clevsec 1.2.1 · protocol 2025-06-18 · 28 tools
29 h ago	mcp initialize	ok	200	31 ms	server clevsec 1.2.1 · protocol 2025-06-18 · 28 tools
2 d ago	mcp initialize	ok	200	56 ms	server clevsec 1.2.0 · protocol 2025-06-18 · 28 tools
2 d ago	mcp initialize	ok	200	67 ms	server clevsec 1.2.0 · protocol 2025-06-18 · 28 tools
2 d ago	mcp initialize	ok	200	46 ms	server clevsec 1.2.0 · protocol 2025-06-18 · 28 tools
2 d ago	mcp initialize	ok	200	78 ms	server clevsec 1.2.0 · protocol 2025-06-18 · 28 tools
3 d ago	mcp initialize	ok	200	52 ms	server clevsec 1.2.0 · protocol 2025-06-18 · 28 tools

Tools observed via MCP handshake

reporting_deadlines — Use for any question about incident or breach reporting deadlines in the EU (for example 'how long do we have to report a breach / a cyber incident?'). Lists wh
nis2_scope_check — Use for questions like 'does NIS2 apply to my company?', 'are we an essential or important entity?' or 'is a company of this size and sector in scope?'. Indicat
nis2_gap_assessment — Use to assess how ready an organisation is for NIS2 cybersecurity requirements, or to find its gaps. Call without answers to get the 53 questions in nine domain
dora_classify_incident — Use when a bank, insurer, investment firm, payment or crypto-asset firm or other financial entity has an IT outage, cyber attack or data incident and asks wheth
dora_checklist — Use for 'what does DORA require?', DORA compliance checklists or gap reviews. Returns the core DORA (Regulation (EU) 2022/2554) requirements for financial entit
dora_gap_assessment — Use to assess how ready a financial entity is for DORA, or to find its gaps. Call without answers to get the 39 questions in five pillars (ICT risk management,
gdpr_breach_decision — Use when a personal data breach has happened (data lost, stolen, sent to the wrong person, encrypted by ransomware, accessed without authorisation) to decide wh
gdpr_fine_estimate — Use for 'how big could a GDPR fine be?' or 'how are GDPR fines calculated?'. Applies step 2 of the EDPB Guidelines 04/2022 method: the Art. 83(4) or 83(5) legal
gdpr_checklist_assessment — Use to check how far an organisation is with GDPR compliance, or to list what GDPR requires in practice. Call without input to get the 48 checklist items in 8 a
gdpr_dpia_screening — Use when someone plans new processing of personal data (a new system, AI use, monitoring, profiling) and asks whether a data protection impact assessment is req
privacy_notice_requirements — Use when writing or checking a privacy policy or privacy notice. Lists every item the GDPR requires with its article, for data collected from the person (Art. 1
data_flow_record_check — Use when someone maps personal data flows or builds GDPR records of processing activities (ROPA, Art. 30). Give the flows (name, purpose, data categories, recip
cookie_consent_check — Use when someone asks whether their cookie banner or cookie consent is compliant in the EU (ePrivacy Art. 5(3) and GDPR consent rules). Call without answers to
cra_reporting_check — Use when a manufacturer of hardware or software sold in the EU learns of an actively exploited vulnerability or a security incident in its product. Applies Art.
iso27001_gap_assessment — Use to check how close an organisation is to ISO/IEC 27001:2022 certification, or to list the Annex A controls in practice. Call without answers to get 41 contr
vendor_risk_assessment — Use when an organisation evaluates a supplier, SaaS or ICT provider (vendor due diligence, third-party risk, supply chain security under NIS2 Art. 21(2)(d) or D
maturity_assessment — Use to measure an organisation's cybersecurity maturity or to benchmark it against NIST CSF 2.0. Call without answers to get 39 capabilities in the six CSF func
cyber_risk_score — Use for a quick view of a small organisation's cyber risk ('how secure are we?', 'what is our cyber risk score?'). Call without answers to get 15 weighted quest
nis2_remediation_plan — Use after nis2_gap_assessment when the user wants a plan to close their NIS2 gaps. Turns the same answers into every gap with a recommended action, a priority,
dora_remediation_plan — Use after dora_gap_assessment when the user wants a plan to close their DORA gaps. Turns the same answers into every gap with a recommended action, a priority,
gdpr_remediation_plan — Use after gdpr_checklist_assessment when the user wants a plan to close their GDPR gaps. Turns the same input into every open item with a recommended action, a
gdpr_dpia_report — Use after gdpr_dpia_screening when the user needs the DPIA worked out: a risk register linking each high or medium risk to its measures with coverage and indica
data_flow_review — Use after data_flow_record_check for a compliance review of each personal data flow: legal basis, special category and children's data, consent and legitimate i
cookie_consent_fix_plan — Use after cookie_consent_check when the user wants to fix their cookie consent. Returns every open item with the fix, its legal source (ePrivacy, GDPR, CJEU Pla
iso27001_remediation_plan — Use after iso27001_gap_assessment when the user wants a plan towards ISO/IEC 27001 certification. Turns the same statuses into every gap with a recommended acti
vendor_due_diligence_plan — Use after vendor_risk_assessment when the user needs to act on a vendor's gaps. Returns every gap with an action, the evidence to request from the vendor, ISO 2
maturity_improvement_plan — Use after maturity_assessment when the user wants to raise their maturity. Lists every capability below the target level (3 or 4) with the next action, NIST CSF
cyber_risk_action_plan — Use after cyber_risk_score when the user wants to reduce their risk. Returns every gap with a recommended action, a priority, NIST CSF 2.0 and NIS2 references a

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryone.clevsec/eu-compliance

first seen 3 d ago · fetched 3 d agoopen ↗

Field history (6 recent events)

3 d ago · declared · summary → "Deterministic, sourced EU compliance checks: NIS2, DORA, GDPR and the Cyber Resilience Act."
3 d ago · declared · description → "Deterministic, sourced EU compliance checks: NIS2, DORA, GDPR and the Cyber Resilience Act."
3 d ago · declared · publisherName → "one.clevsec"
3 d ago · declared · homepageUrl → "https://clevsec.one/mcp/"
3 d ago · declared · version → "1.2.0"
3 d ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from