Elucora Evidence API

What Elucora Evidence API MCP server does

Elucora Evidence API MCP server gives an MCP client a way to create and inspect portable evidence receipts. A capture records the original bytes fetched from a public HTTP(S) URL and can identify a precise quote or JSON Pointer within that content. An attestation records a SHA-256 hash supplied by the caller when the content has no usable URL.

The resulting receipt records evidence hashes, issuer information, signature status, and available time or Bitcoin anchoring information. It demonstrates that the recorded content matched the captured or supplied hash and that the receipt was issued without later alteration. It does not establish that the source itself was accurate or truthful.

How it works

The hosted endpoint uses stateless Streamable HTTP and is available at https://elucora.com/mcp. Clients send MCP requests to the endpoint, optionally adding an Authorization: Bearer ... header. elucora_verify and elucora_get_receipt can be used without credentials. elucora_capture contacts the requested public source, while elucora_attest seals a caller-held hash; both require an API key and consume account quota.

Receipts use ES256 signatures over RFC 8785 canonical JSON. Entries are included in a public hash-linked log with signed checkpoints. When configured, timestamp authority data and OpenTimestamps Bitcoin anchoring provide additional time evidence. Each receipt includes a JWKS location so an ES256 implementation can verify it independently, and a public verifier is available at /verify/{id}.

Setup and configuration

No local installation is required. Configure an MCP client with the hosted URL and, for operations that capture or attest, an API key created through the Elucora dashboard:

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

The API key is supplied as an HTTP header rather than a documented environment variable. The free tier allows 500 receipts per month without a payment card. Hosts should require human approval before capture because it makes an external request and uses monthly quota.

Tools and capabilities

• elucora_verify checks whether a receipt is authentic and unchanged, and identifies the source bytes covered.
• elucora_get_receipt returns receipt details including the source, sealed passage, signature state, and Bitcoin anchor state.
• elucora_capture fetches a public HTTP(S) resource, preserves its returned bytes, optionally selects an exact quote or JSON Pointer, and creates a signed receipt.
• elucora_attest seals a SHA-256 hash already held by the caller for content without a URL. It supports existence and later-integrity claims, but not provenance.

Limitations and notes

Elucora Evidence API MCP server performs HTTP retrieval, not browser rendering. JavaScript-heavy pages are captured as the HTML shell returned by the server, so server-delivered filings, feeds, APIs, and article pages are better fits than single-page applications or social posts.

At capture time, the receipt proves what Elucora received. After that point, the signature and recorded hashes can be checked without relying on Elucora. The service is currently described as having one operator and a young public log. The documentation also states that receipts are not automatically court-admissible; that depends on the applicable court and rules.

An attestation proves that matching content existed at the recorded time and has not changed since, but it does not prove where the content came from. A valid receipt likewise establishes integrity, issuer, and time-related evidence, not the truth of the underlying source.