Web Resource Ledger is answering right now. Last checked 9 min ago. Last commit 24 Oct 2026.
Capture web pages as cryptographically signed, tamper-evident evidence with WACZ archives.
We read the source, 1 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const result = eval(c);
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.
claude mcp add web-resource-ledger --transport http https://api.webresourceledger.com/mcp
https://api.webresourceledger.com/mcp
[mcp_servers.web-resource-ledger]
url = "https://api.webresourceledger.com/mcp"
{
"mcpServers": {
"web-resource-ledger": {
"url": "https://api.webresourceledger.com/mcp"
}
}
}
{
"servers": {
"web-resource-ledger": {
"type": "http",
"url": "https://api.webresourceledger.com/mcp"
}
}
}
This endpoint answered with an authorization challenge. The server is running, but you need an API key from its owner to call it.
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://api.webresourceledger.com/mcp | streamable-http | needs key | 292 ms | 9 min ago |
Pseudonymizes PII before your LLM and returns a cryptographically signed receipt per response.
Agent-native price and event oracle with cryptographic source attestation
Read-only, dated public crypto source registry with evidence status. Local stdio; no API keys.
Evidence-backed crypto due diligence with sources, freshness, and a runtime receipt on every call.
Tamper-evident audit logs for AI agents: submit, fetch, and verify cryptographic proof bundles.
Cryptographically sound randomness for agents, with verifiable commit-reveal.
Cryptographically verifiable blockchain data with Merkle proofs + ECDSA signing.
Crypto-paid uncensored LLM inference with signed execution receipts. No account.
Answers built from our own checks of this server.