# Capability Host Protocol MCP server

> Provides a governed evidence layer to declare, govern, and prove agentic actions through tamper-evident, signed execution records.

- Repository: https://github.com/capabilityhostprotocol/chp-core
- Page: https://hostedmcp.org/servers/capabilityhostprotocol/chp-core
- Transport: remote
- Stars: 1
- License: Apache-2.0
- Latest version: 0.8.0

## Install

### Claude Code

```sh
claude mcp add --transport http chp-core https://capabilityhostprotocol.com/api/mcp
```

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

```json
{
  "mcpServers": {
    "chp-core": {
      "url": "https://capabilityhostprotocol.com/api/mcp"
    }
  }
}
```

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

```json
{
  "servers": {
    "chp-core": {
      "type": "http",
      "url": "https://capabilityhostprotocol.com/api/mcp"
    }
  }
}
```

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

```toml
[mcp_servers.chp-core]
url = "https://capabilityhostprotocol.com/api/mcp"
```

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

```json
{
  "mcpServers": {
    "chp-core": {
      "httpUrl": "https://capabilityhostprotocol.com/api/mcp"
    }
  }
}
```

## FAQ

### What is the difference between CHP and MCP?

MCP exposes tools and context to AI applications, whereas CHP governs and evidences the execution of capabilities, adding correlation, replay, and governance.

### Where is the execution evidence stored?

Every tool call is stored locally in a SQLite database located at ~/.chp/evidence.sqlite.

### Is the protocol tamper-evident?

Yes, the chain is tamper-evident, allowing users to verify if the record is intact even if they did not run the agent.