The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the ActTrace listing page.
A developer-facing EU AI Act compliance API for non-financial SaaS and technology companies. ActTrace gives an engineering team three things, self-serve, over an API or via MCP:
Not legal advice. ActTrace provides operational compliance workflow support and documentation drafts. It does not provide legal advice, does not certify compliance, and does not replace review by qualified counsel. Every response carries this disclaimer.
ActTrace is scoped for non-financial companies. Financial-services use
cases (banking, trading, portfolio/investment advice, credit scoring, …) are
deliberately classified out_of_scope_financial_services.
ActTrace ships as a Claude Code plugin: an acttrace skill plus a local MCP
server. The MCP server runs via uvx — a deterministic rules engine, offline,
no API key.
Then ask Claude "Is my chatbot EU AI Act compliant?" or "Write an Article 50
notice for our support assistant." The MCP server also runs standalone with
any MCP client: uvx acttrace-mcp.
| Method & path | Auth | Tokens | Purpose |
|---|---|---|---|
POST /api/acttrace/diagnostics/free | none | 0 | Public risk diagnostic |
POST /api/acttrace/classify | key | 15 | Documented risk classification |
POST /api/acttrace/notices | key | 10 | Article 50 transparency notice |
POST /api/keys/generate | none | 0 | Issue a free-plan key |
GET /api/health | none | 0 | Liveness |
Auth is X-API-Key. Responses carry X-Request-ID, X-Plan,
X-Tokens-Charged, X-Tokens-Remaining, X-RateLimit-*. Errors are
structured {"code","message","detail"} (401/403/429).
python -m acttrace.mcp_server --sse --port 8002 exposes two tools —
acttrace_classify and acttrace_generate_transparency_notice — authenticated
with the same X-API-Key. A Claude Code skill is in skill/acttrace/.
54 tests: classification engine (7 acceptance fixtures), conflict guard, notice generator, and HTTP API contract.
docker-compose.yml builds a standalone two-container stack (API + MCP) on
ports 8080 / 8002 with its own volume — isolated from FinanceData2. To go live,
append caddy-acttrace.snippet to the shared Caddyfile (replace the
placeholder domain). See BLUEPRINT.md for the full build contract.