CodeRifts

MCPAI代理

提供方 coderifts

AI代理 未标注 API Key 社区 / 第三方 ClaudeCursorCodexZed

PR-native API governance for AI agents. Detects breaking API changes at merge time, scores blast radius, and blocks unsafe agent tool calls before production. Preflight check, risk scoring, Decision Spec v1.0.

一句话选型结论

按资料字段整理

CodeRifts 属于AI代理类 MCP 服务器,传输方式未标注,API Key,可直接接入 Claude、Cursor、Codex 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类AI代理 传输方式未标注 鉴权API Key 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

AI代理
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

preflight mcp openapi

支持客户端

适用场景

preflightmcpopenapi

安装与配置

未标注 API Key
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
给代理接外部能力

让代理在任务中途调用搜索、数据库等真实工具。

多步任务编排

把一串操作拆成步骤,由代理按顺序执行。

自动化重复流程

把固定流程交给代理跑,减少手工操作。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Claude、Cursor、Codex,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好API Key对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在AI代理场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
CodeRifts当前 未标注 未标注 未标注 无 未标注
Filesystem 560c4363 13 未标注 本地部署 无 2026-05-17
Server Everything (everything) 11 stdio · 本地进程 本地部署 有 2026-05-17
Time 7365cb6d 2 SSE · 服务端推送 远程部署 有 2026-05-18
Everything Claude Code 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Openmemory 557e1585 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

AI代理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方coderifts上游标注的维护方 coderifts
分类AI代理本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式API Key远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Cross-platform本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

18.4 KB
来自项目仓库与上游目录的原文,未做删改

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

Install```text

Claude Code

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

Any MCP client (Streamable HTTP) — add to its MCP config

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

SDKs

npm install @coderifts/sdk
pip install coderifts-sdk


GitHub Copilot reads the same server under three different root keys — `servers` in
`.vscode/mcp.json`, `mcpServers` in the cloud agent&#x27;s MCP settings, and `mcp-servers` in a custom
agent&#x27;s frontmatter — and `npx coderifts copilot-setup` writes all three (details below).

A key is needed only to authorize; get one at `https://app.coderifts.com/api/signup`.

---

## Claude Code plugin

Install the CodeRifts marketplace, then the `api-governance` plugin (MCP server + skill).
Requires `CODERIFTS_API_KEY` for tool calls.```text
/plugin marketplace add coderifts/api-governance
/plugin install api-governance@coderifts

Local checkout (after clone):```text
/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.

Path · Role · Source of truth
`plugins/api-governance-cursor/.cursor-plugin/plugin.json` · Cursor Plugin manifest · cursor/plugins `plugin.schema.json`
`plugins/api-governance-cursor/skills/coderifts/SKILL.md` · Skill (`name: coderifts`) · **Generated** — coderifts-app `scripts/generate-skill-carriers.js`; the website `.well-known/agent-skills/coderifts/SKILL.md` is vendored from it
`plugins/api-governance-cursor/rules/coderifts.mdc` · Cursor rule · **Generated** — `generate-agent-host-files.js`
`plugins/api-governance-cursor/mcp.json` · Streamable HTTP MCP wiring · Same endpoint as Claude `.mcp.json` (not the website tool-card)
`plugins/api-governance-cursor/hooks/hooks.json` · preToolUse adapter, `failClosed: true` · CLI `coderifts cursor-hook` on `Write\ · Delete` — same shape as the app&#x27;s generated `.cursor/hooks.json`
`.cursor-plugin/marketplace.json` · Cursor marketplace entry · Cursor `marketplace.schema.json`

Validate:```bash
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.


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.

Path Role Source of truth
plugins/api-governance-openai/.codex-plugin/plugin.json Codex plugin manifest Codex plugin-json-spec (scaffold skill)
plugins/api-governance-openai/.mcp.json Streamable HTTP MCP wiring Same endpoint as Claude .mcp.json
plugins/api-governance-openai/skills/api-governance/SKILL.md Skill + tool list Trigger wording from agent-setup rule; tool names/descriptions from generated mcp.json
plugins/api-governance-openai/AGENTS.md Agent rules file Generated — coderifts agent-setup / generate-agent-host-files.js
plugins/api-governance-openai/openai-agent-instructions.md OpenAI Agents SDK instructions Generated — same generator
plugins/api-governance-openai/docs/openai-production-pattern.md Production pattern (ID108) — host dispatch loop with executeOpenAIToolCall Hand-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.mjs Offline smoke (ALLOW + BLOCK; no OpenAI key) Real dispatcher + stub client
.agents/plugins/marketplace.json Codex marketplace entry Codex 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````bash

Offline smoke (needs ~/coderifts-agent-guard built, or CODERIFTS_AGENT_GUARD_ROOT)

npm run smoke:openai-dispatch


⚠ **Still failing on the same one assertion, re-measured 2026-09-24**: `ALLOW factory ran — execute() did not run`. The other eight assertions pass (4 ALLOW, 5 BLOCK), and the BLOCK side — the side that matters for a gate — is fully green: the factory does not run, the content is the gate denial with no fabricated success, and the decision identity is surfaced. The failing assertion is on the ALLOW path, where the dispatch wrapper returns the function result without having invoked the injected factory.

The 2026-09-14 version of this note ended &quot;Investigation is in progress.&quot; That was dropped rather than re-dated: ten days on, it is a claim about activity that nothing here can verify, and a README that reports its own diligence is reporting the one thing a reader cannot check. What a reader can check is the assertion name and today&#x27;s date.

Local checkout in Codex (team marketplace path):```text
# 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):```bash
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):**```bash
npx coderifts copilot-setup
# optional: --out &lt;dir&gt;   --check (drift-gate)   --force

Agent-host instructions (including .github/copilot-instructions.md) come from:```bash
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):

