eu.riskrouter/evidence-log
REMOTE · API.RISKROUTER.EU · SCANNED OCT 12
Tamper-evident evidence log: signed heads, proofs, and recording salted digests of your records.
Available components
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 585 tokens (~73/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · api.riskrouter.eu
claude mcp add --transport http eu-riskrouter-evidence-log 'https://api.riskrouter.eu/mcp'
{
"mcpServers": {
"eu-riskrouter-evidence-log": {
"url": "https://api.riskrouter.eu/mcp"
}
}
} {
"servers": {
"eu-riskrouter-evidence-log": {
"type": "http",
"url": "https://api.riskrouter.eu/mcp"
}
}
} [mcp_servers.eu-riskrouter-evidence-log] url = "https://api.riskrouter.eu/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"eu-riskrouter-evidence-log": {
"type": "remote",
"url": "https://api.riskrouter.eu/mcp",
"enabled": true
}
}
} openclaw mcp add eu-riskrouter-evidence-log --url 'https://api.riskrouter.eu/mcp' --transport streamable-http
mcp_servers:
eu-riskrouter-evidence-log:
url: "https://api.riskrouter.eu/mcp" {
"McpServers": {
"eu-riskrouter-evidence-log": {
"Transport": "http",
"Url": "https://api.riskrouter.eu/mcp"
}
}
} assistant mcp add eu-riskrouter-evidence-log -t streamable-http -u 'https://api.riskrouter.eu/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 37. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
- Schema quality: 62 → 73 ▼ functional
- 7 Oct 26 +6
- HTTPS: unverified → pass ▲ security
- 5 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 1 Oct 26 62
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 12 Oct 2026 · Probed https://api.riskrouter.eu/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=riskrouter.eu | CN=WE1,O=Google Trust Services,C=US | 19 Sept 2026 | 18 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 55636a4be9b63743136c251fd59ef2f7 |
| SANs: riskrouter.eu, api.riskrouter.eu, *.api.riskrouter.eu | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.riskrouter.eu. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| eu. | present | 35926 | 8 | Verified |
| riskrouter.eu. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'none'; frame-ancestors 'none'; base-uri 'none'; form-action 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.riskrouter.eu/mcp | Verified | 200 | |
| http (plaintext) | http://api.riskrouter.eu/mcp | HTTPS enforced | 301 | https://api.riskrouter.eu/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_chain What the log holds in one completeness chain ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chain_tag | string | yes | The chain's 64-hex tag. |
| from | integer | – | Optional: the first position to list. |
| to | integer | – | Optional: the last position to list. |
No output schema declared.
No examples provided.
get_checkpoint C2SP checkpoint ~29
The log's signed checkpoint in the C2SP format witnesses cosign (origin, size, root).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_consistency_proof Consistency proof between two heads ~66
Proof that the tree at size first is a prefix of the tree at size second (or now): the log never rewrote history.
| Name | Type | Req | Description |
|---|---|---|---|
| first | integer | yes | A tree size you hold a head for. |
| second | integer | – | Optional: a later tree size. |
No output schema declared.
No examples provided.
get_evidence_head Signed head of the evidence log ~40
The current signed head of the evidence log: tree size, Merkle root and signature. Save it: any later head must be consistent with it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_inclusion_proof Inclusion proof for one entry ~69
Proof that the entry at leaf_index is in the tree, optionally at a given tree_size. Checkable offline with the public verifier.
| Name | Type | Req | Description |
|---|---|---|---|
| leaf_index | integer | yes | Position of the entry in the log. |
| tree_size | integer | – | Optional: the tree size to prove against. |
No output schema declared.
No examples provided.
get_ledger_attestation Audit ledger attestation ~26
The signed head hash of the hash-chained audit ledger of recorded quotes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_usage Usage in numbers ~30
How much is recorded, and by how many keys that are not ours. Counts only, nothing about anyone.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
record_evidence Record the digest of a decision ~152
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | A short tag such as ai.decision. |
| record_digest | string | yes | SHA-256 of your salted record, lowercase hex. Never the record itself. |
No output schema declared.
No examples provided.
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 72 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 12 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.