# api-governance MCP server

> Enforces signed, offline-verifiable authorization for contract changes before they are merged, deployed, or registered.

- Repository: https://github.com/coderifts/api-governance
- Page: https://hostedmcp.org/servers/coderifts/api-governance
- Transport: remote
- Stars: 0
- License: MIT
- Latest version: 1.0.3

## Install

### Claude Code

```sh
claude mcp add --transport http api-governance https://app.coderifts.com/mcp
```

### Cursor (`~/.cursor/mcp.json`)

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

### VS Code (`.vscode/mcp.json`)

```json
{
  "servers": {
    "api-governance": {
      "type": "http",
      "url": "https://app.coderifts.com/mcp"
    }
  }
}
```

### Codex (`~/.codex/config.toml`)

```toml
[mcp_servers.api-governance]
url = "https://app.coderifts.com/mcp"
```

### Gemini CLI (`~/.gemini/settings.json`)

```json
{
  "mcpServers": {
    "api-governance": {
      "httpUrl": "https://app.coderifts.com/mcp"
    }
  }
}
```

## Tools (3)

- `preflight_change_set`
- `verify_receipt`
- `get_decision_details`

## FAQ

### How does the authorization process work?

One grant binds the authorization, its single use, and the target state the change moves to, providing a signed decision that can be verified offline.

### What tools are exposed by the MCP server?

The server exposes three specific tools: preflight_change_set, verify_receipt, and get_decision_details.

### Do I need an API key to use the server?

An API key is required to authorize tool calls, but initialization and listing tools do not require one.