| Surface | Config location | Root key | Auth |
|---------|-----------------|----------|------|
| **VS Code / Copilot Chat** | `.vscode/mcp.json` | **`servers`** | `${input:coderifts_api_key}` + `inputs[]` |
| **Copilot cloud agent + code review** | Repo **Settings → Copilot → MCP servers** (paste JSON) | **`mcpServers`** | Agents secret `COPILOT_MCP_CODERIFTS_API_KEY` in `headers` |
| **Custom agent** (org/enterprise) | Agent profile `.md` YAML frontmatter | **`mcp-servers`** | `${{ secrets.COPILOT_MCP_CODERIFTS_API_KEY }}` |

Tools allowlisted everywhere: `preflight_change_set`, `verify_receipt`, `get_decision_details`.

### Vendored reference tree (`copilot/`)

| Path | Role | Source of truth |
|------|------|-----------------|
| `copilot/.vscode/mcp.json` | VS Code / Copilot Chat | **Generated** — `generate-copilot-mcp.js` |
| `copilot/copilot-cloud-agent-mcp.json` | Cloud agent paste JSON (`mcpServers`) | **Generated** — same |
| `copilot/copilot-custom-agent-mcp.frontmatter.md` | Custom agent YAML frontmatter | **Generated** — same |
| `copilot/docs/copilot-mcp.md` | Install guide + surfaces table | **Generated** — same |
| `copilot/.github/copilot-instructions.md` | Copilot coding-agent instructions | **Generated** — `generate-agent-host-files.js` |
| `copilot/SOURCE.md` | Provenance + re-sync commands | Packaging note (this repo) |

Validate empty-diff vs regeneration + 3-tool discipline:```bash
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
mirror
— npx coderifts copilot-setup remains the install path.


Agent Skill (skills.sh)```bash

npx skills add coderifts/api-governance


