Mcp Server
Connects Claude to GovernMy.ai's rules engine for querying AI compliance obligations across EU AI Act, ISO 42001, Colorado AI Act, NIST AI RMF, HIPAA, SOX, and FTC guidance. Exposes six tools: get_obligations returns applicable rules for your system context, classify_risk_tier determines EU AI Act classification, list_frameworks shows coverage, get_rule fetches individual obligations, get_evidence_requirements pulls artifact specs, and get_cross_references maps obligations across frameworks. Every response includes a humanReviewRequired flag and explicit notice that results are obligations, not compliance verdicts. Requires a GovernMy.ai API key. Reach for this when scoping regulatory surface area for AI systems or comparing framework requirements during design and documentation phases.
- tools
- 6
- auth
- Secret needed
- transport
- STDIO
- env vars
- 2
- last updated
- Apr 25, 2026
Tools
6 toolsPublic tool metadata for what this MCP can expose to an agent.
get_obligationsquery obligations that apply to an AI system given context (risk tier, role, industry, etc.)
query obligations that apply to an AI system given context (risk tier, role, industry, etc.)
No parameter schema in public metadata yet.
classify_risk_tierclassify an AI system's EU AI Act risk tier (unacceptable / high / limited / minimal)
classify an AI system's EU AI Act risk tier (unacceptable / high / limited / minimal)
No parameter schema in public metadata yet.
list_frameworkslist the frameworks the engine covers with metadata
list the frameworks the engine covers with metadata
No parameter schema in public metadata yet.
get_rulefetch the full payload for a single obligation by id
fetch the full payload for a single obligation by id
No parameter schema in public metadata yet.
get_evidence_requirementsfetch required evidence artifacts for a set of obligations
fetch required evidence artifacts for a set of obligations
No parameter schema in public metadata yet.
get_cross_referencesfetch cross-framework mappings for an obligation
fetch cross-framework mappings for an obligation
No parameter schema in public metadata yet.
Sponsors
Agent CaffeineSponsoredClose your lid, come back to finished work
SnugSponsoredThe clipboard manager for the AI eraPromote your product hereReach 125k+ visitors monthly
WaxSponsoredBlock anything with supervision, without erasing your iPhonePromote your product hereReach 125k+ visitors monthly
knobsSponsoredSee your site on any phone, any day, in any languageConfiguration
GOVERNMY_API_KEY*secretYour GovernMy.ai API key. Get a free one at https://governmy.ai/developers
GOVERNMY_API_URLOverride the API base URL. Defaults to https://api.governmy.ai
Readme
@governmyai/mcp-server
GovernMy.ai MCP server — query AI governance obligations from Claude Desktop, Cursor, or any MCP-compatible client.
Covers EU AI Act, ISO 42001, Colorado AI Act, NIST AI RMF, HIPAA (AI provisions), SOX (AI provisions), and FTC AI guidance.
What this does
This MCP server gives an AI assistant (like Claude) the ability to query GovernMy's rules engine directly while you're working. You can ask questions like:
- "What EU AI Act obligations apply if I build a hiring AI for the EU?"
- "Which frameworks does this cover?"
- "What evidence do I need for EU AI Act Article 10 data governance?"
- "Does my ISO 42001 Clause 6 work also cover any NIST AI RMF functions?"
...and get structured regulatory obligations back as part of the conversation.
Important: this tool returns obligations, not verdicts. It never tells you "you're compliant" or "you're not compliant" — those are determinations only a human reviewer can make. Every response includes a humanReviewRequired flag where applicable.
Copy-paste into Claude
After installing + restarting, try one of these:
Details
- Repository
- github.com/governmyai/mcp-server
- Package
@governmyai/mcp-server- Transport
- STDIO
- Auth
- Required
- Registry
- MCP registry, active