Elucora Evidence API

Registre officiel Sécurité

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

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (streamable-http)
Claude Code
claude mcp add --transport http elucora-evidence-api 'https://elucora.com/mcp' --header 'Authorization: <Optional. Required only for elucora_capture and elucora_attest, which consume quota. Verifying and reading receipts need no credentials. Bearer token using an Elucora API key created at https://elucora.com/dashboard/keys, for example "Bearer elu_live_...".>'
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "elucora-evidence-api": {
            "type": "http",
            "url": "https://elucora.com/mcp",
            "headers": {
                "Authorization": "<Optional. Required only for elucora_capture and elucora_attest, which consume quota. Verifying and reading receipts need no credentials. Bearer token using an Elucora API key created at https://elucora.com/dashboard/keys, for example \"Bearer elu_live_...\".>"
            }
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. Elucora Evidence MCP Server
  2. Tools
  3. Connecting
  4. What a receipt proves
  5. Limits, stated before you find them
  6. Verifying without Elucora
  7. Links

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:

{
  "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}.

Questions fréquentes

Qu'est-ce que Elucora Evidence API ?

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

Comment installer Elucora Evidence API ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http elucora-evidence-api 'https://elucora.com/mcp' --header 'Authorization: <Optional. Required only for elucora_capture and elucora_attest, which consume quota. Verifying and reading receipts need no credentials. Bearer token using an Elucora API key created at https://elucora.com/dashboard/keys, for example "Bearer elu_live_...".>'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour Elucora Evidence API ?

Oui. Il attend Authorization, à renseigner dans sa configuration.

Elucora Evidence API est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient Elucora Evidence API ?

Il est publié par Fuyuki0. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.