mcpbeat Sign in

Elucora Evidence API MCP Server

answering

Elucora Evidence API is answering right now. Last checked 13 min ago. It exposes 4 tools.

Capture a web source, or seal a hash you hold, into a signed receipt anyone can verify offline.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 18 days of history
18 days agonow
100.0%
Uptime 24h
91 of 91 checks
4
Tools
read from the server
210 ms
Response time
average over 24h
open, no key
Access
streamable-http

What the code does

We have not read this server's code yet · tools taken from the live server

Evidence

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

Claims local-only, but ships network tools elucora_capture
заявлено «локально, без передачи данных», но есть elucora_capture

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

We found things in this code

Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch Elucora Evidence API and you get told the day something new turns up.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

run in your terminal
claude mcp add evidence --transport http https://elucora.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "evidence": {
      "url": "https://elucora.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.evidence]
url = "https://elucora.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "evidence": {
      "url": "https://elucora.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "evidence": {
      "url": "https://elucora.com/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

elucora
elucora_attest
Prove a piece of content existed at a point in time by sealing its SHA-256 hash. Use when you already hold the bytes — a model output, a tool result, a document. Elucora records that you submitted this hash and when; it does not prove where the content came from or that it is true, because Elucora never saw the source. To prove what a web source served, use elucora_capture instead. Consumes receipt quota.
elucora_capture
Freeze proof of what a web source actually served, before quoting or acting on it. Returns a signed receipt that anyone can verify offline without trusting Elucora. Proves what was served and when, not that the content is true. Sends a network request to the supplied source and consumes receipt quota.
elucora_get_receipt
Fetch an evidence receipt by ID: the source it covers, the exact passage or field that was sealed, the current signature result, and its transparency log and Bitcoin anchor state. Needs no credentials.
elucora_verify
Check whether an evidence receipt is genuine and unaltered, and what source bytes it covers. Use this before relying on a receipt produced by someone else. Needs no credentials.

Endpoints

URLTransportStateLatencyChecked
https://elucora.com/mcp streamable-http answering 240 ms 13 min ago

Alternatives to Elucora Evidence API

same job, measured the same way
Seal
by aqta

Verify Seal AI decision receipts: signed evidence anyone can check, no account needed.

10 tools answering
Pcrzero
by pcrzero

Issue signed receipts for AI agent actions; verify any receipt offline - free, no account.

102 installs/wk 3 tools answering
Veritasacta Verify
by tomjwxf

Offline receipt verifier. Ed25519 signature verification without contacting any server.

89 installs/wk local only
Acta — Verifiable Agent Memory
by kylewilson04

Verifiable agent memory with signed ledger receipts — verify every write offline.

local only
Blue Cap Evidence Verify
by soundiq

Verify structured evidence and return machine-verifiable provenance, assurance, and receipts.

3 tools answering
Fact Checker API
by br0ski777

Verify claims with web evidence. Returns sources and verdict. x402 micropayment.

1 tools answering
Otterkit
by useotterkit

Tunnels and webhooks for AI agents: capture, await, verify, replay, and send signed test events.

182 installs/wk local only
Quorum
by godzilla-lab

Market evidence with receipts: every claim resolves to a real stored record you can fetch back.

4 tools answering

Elucora Evidence API — questions

Answers built from our own checks of this server.

What can Elucora Evidence API do?
It exposes 4 tools, read directly from the server on our last check. Among them: elucora_attest, elucora_capture, elucora_get_receipt, elucora_verify. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Elucora Evidence API working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 210 ms. The bar chart above shows every period we have measured.
Is Elucora Evidence API still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Elucora Evidence API?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Elucora Evidence API need an API key?
No. Elucora Evidence API completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Elucora Evidence API?
It answers our handshake in 210 ms on average, which is faster than 71% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.