The skills CLI discovers `skills/api-governance/SKILL.md` at this repository&#x27;s root and installs it under
the name **`api-governance`**. Where it lands depends on the agent (the CLI&#x27;s own table): `.agents/skills/api-governance/`
for most agents (Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode, …) and `.claude/skills/api-governance/` for
Claude Code.

**One skill, one name (2026-09-29).** The three SKILL.md carriers — Claude
(`plugins/api-governance/skills/api-governance/`), Cursor (`plugins/api-governance-cursor/skills/coderifts/`) and
Codex/OpenAI (`plugins/api-governance-openai/skills/api-governance/`) — carry the same body byte for byte and the
same `name: coderifts`, the name skills.sh lists (`npx skills add coderifts/api-governance` installs
`./.agents/skills/coderifts/`, measured 2026-09-29). Only the frontmatter `description` is per host. All three are
generated by coderifts-app `scripts/generate-skill-carriers.js` from `agent/skills/coderifts/SKILL.md`;
`test/one-skill.test.js` holds them together. The website&#x27;s `.well-known/agent-skills/coderifts/SKILL.md` is the
Cursor carrier, vendored.

## 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.3` — read from `initialize` → `result.serverInfo.version` on 2026-09-24. A version typed into a README is a claim with a date on it; `npm run validate:tools-wire` compares the TOOLS to the live server on every push, pull request and daily cron, but nothing compares this line, so re-read it rather than trust it.
- **Auth:** `initialize`, `tools/list` and an **analyze** `tools/call` need no key (measured live 2026-09-26). An **authorize** call mints a signed receipt and needs an API key — send `Authorization: Bearer ` or `X-API-Key: `.

### Connect```json
{
  &quot;mcpServers&quot;: {
    &quot;coderifts&quot;: {
      &quot;url&quot;: &quot;https://app.coderifts.com/mcp&quot;,
      &quot;headers&quot;: {
        &quot;Authorization&quot;: &quot;Bearer &lt;YOUR_CODERIFTS_API_KEY&gt;&quot;
      }
    }
  }
}

Verify the connection```bash

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

An analyze call over MCP needs no key:```bash
curl -sS https://app.coderifts.com/mcp \
  -H &#x27;Content-Type: application/json&#x27; \
  -H &#x27;Accept: application/json, text/event-stream&#x27; \
  -d &#x27;{&quot;jsonrpc&quot;:&quot;2.0&quot;,&quot;id&quot;:1,&quot;method&quot;:&quot;tools/call&quot;,&quot;params&quot;:{&quot;name&quot;:&quot;preflight_change_set&quot;,&quot;arguments&quot;:{&quot;preflight_mode&quot;:&quot;analyze&quot;,&quot;artifacts&quot;:[{&quot;id&quot;:&quot;api&quot;,&quot;type&quot;:&quot;openapi&quot;,&quot;before&quot;:&quot;openapi: 3.0.0\ninfo: {title: Pets, version: 1.0.0}\npaths:\n  /pets:\n    get:\n      responses:\n        \&quot;200\&quot;:\n          description: ok\n          content:\n            application/json:\n              schema:\n                type: object\n                properties:\n                  id: {type: string}\n                  name: {type: string}\n&quot;,&quot;after&quot;:&quot;openapi: 3.0.0\ninfo: {title: Pets, version: 1.0.0}\npaths:\n  /pets:\n    get:\n      responses:\n        \&quot;200\&quot;:\n          description: ok\n          content:\n            application/json:\n              schema:\n                type: object\n                properties:\n                  id: {type: string}\n&quot;}]}}}&#x27;

Measured response (live, 2026-09-26 — removing name from GET /pets), in the tool result:```json
{ "preflight_mode": "analyze", "analysis_outcome": "BREAKS_DETECTED",
"authorization_effect": "NONE", "may_execute": false, "receipt_kind": "NONE",
"breaking_changes": 1, "risk_score": 14 }


That is information, not permission: `may_execute` is `false` on every analyze answer. To act,
call again with `preflight_mode: &quot;authorize&quot;` and `context.operation`, with a key.

Two public REST endpoints need no auth at all:```bash
curl -s &quot;https://app.coderifts.com/api/v1/public/preflight?url=https://petstore3.swagger.io/api/v3/openapi.json&quot;

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

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):

Tool What it does
preflight_change_set Preflight a complete base→head change set of contract artifacts. Returns risk score and breaking-change analysis. With preflight_mode: &quot;authorize&quot; (and context.operation), returns a governance decision (ALLOW / WARN / REQUIRE_APPROVAL / BLOCK) and may mint a signed chain-receipt. With preflight_mode: &quot;analyze&quot;, returns informational risk only (may_execute: false, no decision, no receipt). Requires artifacts + preflight_mode.
verify_receipt Verify 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_details Retrieve 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: &quot;authorize&quot; (plus context.operation).
  2. Branch on execution_action only: CONTINUE proceeds, CONTINUE_WITH_MONITORING proceeds with a wired monitoring sink, REQUEST_APPROVAL pauses for a human, STOP stops the merge / aborts the agent step. Any other value is not permission — fail closed.
  3. Before acting under the receipt you hold, call verify_receipt with the same context the preflight was made under, and act only when currently_authorized is true. 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 on the GitHub Marketplace — installs without configuration and posts a signed contract-change decision (ALLOW / WARN / REQUIRE_APPROVAL / BLOCK) on every pull request, across four gates: API contract, schema-vs-code, auth surface and workflow actions. ⚠ It reports by default: the check's phase-1 conclusion is clamped to neutral and MERGEGATE_ENFORCE defaults false, so it prevents a merge only once the check is required on the branch and that variable is on. The platform truth table is the source of truth for that distinction:
  • SDKs: npm install @coderifts/sdk (TypeScript), pip install coderifts-sdk (Python).
  • CLI: coderifts (npm) with a pre-push hook.
  • Integrations: Backstage plugin, VS Code extension, LangGraph / AutoGen / CrewAI.

Links

  • Website: https://coderifts.com
  • Decision Spec: https://coderifts.com/decision-spec/
  • API reference: https://app.coderifts.com/api/docs
  • Manifest: https://coderifts.com/mcp.json
  • Receipt verifier (verify our receipts without trusting us): https://github.com/coderifts/receipt-verifier
  • Contact: hello@coderifts.com

License

See LICENSE.

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
CodeRifts 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

CodeRifts 怎么在 Claude、Cursor、Codex 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

CodeRifts 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

CodeRifts 需要 API Key 吗?

资料标注需要API Key认证,使用前准备好对应凭据,并按最小权限配置。

CodeRifts 支持哪些客户端?

资料标注支持 Claude、Cursor、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

CodeRifts 能提供哪些能力?

资料显示能力标签包括 preflight、mcp、openapi。具体工具清单以官方文档为准。

CodeRifts 需要什么运行环境?

运行时为 Cross-platform。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。