Home / MCP registry index / io.github.ark-forge/mcp-eu-ai-act
io.github.ark-forge/mcp-eu-ai-act
io.github.ark-forge/mcp-eu-ai-act in the official MCP registry.
Endpoint https://mcp.arkforge.tech/mcp. Source: github.com/ark-forge/mcp-eu-ai-act.
The registry describes it as: EU AI Act + GDPR compliance scanner. One call, no arguments, 10 seconds. 22 AI frameworks detected.
We read its 16 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
scan_project check_compliance generate_report suggest_risk_category generate_compliance_templates generate_compliance_roadmap generate_annex4_package certify_compliance_report validate_api_key register_free_key gdpr_scan_project gdpr_check_compliance gdpr_generate_report gdpr_generate_templates combined_compliance_report get_pricing
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-ark-forge-mcp-eu-ai-act)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.