ActTrace
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:
- A deterministic risk classification of an AI feature under the EU AI Act.
- A ready-to-ship Article 50 transparency notice.
- A free diagnostic as the public entry point.
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.
Install — Claude Code plugin / MCP server
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.
/plugin marketplace add goww7/acttrace
/plugin install acttrace@acttrace
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.
Quickstart
python3 -m venv .venv && .venv/bin/pip install -r requirements.txt
.venv/bin/uvicorn acttrace.app:app --reload --port 8080
# 1. Free diagnostic — no key needed
curl -s localhost:8080/api/acttrace/diagnostics/free -H 'content-type: application/json' -d '{
"feature_name": "AI reply assistant",
"description": "Drafts suggested customer support replies for agents.",
"user_facing": true, "model_provider": "OpenAI", "use_case": "support_assist"
}'
# 2. Mint an API key
KEY=$(curl -s -XPOST localhost:8080/api/keys/generate | python3 -c 'import sys,json;print(json.load(sys.stdin)["api_key"])')
# 3. Classify (15 tokens)
curl -s localhost:8080/api/acttrace/classify -H "X-API-Key: $KEY" -H 'content-type: application/json' -d '{
"feature_name": "AI reply assistant",
"description": "Drafts customer support replies shown to agents.",
"use_case": "support_assist", "user_facing": true, "model_provider": "OpenAI"
}'
# 4. Generate an Article 50 notice (10 tokens)
curl -s localhost:8080/api/acttrace/notices -H "X-API-Key: $KEY" -H 'content-type: application/json' -d '{
"ai_system_name": "Support Copilot", "notice_type": "chatbot", "tone": "plain"
}'
Endpoints
| 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).
MCP
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/.
Tests
.venv/bin/python -m pytest -q
54 tests: classification engine (7 acceptance fixtures), conflict guard, notice generator, and HTTP API contract.
Deploy
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.
Layout
acttrace/
app.py config.py dependencies.py
middleware/ api_key_auth.py
routers/ acttrace.py keys.py
services/ acttrace_service.py acttrace_classification_service.py
acttrace_notice_service.py acttrace_constants.py
api_key_service.py
repositories/ acttrace_repository.py api_key_repository.py
schemas/ acttrace.py
mcp_server/ server.py __main__.py context.py tools/acttrace.py
skill/acttrace/ SKILL.md README.md
tests/
Metadata
Release files for acttrace-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| acttrace_mcp-0.1.0.tar.gz | 34.6 kB | Without provenance | Details for acttrace_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| acttrace_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for acttrace_mcp-0.1.0-py3-none-any.whl |
Total release size: 71.5 kB
Release files / acttrace_mcp-0.1.0.tar.gz
| Download URL | acttrace_mcp-0.1.0.tar.gz |
|---|---|
| Size | 34.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c5461012f1cc58db1dee54ae966dc5ae97bbd56c65604f877ccebf8e5e7842fc
|
|
BLAKE2b-256 checksum How to use checksums |
f51f9058bf8f62d91a840f6fc526f20fdbb4dfaf3407e519573a444aa60d7804
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Release files / acttrace_mcp-0.1.0-py3-none-any.whl
| Download URL | acttrace_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 36.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
251938fc0d9fc6ee8db9e63dc966d012d7d860f22aba99cb6230716ad1490ed4
|
|
BLAKE2b-256 checksum How to use checksums |
9867facc34928ff1f742ad2a31af5de780ec772ab06c4cf98d1a96c918f35297
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for acttrace-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.