Categories › Security › Code & dependency scanning
Tamper-evident evidence log: signed heads, proofs, and recording salted digests of your records.
Remote server: your requests and data go to api.riskrouter.eu. Claude Code: claude mcp add --transport http evidence-log https://api.riskrouter.eu/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
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.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.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.get_checkpoint — The log's signed checkpoint in the C2SP format witnesses cosign (origin, size, root).get_ledger_attestation — The signed head hash of the hash-chained audit ledger of recorded quotes.get_usage — How much is recorded, and by how many keys that are not ours. Counts only, nothing about anyone.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, neverget_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 dNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.