Back to Browse

Api Governance MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

Contract-change authorization for AI agents. Signed receipts verify offline.

About

Contract-change authorization for AI agents. Signed receipts verify offline.

Remote endpoints: streamable-http: https://app.coderifts.com/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.

3 tools verified · Open access · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

file_system

Check that this permission is expected for this type of plugin.

env_vars

Check that this permission is expected for this type of plugin.

Shell Command Execution

Runs commands on your machine. Be cautious — only use if you trust this plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "io-github-coderifts-api-governance": {
      "url": "https://app.coderifts.com/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

CodeRifts — contract-change authorization

Only a granted change can proceed. Before a contract change merges, deploys or registers, CodeRifts decides whether it is authorized — and the check is red without a grant.

One grant binds three things: the authorization, its single use, and the target state the change moves to. The decision is signed, and the receipt verifies offline — you do not have to trust our database to check what was authorized.

Every decision also names what it does not prove.

  • Hosted MCP server: https://app.coderifts.com/mcp
  • Manifest: https://coderifts.com/mcp.json — the canonical published document. The mcp.json at the root of this repository is a pointer to it, not a second copy.
  • Official MCP Registry: io.github.coderifts/api-governance
  • Website: https://coderifts.com
  • Live demo PR: https://github.com/coderifts/demo/pull/4

Claude Code plugin

Install the CodeRifts marketplace, then the api-governance plugin (MCP server + skill). Requires CODERIFTS_API_KEY for tool calls.

/plugin marketplace add coderifts/api-governance
/plugin install api-governance@coderifts

Local checkout (after clone):

/plugin marketplace add .
/plugin install api-governance@coderifts

The plugin wires the hosted MCP at https://app.coderifts.com/mcp and the api-governance skill. Tools exposed: preflight_change_set, verify_receipt, get_decision_details only.


Cursor plugin

Cursor Plugin package (measured Cursor layout: .cursor-plugin/plugin.json + skills/ + rules/ + mcp.json + hooks/hooks.json). Same hosted MCP and the same three tools as the Claude plugin — no fourth tool. Deterministic / signed / fail-closed — not an AI compatibility scan.

PathRoleSource of truth
plugins/api-governance-cursor/.cursor-plugin/plugin.jsonCursor Plugin manifestcursor/plugins plugin.schema.json
plugins/api-governance-cursor/skills/coderifts-api-governance/SKILL.mdSkillWebsite .well-known/agent-skills/coderifts-api-governance/SKILL.md
plugins/api-governance-cursor/rules/coderifts.mdcCursor ruleGeneratedgenerate-agent-host-files.js
plugins/api-governance-cursor/mcp.jsonStreamable HTTP MCP wiringSame endpoint as Claude .mcp.json (not the website tool-card)
plugins/api-governance-cursor/hooks/hooks.jsonPreToolUse adapterExisting CLI coderifts claude-hook (ID912)
.cursor-plugin/marketplace.jsonCursor marketplace entryCursor marketplace.schema.json

Validate:

npm run validate:cursor

The generated-rule check is LIVE when CODERIFTS_APP_ROOT (default ~/coderifts-app) has generated/agent-host/.cursor/rules/coderifts.mdc, and RECORDED against fixtures/recorded/app-generator when it does not (weaker, named). A missing or corrupt snapshot still exits 1 — no silent skip.

Peter — local Cursor load before publish: symlink or add plugins/api-governance-cursor as a local plugin, exercise skill + rule + MCP + hook, then submit https://github.com/coderifts/api-governance at cursor.com/marketplace/publish (open-source, Cursor review).


OpenAI / Codex package

Codex plugin package (measured OpenAI Codex layout: .codex-plugin/plugin.json + .mcp.json + skills/ + AGENTS.md). Same hosted MCP and the same three tools as the Claude plugin — no fourth tool.

PathRoleSource of truth
plugins/api-governance-openai/.codex-plugin/plugin.jsonCodex plugin manifestCodex plugin-json-spec (scaffold skill)
plugins/api-governance-openai/.mcp.jsonStreamable HTTP MCP wiringSame endpoint as Claude .mcp.json
plugins/api-governance-openai/skills/api-governance/SKILL.mdSkill + tool listTrigger wording from agent-setup rule; tool names/descriptions from generated mcp.json
plugins/api-governance-openai/AGENTS.mdAgent rules fileGeneratedcoderifts agent-setup / generate-agent-host-files.js
plugins/api-governance-openai/openai-agent-instructions.mdOpenAI Agents SDK instructionsGenerated — same generator
plugins/api-governance-openai/docs/openai-production-pattern.mdProduction pattern (ID108) — host dispatch loop with executeOpenAIToolCallHand-authored recipe on shipped @coderifts/agent-guard ≥ 6.4.0 (first npm release that exports executeOpenAIToolCall; current npm 17.3.3)
plugins/api-governance-openai/scripts/smoke-execute-openai-tool-call.mjsOffline smoke (ALLOW + BLOCK; no OpenAI key)Real dispatcher + stub client
.agents/plugins/marketplace.jsonCodex marketplace entryCodex marketplace schema

Production pattern (function-calling apps)

OpenAI’s model only emits tool_call JSON; your app executes it. Wire governance at that host loop — not as a Claude-style PreToolUse hook. Full steps + one canonical loop:

plugins/api-governance-openai/docs/openai-production-pattern.md

# Offline smoke (needs ~/coderifts-agent-guard built, or CODERIFTS_AGENT_GUARD_ROOT)
npm run smoke:openai-dispatch

As of 2026-09-14 this command fails on one assertion (ALLOW factory ran — execute() did not run; the remaining ALLOW and BLOCK assertions pass). Investigation is in progress.

Local checkout in Codex (team marketplace path):

# From a clone of this repo, point Codex at .agents/plugins/marketplace.json
# then install api-governance-openai (UI / plugin install — see Codex plugin docs).

Validate package consistency (manifest, tool parity, AGENTS.md empty-diff vs regeneration):

npm run validate:openai
# or: node scripts/validate-openai-package.js

AGENTS.md regeneration is LIVE when ~/coderifts-app (or CODERIFTS_APP_ROOT) exists, and RECORDED against fixtures/recorded/app-generator when it does not (weaker, named). A missing or corrupt snapshot still exits 1. Directory listing / account submission steps are not automated here.


GitHub Copilot kit

Reference copies of the generated Copilot MCP configs + instructions (single source: coderifts-app generators). Same hosted MCP and the same three tools — no fourth tool.

Primary install (living command — prefer this over copying from the kit):

npx coderifts copilot-setup
# optional: --out <dir>   --check (drift-gate)   --force

Agent-host instructions (including .github/copilot-instructions.md) come from:

npx coderifts agent-setup

Three Copilot surfaces (root keys differ)

From the generated guide (copilot/docs/copilot-mcp.md — do not re-author this table):

SurfaceConfig locationRoot keyAuth
VS Code / Copilot Chat.vscode/mcp.jsonservers${input:coderifts_api_key} + inputs[]
Copilot cloud agent + code reviewRepo Settings → Copilot → MCP servers (paste JSON)mcpServersAgents secret COPILOT_MCP_CODERIFTS_API_KEY in headers
Custom agent (org/enterprise)Agent profile .md YAML frontmattermcp-servers${{ secrets.COPILOT_MCP_CODERIFTS_API_KEY }}

Tools allowlisted everywhere: preflight_change_set, verify_receipt, get_decision_details.

Vendored reference tree (copilot/)

PathRoleSource of truth
copilot/.vscode/mcp.jsonVS Code / Copilot ChatGeneratedgenerate-copilot-mcp.js
copilot/copilot-cloud-agent-mcp.jsonCloud agent paste JSON (mcpServers)Generated — same
copilot/copilot-custom-agent-mcp.frontmatter.mdCustom agent YAML frontmatterGenerated — same
copilot/docs/copilot-mcp.mdInstall guide + surfaces tableGenerated — same
copilot/.github/copilot-instructions.mdCopilot coding-agent instructionsGeneratedgenerate-agent-host-files.js
copilot/SOURCE.mdProvenance + re-sync commandsPackaging note (this repo)

Validate empty-diff vs regeneration + 3-tool discipline:

node scripts/validate-copilot-kit.js

Empty-diff vs regeneration is LIVE when CODERIFTS_APP_ROOT has the generators, and RECORDED against fixtures/recorded/app-generator when it does not (weaker, named). A missing or corrupt snapshot still exits 1. The kit is a communication / distribution mirrornpx coderifts copilot-setup remains the install path.


MCP server

CodeRifts runs as a hosted Streamable HTTP MCP server. Any MCP-compatible agent (Claude Desktop, Cursor, LangGraph, AutoGen, custom) can connect and run governance checks before tool calls or merges.

  • Endpoint: https://app.coderifts.com/mcp
  • Transport: Streamable HTTP (protocol version 2025-06-18)
  • Server: CodeRifts API Governance v1.0.2
  • Auth: initialize and tools/list are open (no key); tools/call requires an API key - send Authorization: Bearer <key> or X-API-Key: <key>.

Connect

{
  "mcpServers": {
    "coderifts": {
      "url": "https://app.coderifts.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_CODERIFTS_API_KEY>"
      }
    }
  }
}

