Cra Compliance MCP Server

EU Cyber Resilience Act (Reg 2024/2847) compliance MCP for products with digital elements. CE marking, vulnerability disclosure, SBOM. MIT

Local serverstdio

What is the Cra Compliance MCP MCP server?

Most developer tooling work still happens through a UI a human drives. Cra Compliance MCP MCP server moves it into the conversation instead. EU Cyber Resilience Act (Reg 2024/2847) compliance MCP for products with digital elements. CE marking, vulnerability disclosure, SBOM. MIT.

The tools it exposes

The server publishes 6 tools. What each one is 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

Getting it running

The server ships on npm as @smithery/cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What it needs from you

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.

How it compares

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. Cra 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.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

  • 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 Cra Compliance MCP MCP server

{
  "mcpServers": {
    "cra-compliance-mcp": {
      "command": "uvx",
      "args": ["cra-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 Cra Compliance MCP to Backward-compatible.
  • Use Cra Compliance MCP to Well.
  • Use Cra Compliance MCP to Production-ready.

Frequently asked questions

It connects Cra 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 Cra Compliance MCP directly.