API Governance vs MCP Server
A side-by-side look at the API Governance and MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose API Governance for agreements & coordination work as a local process; choose MCP Server for agreements & coordination over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
Choose MCP Server when
- You need dedicated capabilities in the Agreements & Coordination domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
DA_API_URL, PORT, DA_AUTH_TOKEN. - You want tools like
register_agent, get_agent_profile, create_decision.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Agreements & Coordination | Agreements & Coordination |
| Quality signal | 55/100 · Good | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | CODERIFTS_API_KEY | DA_API_URLPORTDA_AUTH_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 3 | 30 |
| Full listing | View API Governance | View MCP Server |
Tools & capabilities
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.
MCP Server tools 30
register_agentRegister in this environment. Your decisions will accumulate into a trajectory that others can observe.get_agent_profileView an agent's decision profile: their trajectory shape, EE patterns, and activity summary as observed through ARA. Observing another agent is paid via x402 (Trial does not cover ARA observation); observing your own agent_id is free.create_decisionUse when an action crosses an external boundary: payment, delegation, or agreement with another agent. This anchors the responsibility scope. You say when: before you execute, or after a decision you have already made. Record a tamper-evident decision. This route records self-declared decisions; a declaration that involves a counterparty is made with propose_bilateral instead. Each decision is added to your record trajectory, which you and a counterparty can check against DA's external entry. Omitting the EE axes applies the defaults (medium/basic/internal/standard), equivalent to the EE_standard preset. The cost is a base fee plus additions for the selected EE axis values and options, all taken from the current pricing settings; the amount charged is returned in the response as dac_amount, itemized in cost_breakdown.confirm_decisionUse after create_decision to settle the anchored boundary as an external record. Once confirmed, the agreed scope is fixed outside both parties' own logs. Confirm a pending decision: marks the anchored declaration as settled. The integrity hash and timestamp are created at declaration time (create_decision); confirm requires only the dd_id. Call this after the action described in the DD has been executed.propose_bilateralUse when two agents need to fix a shared boundary: both sides must agree before the boundary is anchored. This applies to payment splits, task delegation, and other joint commitments between agents. Propose a bilateral agreement to another agent: creates a DD with declaration_mode 'bilateral' and waits for counterparty acceptance.get_decisionRetrieve a specific decision record by its ID: what was declared, when, and at what scope, plus its place in the lineage. Returns the decision's formal shape (enums, timestamps, hash), never its content.list_decisionsList your decision records: the trajectory built so far.observe_environmentObserve aggregate environment statistics: active agents, total decisions recorded, activity density. Requires auth_token. The cost comes from the current ARA observation pricing and is paid via x402; Trial does not cover ARA observation. The amount charged is returned in the response as dac_charged.observe_patternObserve pattern-level EE distributions and action-type breakdowns across agents. Requires auth_token. The cost comes from the current ARA observation pricing and is paid via x402; Trial does not cover ARA observation. The amount charged is returned in the response as dac_charged.list_toolsBrowse the agent-to-agent tool marketplace. Discover tools that other agents have built and published.register_toolPublish a tool you built to the marketplace. Set a price in DAC and earn revenue when other agents purchase it.purchase_toolPurchase a tool from the marketplace. The tool creator earns DAC from your purchase. Paid via x402; Trial does not cover this route.- +18 more on the listing page
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.
API Governance
{
"mcpServers": {
"api-governance-2": {
"command": "npx",
"args": [
"-y",
"coderifts"
],
"env": {
"CODERIFTS_API_KEY": "YOUR_CODERIFTS_API_KEY_HERE"
}
}
}
}
MCP Server
{
"mcpServers": {
"decision-anchor-mcp-server": {
"url": "https://mcp.decision-anchor.com/mcp"
}
}
}
Frequently asked questions
API Governance is categorized under Agreements & Coordination and uses a local stdio subprocess. MCP Server belongs to Agreements & Coordination and uses a remote HTTP/SSE transport. Pick API Governance for agreements & coordination work and MCP Server 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.
API Governance has no declared pricing — check the project's own site. MCP Server 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 api-governance-2 and decision-anchor-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, API Governance has a quality signal of 55/100 (Good) with 1 views, 0 installs and 0 GitHub stars. MCP Server has 59/100 (Good) with 2 views, 0 installs and 0 GitHub stars.