AG

Api Governance

io.github.coderifts/api-governance

Signed, offline-verifiable contract-change authorization. Only a granted change can proceed.

Yes, your AI can use this right now.Answered a live MCP handshake in 316 ms with no sign-in needed and exposes 3 tools.

Connect it

Settings → Connectors → Add custom connector
URL: https://app.coderifts.com/mcp

3 tools, verified live

Pulled straight from the server with tools/list on 2026-10-17.
preflight_change_set

Use this when: a contract artifact (OpenAPI, GraphQL, protobuf, AsyncAPI, MCP manifests, or agent tool schemas) changes before merge, deploy, publish, or tool registration; AND any agent-executed operation with no supported contract type — send type agent_operation. Do not call for documentation-only changes, static readiness scoring, or receipt verification. Use analyze for risk only; authorize r

verify_receiptread-only

Verify a CodeRifts signed chain-receipt you ALREADY HOLD: cryptographic authenticity (signature + key id), body binding, and — when lifecycle indices are available — whether it is currently valid authorization (not expired, superseded, or revoked) for a stated operation/target. Use this when: - You already obtained a chain_receipt / receipt token from a prior preflight (or CI artifact) and are

get_decision_detailsread-only

Retrieve a PAST CodeRifts decision by exactly one identifier (case_id | decision_id | fingerprint): full report, breaking changes, scores, and linked receipt metadata if stored. Use this when: - You have a decision_id (or fingerprint) from a previous preflight, PR comment, or CI log and need to inspect or explain that past decision. - You are auditing why a prior ALLOW/WARN/BLOCK was issued. -

Alternatives in Developer Tools

Compare →
Try “Notion”, “Stripe”, “create invoice”, “browser”