Skip to content
MCP server

evidence-log

By riskrouterAll Riskrouter servers

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

First seen 2 Oct 2026. One server, whatever directories list it: each directory listing keeps its own page and history.

1
Directories
Collected by InvokeRank
8
Tools
From an anonymous probe
-
ToolBench grade
Not graded by Arcade
-
GitHub stars
No repository data

Tools

ToolDescriptionBehaviour
get_chainThe 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.Not declared
get_checkpointThe log's signed checkpoint in the C2SP format witnesses cosign (origin, size, root).Not declared
get_consistency_proofProof that the tree at size first is a prefix of the tree at size second (or now): the log never rewrote history.Not declared
get_evidence_headThe current signed head of the evidence log: tree size, Merkle root and signature. Save it: any later head must be consistent with it.Not declared
get_inclusion_proofProof that the entry at leaf_index is in the tree, optionally at a given tree_size. Checkable offline with the public verifier.Not declared
get_ledger_attestationThe signed head hash of the hash-chained audit ledger of recorded quotes.Not declared
get_usageHow much is recorded, and by how many keys that are not ours. Counts only, nothing about anyone.Not declared
record_evidenceRecord 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.Not declared

Directory listings

DirectoryListingTierFirst seen
Official MCP Registryeu.riskrouter/evidence-log-2 Oct 2026
evidence-log MCP server | InvokeRank