What it does
The CRA Compliance MCP server supports compliance with the EU Cyber Resilience Act (Regulation (EU) 2024/2847) for products with digital elements. Its documented topics include CE marking, vulnerability disclosure and the software bill of materials (SBOM). It exposes three tools: classify_product, audit_annex_i and sbom_skeleton.
A developer or compliance team working on a product with digital elements could use it to have an AI assistant work through CRA questions, such as how a product is classified, how it measures against Annex I requirements, or how to start an SBOM. It is listed under the security and development categories.
It is installed with pip install cra-compliance-mcp and started with the cra-compliance-mcp command, which uses stdio transport. For Claude Desktop it is added to claude_desktop_config.json; other MCP clients are configured in their own config files. Once connected, the assistant is prompted to call a named tool, for example to run classify_product or sbom_skeleton on a described product.
Limitations and requirements
Use of the publisher's hosted pay-per-call billing requires a top-up and a token from councilof.ai/payg, with top-up tiers of £10, £50 and £200. The default rate is £0.05 per call, and it can be configured through MEOK_PAYG_RATE_GBP. The publisher describes a free tier of 50 calls per day. Pay-per-call is inactive when MEOK_PAYG_KEY is not set.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
io.github.CSOAI-ORG/cra-compliance-mcp
EU Cyber Resilience Act (Regulation 2024/2847) compliance for AI agents. Product classification...
v1.3.15As shown on registry.modelcontextprotocol.io when we last read it