EU Audit Trail
Record tamper-evident audit events for EU AI Act and GDPR obligations while your agent builds or runs AI features.
Overview
io.github.jellewas/eu-audit-mcp is a Ship-phase MCP server that provides a tamper-evident audit trail for EU AI Act and GDPR compliance.
What is this MCP server?
- Tamper-evident audit trail MCP server (PyPI eu-audit-mcp v0.1.1)
- Framed for EU AI Act and GDPR compliance workflows
- YAML-driven configuration via optional AUDIT_CONFIG path
- stdio transport for local agent integration
- PyPI package eu-audit-mcp version 0.1.1
- One documented optional environment variable AUDIT_CONFIG
- Server title EU Audit Trail in MCP registry metadata
What problem does it solve?
EU-facing AI products need credible audit history, but indie teams rarely have tooling that agents can write to during development and operations.
Who is it for?
Solo builders shipping AI features to EU users who need agent-accessible, tamper-evident audit logging.
Skip if: Teams outside EU regulatory scope with no audit mandate, or anyone expecting turnkey legal compliance without policy work.
What do I get? / Deliverables
After setup, your agent can append and query compliance-oriented audit events through MCP using your YAML audit configuration.
- Stdio MCP server emitting tamper-evident audit events
- Agent-invokable audit trail aligned to your EU compliance config
Recommended MCP Servers
Journey fit
How it compares
Compliance audit-trail MCP server, not a penetration-test skill or privacy policy generator.
Common Questions / FAQ
Who is eu-audit-mcp for?
Builders and small teams shipping AI or data-heavy products in the EU who need MCP-accessible audit trails for GDPR and EU AI Act documentation.
When should I use eu-audit-mcp?
Use it in Ship security prep and ongoing Operate monitoring when you must log agent and system actions in a tamper-evident way.
How do I add eu-audit-mcp to my agent?
Install eu-audit-mcp from PyPI, set AUDIT_CONFIG to your YAML file path if needed, register the stdio MCP server in Claude Code or Cursor, then call audit tools from your workflows.