Elucora Evidence API vs Verify
A side-by-side look at the Elucora Evidence API and Verify 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 Verify 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 Verify when
- You need dedicated capabilities in the Cryptography domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cryptography | Cryptography |
| Quality signal | 48/100 · Fair | 45/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 4 | Not listed |
| Full listing | View Elucora Evidence API | View Verify |
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.
Verify tools
No tool names declared yet. Check the project README from the listing page.
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"
}
}
}
Verify
{
"mcpServers": {
"verify-4": {
"command": "npx",
"args": [
"-y",
"@forestrie/mcp-verify"
]
}
}
}
Frequently asked questions
Elucora Evidence API is categorized under Cryptography and uses a remote HTTP/SSE transport. Verify belongs to Cryptography and uses a local stdio subprocess. Pick Elucora Evidence API for cryptography work and Verify 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. Verify is listed as free. Auth: no auth required. 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 verify-4 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. Verify has 45/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.