Skip to content

eu.riskrouter/evidence-log

by riskrouter.eu · remote · no sign-in to list tools · v1.0.1 · published by eu.riskrouter

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

Changes · 1
CompareRegistry entry

8 tools: 1 change things and 7 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

8 tools

Changes things 1Claude Code: ask
  • record_evidenceRecord the SHA-256 of a decision record you keep yourself, so it can later be shown to be unchanged.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Record the digest of a decision
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Only reads 7Claude Code: allow
  • 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.No findings

    Why it is in this group

    • The name "get_chain" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: What the log holds in one completeness chain
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_checkpointThe log's signed checkpoint in the C2SP format witnesses cosign (origin, size, root).No findings

    Why it is in this group

    • The name "get_checkpoint" says "get": a word for reading.
    Description, as the server wrote it
    The log's signed checkpoint in the C2SP format witnesses cosign (origin, size, root).

    Annotations the server declares

    • title: C2SP checkpoint
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • 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.No findings

    Why it is in this group

    • The name "get_consistency_proof" says "get": a word for reading.
    Description, as the server wrote it
    Proof that the tree at size first is a prefix of the tree at size second (or now): the log never rewrote history.

    Annotations the server declares

    • title: Consistency proof between two heads
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_evidence_headThe current signed head of the evidence log: tree size, Merkle root and signature.No findings

    Why it is in this group

    • The name "get_evidence_head" says "get": a word for reading.
    Description, as the server wrote it
    The current signed head of the evidence log: tree size, Merkle root and signature. Save it: any later head must be consistent with it.

    Annotations the server declares

    • title: Signed head of the evidence log
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_inclusion_proofProof that the entry at leaf_index is in the tree, optionally at a given tree_size.No findings

    Why it is in this group

    • The name "get_inclusion_proof" says "get": a word for reading.
    Description, as the server wrote it
    Proof that the entry at leaf_index is in the tree, optionally at a given tree_size. Checkable offline with the public verifier.

    Annotations the server declares

    • title: Inclusion proof for one entry
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_ledger_attestationThe signed head hash of the hash-chained audit ledger of recorded quotes.No findings

    Why it is in this group

    • The name "get_ledger_attestation" says "get": a word for reading.
    Description, as the server wrote it
    The signed head hash of the hash-chained audit ledger of recorded quotes.

    Annotations the server declares

    • title: Audit ledger attestation
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_usageHow much is recorded, and by how many keys that are not ours.No findings

    Why it is in this group

    • The name "get_usage" says "get": a word for reading.
    Description, as the server wrote it
    How much is recorded, and by how many keys that are not ours. Counts only, nothing about anyone.

    Annotations the server declares

    • title: Usage in numbers
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__evidence-log__get_evidence_head",
      "mcp__evidence-log__get_inclusion_proof",
      "mcp__evidence-log__get_consistency_proof",
      "mcp__evidence-log__get_checkpoint",
      "mcp__evidence-log__get_ledger_attestation",
      "mcp__evidence-log__get_usage",
      "mcp__evidence-log__get_chain"
    ],
    "ask": [
      "mcp__evidence-log__record_evidence"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as evidence-log. Review it before you use it.