Evidence Log MCP Server

by riskrouter Your server? Claim it

answering

Evidence Log is answering right now. Last checked 2 min ago. It exposes 8 tools.

Tamper-evident evidence log: signed heads, proofs, and recording salted digests of your records.

Uptime history 15 days of history · worst day 99%

15 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

94 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 7 October 2026. No other catalogue keeps this.

7 Oct a tool appeared get_chain

7 Oct a tool changed the parameters it asks for record_evidence

Nothing serious here today

Today is the operative word: we check Evidence Log every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

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

~/.codex/config.toml

[mcp_servers.evidence-log]
url = "https://api.riskrouter.eu/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 8

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

chain

get_chain

The log's signed statement of one completeness chain as of the current head: its length and, for each position, the leaf, the time and the digest. A position nobody showed you is a record left out.

checkpoint

get_checkpoint

The log's signed checkpoint in the C2SP format witnesses cosign (origin, size, root).

consistency

get_consistency_proof

Proof that the tree at size first is a prefix of the tree at size second (or now): the log never rewrote history.

evidence

get_evidence_head

The current signed head of the evidence log: tree size, Merkle root and signature. Save it: any later head must be consistent with it.

inclusion

get_inclusion_proof

Proof that the entry at leaf_index is in the tree, optionally at a given tree_size. Checkable offline with the public verifier.

ledger

get_ledger_attestation

The signed head hash of the hash-chained audit ledger of recorded quotes.

record

record_evidence

Record the SHA-256 of a decision record you keep yourself, so it can later be shown to be unchanged. Send the digest and a short kind, never the record. Needs your RiskRouter key in the Authorization header of the MCP connection. Entries are permanent.

usage

get_usage

How much is recorded, and by how many keys that are not ours. Counts only, nothing about anyone.

Endpoints

URL	Transport	State	Latency	Checked
https://api.riskrouter.eu/mcp	streamable-http	answering	163 ms	2 min ago

Alternatives to Evidence Log

same job, measured the same way

Agent Incident Reporter MCP

by csoai-org

Signed, hash-chained, tamper-evident AI incident records. EU AI Act Article 73 serious-incident repo

156 installs/wk local only

Vouchwell

by vouchwell

Read, verify and export a tamper-evident log of what an AI agent did. Read-only.

521 installs/wk local only

AccordTrace

by kosta1985

Tamper-evident proof creation and verification for AI agents via MCP, A2A, and REST.

9 tools answering

FluxProof

by equinoxaifinance-rgb

Evidence-bearing public webpage monitoring with hashes, diffs, signed webhooks, REST, and MCP.

6 tools answering

Signal Bureau

by evolutionlabs-dev

SigB (Signal Bureau): maintained, source-traced record of entities and events in your named domain.

29 tools answering

Slate

by slate-hq

Your own SLATE health data in your AI assistant: read, trend, plan and log. Never suggests a dose.

answering

Touchstone

by touchstone

Bitcoin-anchored, tamper-evident audit log for AI agents — record, disclose and verify actions.

38 installs/wk answering

Auditreach

by rudrendupaul

BYOK Reddit/YouTube research CLI with a tamper-evident audit log and an MCP server.

194 installs/wk local only

Evidence Log — questions

Answers built from our own checks of this server.

What can Evidence Log do?

It exposes 8 tools, read directly from the server on our last check. Among them: get_chain, get_checkpoint, get_consistency_proof, get_evidence_head, get_inclusion_proof, get_ledger_attestation and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Evidence Log working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 94 ms. The bar chart above shows every period we have measured.

How do I connect Evidence Log?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Evidence Log need an API key?

No. Evidence Log completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Evidence Log?

It answers our handshake in 94 ms on average, which is faster than 86% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.