Verify the connection

curl -sS https://app.coderifts.com/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl","version":"1.0"}}}'

Expected: a JSON-RPC result with serverInfo and capabilities.tools.

Try without a key

Two public endpoints need no auth at all:

curl -s "https://app.coderifts.com/api/v1/public/preflight?url=https://petstore3.swagger.io/api/v3/openapi.json"

curl -s -X POST https://app.coderifts.com/api/v1/public/actionguard-check \
  -H "Content-Type: application/json" \
  -d '{"filename":".github/workflows/ci.yml","base_content":null,"head_content":"jobs:\n  b:\n    steps:\n      - uses: some-owner/some-action@main"}'

Both return HTTP 200 without a key. They do not share a response shape:

  • GET /api/v1/public/preflight is analyze-only. There is no decision field. The body carries analysis_outcome (Petstore URL: NO_BREAK_DETECTED), authorization_effect: NONE, and may_execute: false.
  • POST /api/v1/public/actionguard-check does return a decision field (unpinned uses: @main payload: WARN) plus execution_action: CONTINUE_WITH_MONITORING.

Tools

The hosted MCP server exposes exactly three tools (from live tools/list; pinned in this repository as tools.wire.v1.json, which npm run validate:tools-wire checks against the live server on every push, pull request and the daily cron):

