Ownership Attestation Protocol vs API Governance
A side-by-side look at the Ownership Attestation Protocol and API Governance MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Ownership Attestation Protocol for agreements & coordination work over a hosted endpoint; choose API Governance for agreements & coordination as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Ownership Attestation Protocol when
- You need dedicated capabilities in the Agreements & Coordination domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
DATABASE_URL, MCP_ACCESS_TOKEN.
Choose API Governance when
- You need dedicated capabilities in the Agreements & Coordination domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
CODERIFTS_API_KEY. - You want tools like
preflight_change_set, verify_receipt, get_decision_details.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Agreements & Coordination | Agreements & Coordination |
| Quality signal | 39/100 · Fair | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | DATABASE_URLMCP_ACCESS_TOKEN | CODERIFTS_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View Ownership Attestation Protocol | View API Governance |
Tools & capabilities
Ownership Attestation Protocol tools
No tool names declared yet. Check the project README from the listing page.
API Governance tools 3
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 `prefligh…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.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Ownership Attestation Protocol
{
"mcpServers": {
"ownership-attestation-protocol": {
"url": "http://localhost:5000/mcp"
}
}
}
API Governance
{
"mcpServers": {
"api-governance-2": {
"command": "npx",
"args": [
"-y",
"coderifts"
],
"env": {
"CODERIFTS_API_KEY": "YOUR_CODERIFTS_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Ownership Attestation Protocol is categorized under Agreements & Coordination and uses a remote HTTP/SSE transport. API Governance belongs to Agreements & Coordination and uses a local stdio subprocess. Pick Ownership Attestation Protocol for agreements & coordination work and API Governance for agreements & coordination.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Ownership Attestation Protocol has no declared pricing — check the project's own site. API Governance has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add ownership-attestation-protocol and api-governance-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Ownership Attestation Protocol has a quality signal of 39/100 (Fair) with 2 views, 0 installs and 1 GitHub stars. API Governance has 55/100 (Good) with 1 views, 0 installs and 0 GitHub stars.