Elucora Evidence API
REMOTE · ELUCORA.COM
Capture a web source, or seal a hash you hold, into a signed receipt anyone can verify offline.
Available components
Last scanned (16 minutes ago)
Scores higher than 6% of remote servers
Reachable. Last reached 24 Oct 2026.
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 410. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 20 Sept 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- HTTPS: unverified → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list. functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 18 Aug 26 0
- Server version: 1.3.0 → 1.4.0 functional
- 17 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 67% → 80% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- New tool “elucora_attest” functional
- 16 Aug 26 0
- Transport: unverified → pass ▲ security
- Authorization: fail → partial ▲ security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Tool coverage: 67 functional
- First check of Schema quality: fail functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Oct 2026 · Probed https://elucora.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=elucora.com | CN=WE1,O=Google Trust Services,C=US | 12 Oct 2026 | 10 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 9d4207f03ac1ecea0ea128477766d075 |
| SANs: elucora.com, *.elucora.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of elucora.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| elucora.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 410 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://elucora.com/mcp | HTTP error | 410 | |
| http (plaintext) | http://elucora.com/mcp | HTTPS enforced | 308 | https://elucora.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
elucora_attest Seal a hash you already hold ~182
Prove a piece of content existed at a point in time by sealing its SHA-256 hash. Use when you already hold the bytes — a model output, a tool result, a document. Elucora records that you submitted this hash and when; it does not prove where the content came from or that it is true, because Elucora never saw the source. To prove what a web source served, use elucora_capture instead. Consumes receipt quota.
| Name | Type | Req | Description |
|---|---|---|---|
| content_type | string|null | – | Optional media type of the content, as described by the caller. |
| hash | string | yes | SHA-256 digest of the content, written as sha256:<64 hex characters>. |
| metadata | object|null | – | Optional signed scalar metadata. |
| size_bytes | integer|null | – | Optional size of the content, as described by the caller. |
No output schema declared.
No examples provided.
elucora_capture Capture verifiable source evidence ~127
Freeze proof of what a web source actually served, before quoting or acting on it. Returns a signed receipt that anyone can verify offline without trusting Elucora. Proves what was served and when, not that the content is true. Sends a network request to the supplied source and consumes receipt quota.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | – | Stable retry key for this capture. |
| metadata | object|null | – | Optional signed scalar metadata. |
| selector | object|null | – | Optional text-quote or JSON Pointer selector. |
| url | string | yes | Public HTTP(S) source URL. |
No output schema declared.
No examples provided.
elucora_get_receipt Retrieve an Elucora receipt ~58
Fetch an evidence receipt by ID: the source it covers, the exact passage or field that was sealed, the current signature result, and its transparency log and Bitcoin anchor state. Needs no credentials.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
elucora_verify Verify an Elucora receipt ~52
Check whether an evidence receipt is genuine and unaltered, and what source bytes it covers. Use this before relying on a receipt produced by someone else. Needs no credentials.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Elucora Evidence API MCP server?
Elucora Evidence API is a hosted endpoint at https://elucora.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · elucora.com
claude mcp add --transport http com-elucora-evidence 'https://elucora.com/mcp'
What is the Elucora Evidence API MCP server?
Elucora Evidence API is an MCP server listed in the public MCP registry as com.elucora/evidence. Capture a web source, or seal a hash you hold, into a signed receipt anyone can verify offline. This page covers its hosted endpoint (https://elucora.com/mcp).
Is the Elucora Evidence API MCP server safe to use?
Elucora Evidence API scores 23 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Elucora Evidence API MCP server expose?
Elucora Evidence API exposes 4 tools: elucora_capture, elucora_attest, elucora_get_receipt, elucora_verify. Their descriptions and schemas cost roughly 419 tokens of context every time the server is loaded.
Does the Elucora Evidence API MCP server require authentication?
Its publisher declares no required credentials for Elucora Evidence API. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Elucora Evidence API MCP server still maintained?
Elucora Evidence API is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.