Elucora Evidence API

REMOTE · ELUCORA.COM · SCANNED AUG 18

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

Available components

68 68 Trust /100

Trust breakdown (6 categories)

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 →

Endpoint Security69

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability74

AI-judged instruction clarity (good).Pass
Context-footprint check failed: tool/resource definitions use about 553 tokens (~138/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management7

Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage93

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
80% of tool parameters carry a description.Partial

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · elucora.com

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http com-elucora-evidence https://elucora.com/mcp

# ~/.codex/config.toml

[mcp_servers.com-elucora-evidence]
url = "https://elucora.com/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-elucora-evidence": {
      "type": "remote",
      "url": "https://elucora.com/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add com-elucora-evidence --url https://elucora.com/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  com-elucora-evidence:
    url: "https://elucora.com/mcp"

// mcp.json

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

18 Aug 26 +1
- Server version: 1.3.0 → 1.4.0 functional
17 Aug 26 +1
- 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 +35
- 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
15 Aug 26 +3
- HSTS header: fail → pass ▲ security
14 Aug 26 28

First indexed and scored.

Show 1 earlier entry Hide earlier entries

Diagnostics

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 18 Aug 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	14 Aug 2026	12 Nov 2026	ECDSA 256	ECDSA-SHA256	a82c5b01b6d8335c13312644b8ed91d8
SANs: 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

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 No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	200

Header	Value
strict-transport-security	max-age=31536000; includeSubDomains; preload
content-security-policy	default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob:; font-src 'self' data:; connect-src 'self'; frame-ancestors 'none'; base-uri 'self'; form-action 'self'; object-src 'none'; upgrade-insecure-requests
x-content-type-options	nosniff
referrer-policy	strict-origin-when-cross-origin
permissions-policy	camera=(), microphone=(), geolocation=(), payment=(), usb=()

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://elucora.com/mcp	Verified	200
http (plaintext)	http://elucora.com/mcp	Inconclusive	405

MCP tools · 4 exposed · ~419 tokens

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.

Tool Tokens

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

Name	Type	Req	Description
id	string	yes	–

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

14 Aug 18 Aug