mcpbeat

API Governance MCP Server

io.github.coderifts/api-governance
answering

API Governance is answering right now. Last checked 8 min ago. It exposes 3 tools. Last commit 16 Jul 2026.

API governance for AI agents. Detects breaking changes, scores blast radius, blocks unsafe calls.

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
3
Tools
read from the server
166 ms
Response time
average over 24h
0
Stars
last commit 16 Jul 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add api-governance --transport http https://app.coderifts.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "api-governance": {
      "url": "https://app.coderifts.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.api-governance]
url = "https://app.coderifts.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "api-governance": {
      "url": "https://app.coderifts.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "api-governance": {
      "url": "https://app.coderifts.com/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

decision
get_decision_details
Retrieve a PAST CodeRifts decision by decision_id (or fingerprint): full report payload, breaking changes list, 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. - You are NOT requesting a new analysis of current before/after specs. Do not use when: - You need a decision for the CURRENT uncommitted or PR head change set — call coderifts.preflight_change_set with the current artifacts. - You hold a receipt token and only need cryptographic/lifecycle verification — use coderifts.verify_receipt. - You have no decision_id/fingerprint — run preflight first to create one. Inputs: decision_id (preferred) and/or fingerprint. Returns the stored decision document or not_found.
preflight
preflight_change_set
Preflight a COMPLETE base→head change set of contract artifacts and return a governance decision (ALLOW / WARN / REQUIRE_APPROVAL / BLOCK), risk score, breaking-change analysis, and a signed chain-receipt when applicable. Use this when: - You are about to merge, push to a protected branch, deploy, publish a package, or register/expose agent tools, AND the change includes at least one contract artifact: OpenAPI/Swagger, GraphQL SDL, gRPC/protobuf, AsyncAPI, MCP manifest, or agent tool schemas (inputSchema/JSON Schema tools list). - You have (or can assemble) the FULL base and head (or before/after) content for every changed contract artifact in this change set — not a single-file subset when other contract files also change. - You need a NEW decision for the CURRENT change; you do not already hold a currently-valid receipt for this exact target/operation. Do not use when: - The change is documentation-only (README, guides, comments) with no contract artifact content change — do not call any CodeRifts tool. - You already hold a signed receipt and only need to check it is authentic and currently valid — use coderifts.verify_receipt instead. - You need details of a PREVIOUS decision by decision_id — use coderifts.get_decision_details instead. - You only want a static "agent readiness" score of a single unspec-diffed file with no pending mutate — that is a specialized non-default alias, not this tool. - You cannot supply both before and after (or base and head) for the artifacts that change — fix the change set first; do not invent empty before specs. Inputs: list of artifacts, each with type, before, after (or equivalent), plus optional operation (merge|deploy|tool_call|publish), environment/stakes, and context. Returns decision, execution_action, risk fields, and chain_receipt when issued.
verify
verify_receipt
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 about to act (merge/deploy) under that receipt. - A contract-gate or policy requires offline/online proof that the receipt is authentic for this change before proceeding. - You must distinguish "signature ok" from "currently authorized" (stale or superseded receipts must not be treated as live approval). Do not use when: - You do not have a receipt yet — call coderifts.preflight_change_set first. - You need a NEW decision for a changed base→head set — preflight again; verify_receipt does not re-diff specs. - You only need human-readable history of an old decision_id without a receipt token — use coderifts.get_decision_details. - The change set itself is unknown or incomplete — fix the change set and preflight; do not "verify" a placeholder. Inputs: receipt token (required); optional expected target_id, operation, and now-skew policy hooks. Returns { valid, status, currently_authorized (bool|null), reason, payload, authz_* }. Branch on currently_authorized; null = not evaluated.

Endpoints

URLTransportStateLatencyChecked
https://app.coderifts.com/mcp streamable-http answering 174 ms 8 min ago

API Governance — questions

Answers built from our own checks of this server.

What can API Governance do?
It exposes 3 tools, read directly from the server on our last check. Among them: get_decision_details, preflight_change_set, verify_receipt. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is API Governance working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 166 ms. The bar chart above shows every period we have measured.
How do I connect API Governance?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does API Governance need an API key?
No. API Governance completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is API Governance?
It answers our handshake in 166 ms on average, which is faster than 70% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is API Governance open source?
Yes — 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.