MCP

EU AI Act Scanner: scan a repo for AI frameworks

For a first pass over AI-framework traces in a local project. The free tier needs no key, but a scan still reads source and config files.

Official source · mcp-eu-ai-act

Install

pip install eu-ai-act-scanner

Who it's for

If you want an agent or a terminal to check whether a codebase uses AI frameworks and to run a compliance scan against the EU AI Act, this tool matches. It ships both a command line and an MCP server. It is not legal advice and will not write the conclusion of a compliance report for you.

Official notes:

https://github.com/ark-forge/mcp-eu-ai-act

Main prerequisite: you scan a local project directory. The free tier needs no signup and no API key; install and scan. The paid tier claims to open the full toolbox and mentions an August 2027 deadline; this page does not write paid-activation steps.

First try in 3 minutes

Use one official path: install eu-ai-act-scanner with pip, then run the same-named command in the project directory. Do not treat an alternate package name as the main path.

Prerequisites: Python / pip installed. The first try is a local scan only — do not start HTTP listening first.

Install command:

pip install eu-ai-act-scanner

Where to configure: MCP writes the service name as eu-ai-act and command as eu-ai-act-mcp. The evidence does not name a required client; do not add a roster. Before scanning, enter a real project directory; do not copy a sample directory name.

Low-risk first call: run eu-ai-act-scanner at the project root. Official text says it detects AI frameworks in source and config/manifest files, covering Python, JS, TS, Go, Java, and Rust — 16 frameworks in total. This reads the repo and does not change code, but it still walks your source files. Confirm that directory may go to the scanner. After MCP is attached, do the same kind of detection only; do not invent tool names.

Success signal: the command finishes and reports framework use, not a missing-key prompt. The free tier is written as just pip install and scan.

Use cases

Case 1: scan a local repo with the command line eu-ai-act-scanner. Official text writes CLI + MCP Server. What you can check is whether it reported framework traces. The evidence does not name those 16 frameworks; do not invent detection rules for the missing parts.

Case 2: attach the same scan to MCP with command eu-ai-act-mcp. This fits after the pip package is installed and you want an agent to ask about the current project. Up to here you can only confirm detection exists and walks local files. HTTP mode is another path for CI/CD or a remote client: first pip install uvicorn, then python3 server.py --http, listening on 0.0.0.0:8089. Do not use that as the first try.

Limits

No key is not zero risk. A scan reads source and config; that is a local-read boundary. HTTP mode binds 0.0.0.0:8089, which opens the scan port onto the network — do not start it before you accept that exposure.

If free-tier and paid-tier tool counts or daily quotas do not appear in the consecutive source, do not invent numbers. August 2027 is only a deadline official text mentions, not an automatic execution point of this tool. This guide only covers pip install, local scan, and stdio MCP. Do not extrapolate remote mode or the paid toolbox.