The metering is the unusual part: leave `MEOK_PAYG_KEY` unset and the server runs as it always did; set it and every call draws on a prepaid balance that works across the vendor's other compliance servers too. The three tools are named but not documented in depth, so run one against a system you know before building a review process on top of it.
A Python server for ISO 42001 compliance work: AI management-system assessment, risk management, AI lifecycle governance and certification readiness. It belongs to a fleet of compliance servers that share one pay-per-call token.
- An audit pass over a management system — `audit_management_system`
- An AI risk assessment — `assess_ai_risk`
- A generated policy template — `generate_policy_template`
- Optional metering: with `MEOK_PAYG_KEY` set, each call draws down a prepaid balance and the tool returns a top-up URL when it reaches zero
`pip install iso_42001_ai_mcp`, or have the client launch `uvx` with the `iso-42001-ai-mcp` package over stdio. With `MEOK_PAYG_KEY` unset, behaviour is unchanged and nothing is deducted. With it set, calls cost £0.05 each by default and `MEOK_PAYG_RATE_GBP` changes that; `MEOK_X402_RECEIVER` enables paying in USDC on Base L2. The PyPI package is `iso-42001-ai-mcp` 1.1.10.
One command — pip install iso_42001_ai_mcp