io.github.ark-forge/mcp-eu-ai-act

MCPcommunitylive
v2.0.31io.github.ark-forgeUnknownUpdated 5mo agoGitHub

EU AI Act + GDPR compliance scanner. One call, no arguments, 10 seconds. 22 AI frameworks detected.

One command. Zero config. Full EU AI Act + GDPR compliance report in under 10 seconds. Detects 16 AI frameworks in your codebase, maps each to binding legal articles, returns pass/fail with fix instructions. Free tier, no API key needed. August 2, 2026 enforcement deadline. Fines up to 35M EUR or 7% global turnover. If this tool helps your compliance work, a ⭐ on GitHub helps others discover it.…

Endpoint healthlive
checked 9 days ago · 642ms
100% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
11GitHub stars
2Forks
5mo agoLast update
Package
Authorio.github.ark-forge
LicenseUnknown
Version2.0.31
Sourcemcp-registry
GitHubark-forge/mcp-eu-ai-act
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scan✓ CleanvHEAD · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

No tool declarations found in the source3mo ago

Forge read 0 source files from the repository archive and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

One command. Zero config. Full EU AI Act + GDPR compliance report in under 10 seconds. Detects 16 AI frameworks in your codebase, maps each to binding legal articles, returns pass/fail with fix instructions. Free tier, no API key needed. August 2, 2026 enforcement deadline. Fines up to 35M EUR or 7% global turnover. If this tool helps your compliance work, a ⭐ on GitHub helps others discover it. Need audit-grade proof? Certify every scan with ArkForge Trust Layer — tamper-proof, timestamped…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.