ai-act-governance
Related Servers
Alternatives to ai-act-governance
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for EU AI Act compliance classification with multi-jurisdiction overlay across 8 frameworks (NIST AI RMF, ISO 42001, GDPR, HIPAA, Colorado SB 24-205). Provides deterministic risk classifier (quick_risk_class) and Claude-powered Annex III deep classifier (classify_annex3) with remediation actions.29 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for EU AI Act compliance analysis — classify any AI system or workflow against Regulation (EU) 2024/1689, updated with AI Omnibus 2026.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to search and retrieve cited passages from the EU AI Act in English or Italian, including full articles and cross-references, so agents can ground answers in verified regulatory text.MIT
- AlicenseAqualityDmaintenanceLets AI assistants classify an AI system under the EU AI Act, returning risk tier, obligations, and deadlines based on a plain-English description of the product.46 npmMIT
- AlicenseAqualityBmaintenanceConnects Claude Desktop, Cursor, and other MCP clients to a governed enterprise architecture context engine so assistants can answer map-grounded, evidence-cited questions and optionally propose document enrichment for human approval.18MIT
- AlicenseAqualityBmaintenanceAn MCP server providing structured intelligence about the EU AI Act, including risk classification, deadline tracking, obligations, penalties, and article lookups.10217 npm4MIT
TDQS
Scored across 7 tools
Each tool targets a distinct object: identity (whoami), application list/detail (list_applications, get_application), per-use-case obligation detail (obligations_for_use_case), gap aggregation (evidence_gaps), portfolio rollup (portfolio_exposure), and tier proposal (classify_use_case). The main potential confusion is list_applications vs portfolio_exposure and obligations_for_use_case vs evidence_gaps, but the descriptions clearly mark one as detail and the other as aggregate, so an agent can choose correctly.
All names are snake_case and readable, with action tools following verb_noun (list_applications, get_application, classify_use_case) and reporting tools following noun phrases (evidence_gaps, portfolio_exposure, obligations_for_use_case). The split between verb-led and noun-led conventions is a minor deviation, and whoami is a conventional outlier rather than a real inconsistency.
Seven tools is well within the sensible range and each one covers a distinct governance need (identity, inventory, detail, obligations, gaps, rollup, classification). Nothing appears redundant or tacked on for the stated compliance scope.
The surface is read-heavy: it can inspect applications, obligations, gaps and exposure, and classify_use_case proposes a tier, but there is no tool to persist that proposal, attach/refresh evidence, or update an application or assessment. This leaves a notable dead end, since the classify tool explicitly says compliance must review before it enters the inventory and no review or write path exists.