Agent Receipts vs APEX PSI
A side-by-side look at the Agent Receipts and APEX PSI MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
A
Agent ReceiptsCryptographyIssue & verify signed (ed25519), hash-chained, timestamped provenance receipts for agent actions.37FairAuth: not declaredVerdict: choose Agent Receipts for cryptography work; choose APEX PSI for cryptography as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
AChoose Agent Receipts when
- You need dedicated capabilities in the Cryptography domain.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | A Agent Receipts | |
|---|---|---|
| Category | Cryptography | Cryptography |
| Quality signal | 37/100 · Fair | 60/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| 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 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 5 |
| Full listing | View Agent Receipts | View APEX PSI |
Tools & capabilities
Agent Receipts tools
No tool names declared yet. Check the project README from the listing page.
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.
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.
Agent Receipts
No confirmed install command for Agent Receipts yet — follow the setup steps linked from its listing page rather than a guessed package name.
APEX PSI
{
"mcpServers": {
"apex-psi": {
"command": "npx",
"args": [
"-y",
"apex-psi-mcp"
]
}
}
}
Frequently asked questions
Agent Receipts is categorized under Cryptography and uses an install path we have not confirmed yet. APEX PSI belongs to Cryptography and uses a local stdio subprocess. Pick Agent Receipts for cryptography work and APEX PSI 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. Agent Receipts has no confirmed install command yet — follow its own setup instructions.
Agent Receipts has no declared pricing — check the project's own site. APEX PSI 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 agent-receipts and apex-psi as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agent Receipts has a quality signal of 37/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. APEX PSI has 60/100 (Good) with 1 views, 0 installs and 1 GitHub stars.