Kevros

Kevros MCP Server enables you to issue and verify trust certificates, check peer reputation, verify release tokens, and generate tamper-evident audit trails with post-quantum cryptographic signatures. It provides a standardized MCP interface so your agents can interact within a verifiable trust network.

How to use

You use the Kevros MCP Server by running the MCP adapter for Kevros and then interacting with it through your MCP client. The server exposes a set of tools that let you verify actions, attest provenance, bind intents to commands, verify outcomes, bundle trust certificates, check peer trust, verify tokens, and observe health status. This enables your agents to act with verifiable identity, cryptographic authorization, and auditable, hash-chained evidence.

How to install

Prerequisites: ensure you have Python installed and access to the Python package manager.

pip install kevros

# Add to Claude Code as an MCP plugin (one command):
pip install kevros && claude mcp add kevros -- kevros-mcp

Additional sections

MCP usage and configuration. The Kevros MCP Server can be invoked via a standard CLI entry point and is designed to integrate with common MCP ecosystems. If you are configuring an MCP runtime, you can reference the provided example configuration below to start the Kevros MCP server.

{
  "mcpServers": {
    "kevros": {
      "command": "kevros-mcp",
      "args": []
    }
  }
}

Notes and practical tips

• The MCP entry shown uses a local, stdio-based server driven by the kevros-mcp command. This means you run the server locally and connect your MCP client to it through the standard MCP interface.

• The server exposes tools for action verification, provenance attestation, intent binding, outcome verification, trust bundling, peer verification, token verification, and health checks. These tools enable end-to-end trust with post-quantum signatures where supported.

Available tools

verify

Pre-flight action check that returns ALLOW, CLAMP, or DENY along with a release token proving the action was evaluated and authorized.

attest

Create a hash-chained provenance record with a PQC block reference to establish tamper-evident evidence of actions.

bind

Cryptographic binding of an intent to a command so accountability can be traced from intent to action.

verify_outcome

Check whether an action achieved the declared intent and return the outcome status and metrics.

bundle

Generate an auditor-grade trust certificate that is PQC-signed and portable for verification by auditors or regulators.

verify_peer

Look up another agent’s trust score and reputation within the network.

verify_peer_token

Independently verify another agent’s release token to ensure authenticity and authorization.

health

Check gateway health and chain integrity to ensure the trust framework is functioning properly.