Compliance MCP Server

EU AI Act compliance audit trails and evidence generation for AI agent systems — risk classification

Local serverstdio

What is the Compliance MCP server?

Compliance MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. EU AI Act compliance audit trails and evidence generation for AI agent systems — risk classification.

What you get

  • Risk Classification — — Classify AI systems as Unacceptable, High, Limited, or Minimal risk per the EU AI Act framework
  • Audit Trails — — Create and maintain decision logs with full traceability (input, output, reasoning, human oversight, model, confidence)
  • Gap Analysis — — Identify missing compliance requirements with specific article references and actionable recommendations
  • Evidence Packages — — Generate auditor-ready documentation suitable for regulatory submission
  • Enforcement Timeline — — Track upcoming deadlines with days remaining and penalty structure

What the assistant can call

Once Compliance is connected, these are the calls the assistant has available:

  • assess_risk_level — Classify an AI system under EU AI Act risk framework
  • create_audit_trail — Start a compliance audit trail for an AI system
  • log_decision — Log an AI decision with full traceability metadata
  • check_compliance_gaps — Identify missing compliance requirements
  • generate_evidence_package — Generate auditor-ready evidence documentation
  • get_enforcement_timeline — Show upcoming enforcement deadlines and penalties

Setting it up

compliance-shield-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Choosing this one

Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Compliance's toolset — assess_risk_level, create_audit_trail, log_decision and 3 more — is a fair guide to whether it matches your workflow. It is maintained by mdfifty50-boop; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

  • 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.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the compliance mcp server does with a few real requests.

Available tools

ToolWhat it does
assess_risk_levelClassify an AI system under EU AI Act risk framework
create_audit_trailStart a compliance audit trail for an AI system
log_decisionLog an AI decision with full traceability metadata
check_compliance_gapsIdentify missing compliance requirements
generate_evidence_packageGenerate auditor-ready evidence documentation
get_enforcement_timelineShow upcoming enforcement deadlines and penalties

How to install the Compliance MCP server

### Claude Desktop

```json
{
  "mcpServers": {
    "compliance-shield": {
      "command": "npx",
      "args": ["compliance-shield-mcp"]
    }
  }
}

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

Example prompts to try

  • Use Compliance to assess risk level.
  • Use Compliance to create audit trail.
  • Use Compliance to log decision.

Frequently asked questions

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