Enforcement — days until EU AI Act enforcement deadline — August 2, 2026
April 7, 2026 mcp.arkforge.tech
FR EN
Model Context Protocol Server — v2.0

EU AI Act
compliance
in your IDE.

Ten MCP tools covering the full compliance lifecycle: scan, score, roadmap, Annex IV evidence package, and Trust Layer cryptographic certification.

Get started → GitHub
Claude Cursor Windsurf REST API MIT License
generate_annex4_package + certify
$ claude "Generate Annex IV package and certify it"

▸ generate_annex4_package
§1 General description ……… ✓
§2 Development process ……… ✓
§3 Training methodology ……… ✓
§4 Testing & validation ……… ✓
§5 Risk management ……………… ✓
§6 Monitoring procedures ……… ✓
§7 Human oversight ……………… ✓
§8 Data governance ……………… ✓

Package: annex4_2026-04-07.zip (8 sections)
Manifest SHA-256: a3f9bc…

▸ certify_compliance_report
proof_id: proof_e8f3c12a9b
timestamp: 2026-04-07T09:42:11Z
signature: Ed25519 ✓ RFC 3161
Verify: trust.arkforge.tech/verify/proof_e8f3c12a9b
10 MCP tools

The complete compliance toolset.

Each tool maps directly to EU AI Act obligations. Use them independently or chain them in a full compliance workflow.

01

scan_project

Detect AI frameworks in your codebase. Python, JS, TS, Go, Java, Rust. 16 frameworks including OpenAI, LangChain, HuggingFace, TensorFlow.

Art. 52 · Art. 11
02

check_compliance

Score your compliance documents 0–100 against 14 articles. Sections present, keywords, citations, minimum length — not just file existence.

Art. 9 · Art. 10 · Art. 13
03

suggest_risk_category

Classify your AI system: unacceptable, high-risk, limited, or minimal. Mapped to Annex III categories with justification.

Art. 5 · Art. 6
04

generate_compliance_roadmap

Week-by-week action plan sorted by legal criticality × implementation effort. Art. 52 (transparency) always week 1. Deadline-aware for Aug 2, 2026.

All articles
05

generate_annex4_package

Generate a ZIP with all 8 official Annex IV sections, SHA-256 manifest, and optional Trust Layer certification embedded.

Annex IV
06

certify_compliance_report

Cryptographic proof via Trust Layer. Ed25519 signature + RFC 3161 timestamp. Public verification URL for auditors. Art. 12 compliant.

Art. 12
07

generate_report

Two-level output: executive summary for DPO/legal (deadline-aware) + technical breakdown for developers (article-by-article with citations).

Art. 11 · Art. 17
08

generate_compliance_templates

Generate compliance document templates: risk management plan, data governance policy, transparency notice, Model Card, incident log.

Art. 9 · Art. 10 · Art. 50
09

get_actionable_guidance

Article-specific actionable guidance. For each gap, get concrete implementation steps, documentation requirements, and timeline estimates.

All articles
10

get_compliance_status

Current compliance state summary: score, gaps, articles met, articles failing, and next priority action. Suitable for CI/CD pass/fail gates.

CI/CD · REST API
Trust Layer — Art. 12

The only MCP that certifies
its own reports.

Every Certified plan report is signed cryptographically via ArkForge Trust Layer. Ed25519 + RFC 3161 timestamp. Tamper-proof. Auditor-ready.

§

How it works

Your compliance report is hashed and signed via POST trust.arkforge.tech/v1/proxy. The proof_id is embedded in your Annex IV package. Anyone can verify the report was not modified after certification.

Ed25519 RFC 3161 SHA-256
Verification example
# Verify any certified report
curl https://trust.arkforge.tech/v1/verify/proof_e8f3c12a9b

{
"status": "valid",
"timestamp": "2026-04-07T09:42:11Z",
"signature": "Ed25519",
"article": "Art. 12 — Record keeping",
"tampered": false
}
Pricing

Three plans. One deadline.

Free
€0 / forever

10 REST scans/day. Open source. No account.

  • scan_project
  • check_compliance (content scoring)
  • suggest_risk_category
  • generate_report
  • get_actionable_guidance
  • MCP: Claude, Cursor, Windsurf
  • REST API (10 req/day/IP)
  • MIT License
Install from GitHub →
Pro
€29 / month

All 10 tools. Unlimited scans. Compliance roadmap. Annex IV package.

  • All Free tools
  • generate_compliance_roadmap
  • generate_annex4_package
  • generate_compliance_templates
  • get_compliance_status
  • Unlimited REST API
  • API key authentication
  • CI/CD integration
  • Email support (48h)
Certified
€99 / month

All Pro + automatic Trust Layer certification on every report.

  • All Pro tools
  • certify_compliance_report
  • Annex IV package + proof_id embedded
  • Ed25519-signed reports
  • RFC 3161 timestamp
  • Public verification URLs
  • Art. 12 audit trail compliant
  • Priority support
Quick start

Add to your IDE in 90 seconds.

01

Add MCP server

Add mcp.arkforge.tech/mcp to Claude Desktop, Cursor, or Windsurf settings.

02

Scan your project

Ask Claude to scan your codebase and classify its risk level under the EU AI Act.

03

Get your roadmap

Receive a scored report + week-by-week action plan prioritized for the Aug 2, 2026 deadline.

04

Generate & certify

Export your Annex IV evidence package. Certify with Trust Layer. Share the proof URL with your auditors.

claude_desktop_config.json
{ "mcpServers": { "eu-ai-act": { "url": "https://mcp.arkforge.tech/mcp" } } }

August 2, 2026 is your deadline.

Start with the free scanner. Upgrade when you need the roadmap, Annex IV package, or certified reports.

Start free on GitHub