Evidence MCP server
{
"mcpServers": {
"elucora": {
"type": "http",
"url": "https://elucora.com/mcp"
}
}
}{
"mcpServers": {
"elucora": {
"type": "http",
"url": "https://elucora.com/mcp"
}
}
}{
"mcpServers": {
"elucora": {
"type": "http",
"url": "https://elucora.com/mcp"
}
}
}{
"servers": {
"elucora": {
"type": "http",
"url": "https://elucora.com/mcp"
}
}
}{
"mcpServers": {
"elucora": {
"type": "http",
"url": "https://elucora.com/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.4.0
What it does
Elucora Evidence captures web pages, PDFs, or JSON fields and returns cryptographically signed receipts that prove integrity and timestamp. Anyone can verify a receipt offline without trusting Elucora, making it useful for agents that need to seal evidence of what a source said at a specific moment.
- Capture a news article or filing and create a verifiable record that proves exactly what was published at that time.
- Seal a hash of content you hold locally to prove it existed and hasn't changed, without revealing the content itself.
- Pass a signed receipt to another person or system so they can verify the source bytes offline without accessing Elucora's API or dashboard.
Tools this server exposes
| Tool | Does |
|---|---|
| elucora_capture | Fetches a public HTTP(S) source, preserves the original bytes, optionally pins an exact quote or JSON Pointer path, and returns a signed receipt; requires API k |
| elucora_attest | Seals a SHA-256 hash you provide for content with no URL, proving the content existed at that moment and has not changed; requires API key and consumes quota. |
| elucora_verify | Checks whether a receipt is genuine and unaltered, and returns what source bytes it covers; requires no API key. |
| elucora_get_receipt | Reads a receipt to return its source, sealed passage, signature status, and Bitcoin anchor state; requires no API key. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.