Developer · Remote MCP server
Evidence Log
Tamper-evident evidence log: signed heads, proofs, and recording salted digests of your records.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
eu.riskrouter/evidence-log- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-10-01
- Updated
- 2026-10-01
- Publisher
- eu.riskrouter
- Namespace
- Namespace verified by the MCP Registry via the domain riskrouter.eu · how
- Website
- riskrouter.eu/ai
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.riskrouter.eu/mcp | Authorization (secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- riskrouter 1.0.0 · protocol 2025-06-18
- Tools discovered
- 7:
get_evidence_head,get_inclusion_proof,get_consistency_proof,get_checkpoint,get_ledger_attestation,get_usage,record_evidence - Checked on
- 2026-10-05
How to connect Evidence Log
Evidence Log is a remote MCP server: there is nothing to install. Its endpoint is https://api.riskrouter.eu/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Evercraft WebRead public web content with Evercraft; search and browser automation stay behind safety gates. | Remote · HTTPLive check: ✓ handshake |
| Evernode MCPEvernode/HotPocket dApp helper: templates, non-determinism lint, lease math, live host lookup. | Local · stdio |
| Evidence Diff MCPExplain coarse Git and test-build evidence changes without source diff contents. Tools include... | Local · stdio |
| Evidence LedgerRead-only MCP: free OpenAI security evidence ledger (55 fields) + SaaSDossier release register. | Remote · HTTPLive check: ✓ handshake |
| EvidriftCatch TypeScript API and OpenAPI contract drift in AI-generated code, then revalidate it in CI. | Local · stdio |
| EVMoleLocal structured analysis of deployed EVM runtime bytecode. | Local · stdio |
| EvolutionDB Long-Term MemoryPersistent long-term memory for Claude Desktop / Claude Code, backed by EvolutionDB. | Local · stdio |
| EvolveguardWraps the evolveguard CLI as a single generic MCP tool for agent-skill file safety checks. | Local · stdio |