# eu.riskrouter/evidence-log (remote · api.riskrouter.eu)

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

- Trust score: 84/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

## Components

- remote · `api.riskrouter.eu`: 84/100 (this document), [markdown](https://verifymcp.io/servers/eu-riskrouter-evidence-log/api.md), [page](https://verifymcp.io/servers/eu-riskrouter-evidence-log/api)

## Channel facts

- Endpoint: `https://api.riskrouter.eu/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-25.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 585 tokens (~73/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the eu.riskrouter/evidence-log MCP server?

eu.riskrouter/evidence-log is a hosted endpoint at https://api.riskrouter.eu/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

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

### VS Code

```json
{
  "servers": {
    "eu-riskrouter-evidence-log": {
      "type": "http",
      "url": "https://api.riskrouter.eu/mcp"
    }
  }
}
```

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "eu-riskrouter-evidence-log": {
      "type": "remote",
      "url": "https://api.riskrouter.eu/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add eu-riskrouter-evidence-log --url 'https://api.riskrouter.eu/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  eu-riskrouter-evidence-log:
    url: "https://api.riskrouter.eu/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "eu-riskrouter-evidence-log": {
      "Transport": "http",
      "Url": "https://api.riskrouter.eu/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add eu-riskrouter-evidence-log -t streamable-http -u 'https://api.riskrouter.eu/mcp'
```

### Other

```json
{
  "mcpServers": {
    "eu-riskrouter-evidence-log": {
      "type": "http",
      "url": "https://api.riskrouter.eu/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-24 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-19 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-17 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-15 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-13 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-12 (score 78, +7)

- [security improvement] Authorization: unverified → partial

### 2026-10-10 (score 71, +1)

- [functional regression] Schema quality: 62 → 73

## MCP tools (8)

### `get_evidence_head` (~40 tokens)

Signed head of the evidence log

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` (~69 tokens)

Inclusion proof for one entry

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

Input parameters:

- `leaf_index` (integer, required): Position of the entry in the log.
- `tree_size` (integer): Optional: the tree size to prove against.

### `get_consistency_proof` (~66 tokens)

Consistency proof between two heads

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

Input parameters:

- `first` (integer, required): A tree size you hold a head for.
- `second` (integer): Optional: a later tree size.

### `get_checkpoint` (~29 tokens)

C2SP checkpoint

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

### `get_ledger_attestation` (~26 tokens)

Audit ledger attestation

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

### `get_usage` (~30 tokens)

Usage in numbers

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

### `record_evidence` (~152 tokens)

Record the digest of a decision

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.

Input parameters:

- `chain_seq` (integer): Optional, with chain_tag: this record's position in its chain, from 1.
- `chain_tag` (string): Optional: the completeness chain this record belongs to (64 hex characters derived from a secret you keep).
- `kind` (string, required): A short tag such as ai.decision.
- `record_digest` (string, required): SHA-256 of your salted record, lowercase hex. Never the record itself.

### `get_chain` (~95 tokens)

What the log holds in one completeness 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.

Input parameters:

- `chain_tag` (string, required): The chain's 64-hex tag.
- `from` (integer): Optional: the first position to list.
- `to` (integer): Optional: the last position to list.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/eu-riskrouter-evidence-log/api#diagnostics

## Score history

- 2026-10-25: 84
- 2026-10-24: 84
- 2026-10-23: 83
- 2026-10-22: 83
- 2026-10-21: 83
- 2026-10-20: 82
- 2026-10-19: 82
- 2026-10-18: 81
- 2026-10-17: 81
- 2026-10-16: 80
- 2026-10-15: 80
- 2026-10-14: 79
- 2026-10-13: 79
- 2026-10-12: 78
- 2026-10-10: 71
- 2026-10-07: 70
- 2026-10-05: 64
- 2026-10-04: 63
- 2026-10-03: 63
- 2026-10-02: 62
- 2026-10-01: 62

## Common questions

### What is the eu.riskrouter/evidence-log MCP server?

eu.riskrouter/evidence-log is an MCP server listed in the public MCP registry as eu.riskrouter/evidence-log. Tamper-evident evidence log: signed heads, proofs, and recording salted digests of your records. This page covers its hosted endpoint (https://api.riskrouter.eu/mcp).

### Is the eu.riskrouter/evidence-log MCP server safe to use?

eu.riskrouter/evidence-log scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the eu.riskrouter/evidence-log MCP server expose?

eu.riskrouter/evidence-log exposes 8 tools: get_evidence_head, get_inclusion_proof, get_consistency_proof, get_checkpoint, get_ledger_attestation, and 3 more. Their descriptions and schemas cost roughly 507 tokens of context every time the server is loaded.

### Does the eu.riskrouter/evidence-log MCP server require authentication?

No. We connected to eu.riskrouter/evidence-log without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the eu.riskrouter/evidence-log MCP server still maintained?

eu.riskrouter/evidence-log is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.riskrouter.eu/mcp
- Website: https://riskrouter.eu/ai
- Changelog RSS feed: https://verifymcp.io/servers/eu-riskrouter-evidence-log/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/eu-riskrouter-evidence-log/api.json
- HTML version of this page: https://verifymcp.io/servers/eu-riskrouter-evidence-log/api