Evidence Log
eu.riskrouterv1.0.0Updated Oct 1, 2026
Tamper-evident evidence log: signed heads, proofs, and recording salted digests of your records.
Overview
AI-generated overview
A remote MCP endpoint for a tamper-evident evidence log that records salted digests of records and returns signed heads and proofs.
- What it does
- This server exposes a tamper-evident evidence log over a remote HTTP endpoint. According to its description, it records salted digests of your records and provides signed heads and proofs, which can be used to show that a record existed in a given state at a point in time. The manifest does not list individual tools, so the exact operations are not documented here.
- When to use it
- Consider it when an assistant needs to timestamp or attest to records in a way that can later be verified, for example keeping an auditable trail of documents or events. It is less useful if you only need ordinary logging or storage without integrity proofs.
- Requirements
- A remote MCP client that supports streamable HTTP, connecting to the provider's endpoint. Recording requires an Authorization header carrying a bearer RiskRouter key; reading is described as not requiring a key. No local runtime or package is needed.
Before you install
The Authorization header carries a secret bearer key, so treat it as a credential and avoid exposing it in logs or shared configuration. The service receives salted digests of your records, so consider what metadata that reveals. The description does not state whether recorded entries can be deleted or changed, so assume writes may be permanent.
Installation
In SourceWeft
- Open Evidence Log in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"evidence-log": {
"type": "http",
"url": "https://api.riskrouter.eu/mcp"
}
}
}Tools
0Tool metadata has not been indexed yet.
Version history
1- v1.0.0LatestOct 1, 2026
