ai-act-mcp
Related Servers
Alternatives to ai-act-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceScans codebases for AI frameworks, checks EU AI Act compliance, and generates compliance reports, roadmaps, and audit-ready packages.1612MIT
- AlicenseAqualityDmaintenanceScans codebases for AI system usage and generates EU AI Act compliance reports.450 npmMIT
- AlicenseAqualityBmaintenanceKeeps AI coding agents on track: checks the code they write for secrets, open databases, unsafe agent settings and request data reaching a query or shell, maps findings to OWASP, GDPR and the EU AI Act, and tells the agent to ask before changing anything. Runs locally.3853Apache 2.0

Legalithmofficial
AlicenseAqualityBmaintenanceEU AI Act compliance in your editor.Classify risk, cite obligations, draft Article 50 disclosures. Offline, no API key.71MIT- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to classify AI systems against the EU AI Act with requirement checklists and penalty exposure, generate and validate Factur-X / EN 16931 electronic invoices, and assess GDPR and NIS2 readiness directly from the IDE. Runs as a zero-dependency Python stdio server for Claude Desktop, Cursor, and similar clients.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceLocal-first AI compliance scanner via Model Context Protocol, scanning codebases for violations of DPDPA 2023, RBI FREE-AI, SEBI AI/ML, and the EU AI Act.82 PyPI1Apache 2.0
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: classifying risk, listing obligations, providing deadlines, and scanning documentation. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern (check_obligations, classify_risk, next_deadlines, scan_repo), making them predictable and easy to understand.
Four tools are well-suited for the domain of EU AI Act compliance, covering classification, obligations, deadlines, and documentation scanning without being too few or too many.
The tool surface covers the core lifecycle: understanding risk tier, knowing obligations, checking deadlines, and verifying documentation readiness. No obvious gaps for the stated purpose.