Elucora Evidence API vs Provenonce
A side-by-side look at the Elucora Evidence API and Provenonce MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Elucora Evidence API for cryptography work over a hosted endpoint; choose Provenonce for cryptography as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Elucora Evidence API when
- You need dedicated capabilities in the Cryptography domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
elucora_verify, elucora_get_receipt, elucora_capture.
Choose Provenonce when
- You need dedicated capabilities in the Cryptography domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PROVENONCE_API_KEY, PROVENONCE_AGENT_HASH, PROVENONCE_SKILL_REF, PROVENONCE_REGISTRY_URL. - You want tools like
provenonce_register, provenonce_status, provenonce_purchase_sigil.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cryptography | Cryptography |
| Quality signal | 48/100 · Fair | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | PROVENONCE_API_KEYPROVENONCE_AGENT_HASHPROVENONCE_SKILL_REFPROVENONCE_REGISTRY_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 4 | 11 |
| Full listing | View Elucora Evidence API | View Provenonce |
Tools & capabilities
Elucora Evidence API tools 4
elucora_verifyChecks whether a receipt is genuine and unaltered, and what source bytes it covers.elucora_get_receiptReads a receipt: source, sealed passage, signature status, Bitcoin anchor state.elucora_captureFetches 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_attestSeals 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.
Provenonce tools 11
provenonce_registerRegister this agent with Provenonce to get a cryptographic identity (hash + API key). Safe to call multiple times — returns existing identity if already registered. No wallet required. Free.provenonce_statusGet this agent's current Provenonce status: identity, SIGIL, beats balance, and next steps. Requires prior provenonce_register call.provenonce_purchase_sigilPurchase a Provenonce SIGIL to unlock full provenance: heartbeat access, signed passport, and a permanent identity record. If payment_tx is omitted, returns payment instructions (fee amount + address). SIGIL format: name*principal*tier (e.g. my-agent*acme*ind).provenonce_heartbeatSubmit a heartbeat to prove this agent is alive. Root agents (depth 0) require a SIGIL first; child agents (depth > 0) can heartbeat without a SIGIL. If payment_tx is omitted, returns payment instructions (fee amount + address).provenonce_get_passportGet this agent's cryptographically signed Passport — a verifiable identity document any third party can verify offline using the Provenonce authority public key. Root agents (depth 0) require an active SIGIL; child agents (depth > 0) only need at least one heartbeat.provenonce_beats_proofCompute a Beats work-proof — cryptographic evidence of computational effort by this agent. Computes sequential hash chains at the current network difficulty, submits to the Beats service for a signed receipt. The receipt can be used for spawn authorization and other operations.provenonce_submit_beatsCompute VDF beats and submit to the Registry to credit this agent's lifetime beat count. Unlike provenonce_beats_proof (which gets a receipt for spawn/resync), this extends the agent's persistent beat chain and increases the "Lifetime Beats" metric visible in the Registry.provenonce_verify_agentVerify another agent's Provenonce identity. Returns their SIGIL, identity class, and registration status. Public — no authentication required.provenonce_spawnSpawn a child agent under this agent's identity. The child inherits lineage from the parent. Returns the child's hash and API key. Requires sufficient beats balance or a work-proof receipt.provenonce_get_lineageGet the full lineage chain for an agent — all events in its provenance history (registration, SIGIL issuance, heartbeats, spawns). Public — no authentication required.provenonce_batch_heartbeatSubmit heartbeats for multiple child agents in a single call. One payment covers all children. Requires active sponsorships for each child. Max 20 children per batch.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Elucora Evidence API
{
"mcpServers": {
"elucora-evidence-api-2": {
"url": "https://elucora.com/mcp"
}
}
}
Provenonce
{
"mcpServers": {
"provenonce": {
"command": "npx",
"args": [
"-y",
"@provenonce/mcp"
],
"env": {
"PROVENONCE_API_KEY": "YOUR_PROVENONCE_API_KEY_HERE",
"PROVENONCE_AGENT_HASH": "YOUR_PROVENONCE_AGENT_HASH_HERE",
"PROVENONCE_SKILL_REF": "YOUR_PROVENONCE_SKILL_REF_HERE",
"PROVENONCE_REGISTRY_URL": "YOUR_PROVENONCE_REGISTRY_URL_HERE"
}
}
}
}
Frequently asked questions
Elucora Evidence API is categorized under Cryptography and uses a remote HTTP/SSE transport. Provenonce belongs to Cryptography and uses a local stdio subprocess. Pick Elucora Evidence API for cryptography work and Provenonce for cryptography.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Elucora Evidence API has no declared pricing — check the project's own site. Provenonce has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add elucora-evidence-api-2 and provenonce as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Elucora Evidence API has a quality signal of 48/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. Provenonce has 55/100 (Good) with 2 views, 0 installs and 0 GitHub stars.