ToolWhat it does
preflight_change_setPreflight a complete base→head change set of contract artifacts. Returns risk score and breaking-change analysis. With preflight_mode: "authorize" (and context.operation), returns a governance decision (ALLOW / WARN / REQUIRE_APPROVAL / BLOCK) and may mint a signed chain-receipt. With preflight_mode: "analyze", returns informational risk only (may_execute: false, no decision, no receipt). Requires artifacts + preflight_mode.
verify_receiptVerify a signed chain-receipt you already hold: signature authenticity, body binding, and (when lifecycle indices are available) whether it is currently authorized for a stated operation/target. Requires token. Does not re-diff specs.
get_decision_detailsRetrieve a past decision by decision_id (preferred) or fingerprint: stored report, breaking changes, scores, and linked receipt metadata if present. Not for a new analysis of the current change set.

On the authorize path of preflight_change_set, the decision envelope includes fields such as decision, execution_action, risk_score, safe_for_agent, and related analysis fields so agent runtimes can branch on a stable contract. Prefer branching on execution_action when present.


How agents use it

  1. Before merging an API change (or before an agent acts on a contract change), call preflight_change_set with full before/after artifacts and preflight_mode: "authorize" (plus context.operation).
  2. Read execution_action / decision: CONTINUE/ALLOW proceeds, WARN flags, REQUIRE_APPROVAL pauses for a human, STOP/BLOCK stops the merge / aborts the agent step.
  3. If you already hold a receipt and only need to confirm it is still valid, call verify_receipt — do not re-preflight unless the change set or operation changed.
  4. To inspect a prior decision by id, call get_decision_details.

Decision logic is deterministic: a single breaking change is never silently allowed. Tests can pass and still ship a broken contract — CodeRifts checks the contract itself at PR time.


Also available

  • GitHub App (zero-config, one-click install) on the GitHub Marketplace - posts a four-gate governance report (API contract, schema-vs-code, auth surface, workflow actions) on every pull request.
  • SDKs: @coderifts/sdk (TypeScript / npm), coderifts-sdk (Python / PyPI).
  • CLI: coderifts (npm) with a pre-push hook.
  • Integrations: Backstage plugin, VS Code extension, LangGraph / AutoGen / CrewAI.

Links

License

See LICENSE.

Reviews

No reviews yet

Be the first to review this server!