APEX PSI vs Elucora Evidence API
A side-by-side look at the APEX PSI and Elucora Evidence API MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose APEX PSI for cryptography work as a local process; choose Elucora Evidence API for cryptography over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose APEX PSI when
- You need dedicated capabilities in the Cryptography domain.
- You prefer a local stdio subprocess transport.
- You want tools like
seal, verify, anchor.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cryptography | Cryptography |
| Quality signal | 60/100 · Good | 48/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 5 | 4 |
| Full listing | View APEX PSI | View Elucora Evidence API |
Tools & capabilities
APEX PSI tools 5
sealStamp a cryptographic receipt on content. Writes to the APEX PSI append-only ledger with SHA-256 hash, Ed25519 signature, and post-quantum LMS-W4-SHA256 signature. Proves existence and integrity at a point in time — not the truth of the contents.verifyConfirm a seal's integrity against the APEX PSI append-only ledger. Accepts a receipt object (from the seal tool) or a raw SHA-256 hash. Reports whether the hash is present and anchored — integrity, not the truth of the original content.anchorRead the Bitcoin (OpenTimestamps) anchoring state of the ledger's pending Merkle roots, or — only when action:'anchor' is passed explicitly — request that pending roots be aggregated and submitted to the OTS calendars. Defaults to 'status' (read-only) so a routine call never triggers a batch write. An anchor becomes confirmed only when a real Bitcoin block is found.citeGenerate a citation for a sealed receipt in APA, BibTeX, or MLA format, citing the APEX PSI ledger entry.verify_chainIndependently verify a chain of receipts against the APEX PSI ledger. Recomputes each hash's presence and integrity and reports Merkle chain continuity. Returns a verification report — a recomputation result, not an opinion or a certification.
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.
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.
APEX PSI
{
"mcpServers": {
"apex-psi": {
"command": "npx",
"args": [
"-y",
"apex-psi-mcp"
]
}
}
}
Elucora Evidence API
{
"mcpServers": {
"elucora-evidence-api-2": {
"url": "https://elucora.com/mcp"
}
}
}
Frequently asked questions
APEX PSI is categorized under Cryptography and uses a local stdio subprocess. Elucora Evidence API belongs to Cryptography and uses a remote HTTP/SSE transport. Pick APEX PSI for cryptography work and Elucora Evidence API 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.
APEX PSI has no declared pricing — check the project's own site. Elucora Evidence API 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 apex-psi and elucora-evidence-api-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, APEX PSI has a quality signal of 60/100 (Good) with 1 views, 0 installs and 1 GitHub stars. Elucora Evidence API has 48/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.