MEOK publishes a server per regime — Article 50 watermarking, incident reporting, NIST RMF and the rest. This is the piece that sits across them, so reach for it when your question spans more than one framework and for the specific servers when it does not. The README is thin on which thirteen frameworks and which tools; the vendor's documentation site is the place to settle that before you build a workflow on it.
The orchestration layer of the MEOK compliance suite: rather than one server per regulation, this one coordinates thirteen regulatory frameworks behind a single connection and produces signed audit receipts for what it assessed.
- Thirteen regulatory frameworks addressed through one server, instead of installing and switching between one server per regime
- Signed compliance attestations on the paid tier, which an auditor verifies independently rather than taking your word or contacting the vendor
- A free tier that needs no key at all — useful for finding out what it answers before deciding whether to pay
- The rest of the MEOK fleet installable alongside it in one command, if you want the individual per-regulation servers as well
No key on the free tier, which allows 10 calls a day. Install with `pip install meok_governance_engine_mcp`, or through the Smithery installer for Claude Desktop; the package is `meok-governance-engine-mcp` (1.0.18 in pyproject and server.json) and runs over stdio. The signed attestations are a paid-tier feature — the free tier answers, but does not produce the artefact an auditor can verify.
One command — pip install meok_governance_engine_mcp