Dora Compliance MCP Server

DORA (Regulation EU 2022/2554) compliance MCP for financial entities. ICT risk, incident classification, reporting workflows. MIT

Local serverstdio

What is the Dora Compliance MCP MCP server?

Connect Dora Compliance MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. DORA (Regulation EU 2022/2554) compliance MCP for financial entities. ICT risk, incident classification, reporting workflows. MIT. The dora compliance mcp mcp server is what makes that connection.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Backward-compatible — when MEOK_PAYG_KEY is unset, behaviour is unchanged
  • Well — documented API
  • Production-ready — Active maintenance
  • Pro — ** £79/mo — Full MCP suite + EU AI Act tracking
  • Enterprise — ** £499/mo — Custom dev + SLA + Dedicated support
  • Domain — Purpose

Credentials and setup notes

Configuration is passed through the environment: MEOK_PAYG_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

Installation goes through your MCP client rather than a global install: point it at @smithery/cli on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Dora Compliance MCP's toolset — Backward-compatible, Well, Production-ready and 3 more — is a fair guide to whether it matches your workflow. It is maintained by csoai-org; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Dora Compliance MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
Backward-compatiblewhen MEOK_PAYG_KEY is unset, behaviour is unchanged.
Welldocumented API
Production-readyActive maintenance
Pro** £79/mo — Full MCP suite + EU AI Act tracking
Enterprise** £499/mo — Custom dev + SLA + Dedicated support
DomainPurpose

How to install the Dora Compliance MCP MCP server

{
  "mcpServers": {
    "dora-compliance-mcp": {
      "command": "uvx",
      "args": ["dora-compliance-mcp"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
MEOK_PAYG_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Dora Compliance MCP to Backward-compatible.
  • Use Dora Compliance MCP to Well.
  • Use Dora Compliance MCP to Production-ready.

Frequently asked questions

It connects Dora Compliance MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 6 tools (Backward-compatible, Well, Production-ready, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Dora Compliance MCP directly.