Elucora Evidence API

com.elucoraPublished by elucora.comOfficial publisherv1.4.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingSecurity & Monitoring

Overview

AI-generated overview

Hosted MCP server that captures a public web source or seals a SHA-256 hash into a signed, offline-verifiable evidence receipt.

What you can do
Capture a public HTTP(S) source, preserve its original bytes, optionally pin a quote or JSON Pointer, and get a signed receipt (consumes quota). Seal a SHA-256 hash you already hold for content without a URL (consumes quota). Verify whether a receipt is genuine and unaltered and what bytes it covers, with no key. Read a receipt's source, sealed passage, signature status and Bitcoin anchor state, with no key.
When to use it
Useful when an assistant needs to prove that a specific page, PDF or JSON field existed at a point in time and hand a receipt to someone who can check it without trusting the vendor's dashboard. Good for filings, feeds, APIs and article pages; not for JavaScript-rendered pages or social posts.
Requirements
A remote MCP endpoint; nothing to install. Verifying and reading receipts need no credentials. Capturing and attesting need an Elucora API key sent as a Bearer token in the Authorization header. The free tier allows 500 receipts a month without a card. Network access to the source being captured.
Before you install
Capture makes an outbound request to an external URL and consumes the account's monthly quota, so a human approval step is advised. The API key is a secret sent in the Authorization header. Elucora is trusted at the moment of capture; the receipt proves integrity, issuer and time, not that the source was truthful, and it is not offered as court-admissible.

Installation

In SourceWeft

  1. Open Elucora Evidence API in the dashboard and add it to a workspace.
  2. 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.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.elucora%2Fevidence/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "elucora-evidence-api": {
      "type": "http",
      "url": "https://elucora.com/mcp"
    }
  }
}

README

Elucora Evidence MCP Server

Capture a public web source and return a portable, cryptographically signed evidence receipt.

Elucora is a hosted MCP server. There is nothing to install: point your client at https://elucora.com/mcp. Two of the four tools need no API key at all, so a client can verify and read receipts before anyone signs up for anything.

An agent can seal the exact page, PDF, or JSON field behind a claim, hand the receipt to someone else, and have them verify it without trusting Elucora's dashboard or its API.

Tools

ToolKey requiredWhat it does
elucora_verifyNoChecks whether a receipt is genuine and unaltered, and what source bytes it covers.
elucora_get_receiptNoReads a receipt: source, sealed passage, signature status, Bitcoin anchor state.
elucora_captureYesFetches a public HTTP(S) source, preserves the original bytes, optionally pins an exact quote or JSON Pointer, and returns a signed receipt. Consumes quota and contacts the source.
elucora_attestYesSeals a SHA-256 hash the caller already holds, for content with no URL. Proves the content existed then and has not changed since — not where it came from. Consumes quota.

The free tier is 500 receipts a month with no card.

Connecting

elucora_verify and elucora_get_receipt work with no credentials. For the two tools that contact a source or spend quota, create an API key at elucora.com/dashboard/keys, then:

json
{  "mcpServers": {    "elucora": {      "url": "https://elucora.com/mcp",      "headers": { "Authorization": "Bearer elu_live_..." }    }  }}

The server implements stateless Streamable HTTP, protocol version 2025-11-25.

Hosts should keep a human approval step before elucora_capture: it makes a request to an external URL and consumes the account's monthly quota.

What a receipt proves

  • The captured bytes and the selected evidence match their recorded SHA-256 hashes
  • Elucora issued the receipt and it has not been altered since, by ES256 signature over RFC 8785 canonical JSON
  • The entry is in a public hash-linked log, published as signed checkpoints outside Elucora
  • When a timestamp authority is configured, an RFC 3161 token binds the entry to an independently signed time, and entry digests are submitted to OpenTimestamps for Bitcoin anchoring

A valid receipt proves integrity, issuer, and time. It does not prove that the source was telling the truth.

Limits, stated before you find them

  • Captures are HTTP, not a browser. A page that renders its content with JavaScript is captured as the shell the server sent. Filings, feeds, APIs and article pages are exactly right; single page applications and social posts are not.
  • Elucora is trusted at the moment of capture. The receipt proves what Elucora was served. Everything after that instant is verifiable without trusting Elucora at all.
  • No affidavit. Nothing here is offered as court-admissible; that is a matter for a court and its rules, not for a vendor.
  • One operator, and a young log. Both are publicly countable at elucora.com/transparency.

Verifying without Elucora

Every receipt carries jwks_url, and verification keys are published at /.well-known/jwks.json. Any ES256 implementation can check a receipt offline. The public verifier for a receipt lives at /verify/{id}.

Links

Source: README.md at commit 24e5993

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.4.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts