RiskRouter MCP MCP server

An official tamper-evident evidence log MCP server provided by RiskRouter for AI agents. It allows agents to record SHA-256 digests of their decisions and actions into a signed, immutable ledger. This enables AI systems to provide verifiable proofs of their operations for compliance, auditing, and defense against future inquiries, supporting requirements like the EU AI Act.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by RiskRouter

MCP endpoint (Streamable HTTP)

https://api.riskrouter.eu/mcp

Vendor documentation

What you can do with it

Record AI agent decisions and tool calls in a tamper-evident log
Verify inclusion of specific records in the evidence log
Check consistency of the log between different time points
Generate signed proofs for regulatory compliance

Tools advertised by the last live check:

get_evidence_head
get_inclusion_proof
get_consistency_proof
get_checkpoint
get_ledger_attestation
get_usage
record_evidence

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http riskrouter-mcp https://api.riskrouter.eu/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add riskrouter-mcp --url https://api.riskrouter.eu/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable riskrouter-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "riskrouter-mcp": {
      "url": "https://api.riskrouter.eu/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "riskrouter-mcp": {
      "type": "streamableHttp",
      "url": "https://api.riskrouter.eu/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start riskrouter-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "riskrouter-mcp": {
      "type": "http",
      "url": "https://api.riskrouter.eu/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http riskrouter-mcp https://api.riskrouter.eu/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "riskrouter-mcp": {
      "url": "https://api.riskrouter.eu/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "riskrouter-mcp": {
      "serverUrl": "https://api.riskrouter.eu/mcp"
    }
  }
}

See all 782

Do you run RiskRouter MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing