INDIVIDUAL MCP TOOL

cookie_consent_fix_plan

Use after cookie_consent_check when the user wants to fix their cookie consent.

clevsec.onenone authenticationAvailability not checked

LIVE ENDPOINT

https://mcp.clevsec.one/mcp

No auth detected

Connect to this endpoint to inspect the live schema for cookie_consent_fix_plan and invoke it with your own arguments.

{}

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.clevsec]
url = "https://mcp.clevsec.one/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "clevsec": {
      "type": "http",
      "url": "https://mcp.clevsec.one/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: clevsec
Remote MCP URL: https://mcp.clevsec.one/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "clevsec": {
      "type": "http",
      "url": "https://mcp.clevsec.one/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "clevsec",
  "transport": "streamable-http",
  "url": "https://mcp.clevsec.one/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

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?
nis2_scope_check — Use for questions like 'does NIS2 apply to my company?
nis2_gap_assessment — Use to assess how ready an organisation is for NIS2 cybersecurity requirements, or to find its gaps.
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 whether it must be reported under DORA.
dora_checklist — Use for 'what does DORA require?
dora_gap_assessment — Use to assess how ready a financial entity is for DORA, or to find its gaps.
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 whether the GDPR requires notifying the supervisory authority within 72 hours (Art.
gdpr_fine_estimate — Use for 'how big could a GDPR fine be?