FractalAI Post Quantum Proofs vs Orphograph
A side-by-side look at the FractalAI Post Quantum Proofs and Orphograph MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose FractalAI Post Quantum Proofs for cryptography work as a local process; choose Orphograph 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 FractalAI Post Quantum Proofs when
- You need dedicated capabilities in the Cryptography domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
FRACTALAI_BASE_URL.
Choose Orphograph when
- You need dedicated capabilities in the Cryptography domain.
- You prefer a local stdio subprocess transport.
- You want tools like
orphograph_anchor_file, orphograph_anchor_folder, orphograph_anchor_output.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cryptography | Cryptography |
| Quality signal | 44/100 · Fair | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Freemium | Not declared |
| Required env vars | FRACTALAI_BASE_URL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 6 |
| Full listing | View FractalAI Post Quantum Proofs | View Orphograph |
Tools & capabilities
FractalAI Post Quantum Proofs tools
No tool names declared yet. Check the project README from the listing page.
Orphograph tools 6
orphograph_anchor_fileAnchor a local file to the Bitcoin chain via Orphograph. Reads the file locally, computes SHA-256 and SHA-512 in-process, and transmits ONLY those fingerprints. The file body never leaves the device. Returns a receipt id, a receipt URL, and calendar attestation counts.orphograph_anchor_folderAnchor a whole folder (a dataset) to the Bitcoin chain via Orphograph. Every file is hashed locally into an RFC-6962 Merkle tree; ONLY the manifest (relative paths + SHA-256 digests + the root) is transmitted — no file body leaves the device. Returns a receipt id and a hosted certificate URL; each file stays independently verifiable via an inclusion proof.orphograph_anchor_outputAnchor a string of generated OUTPUT (an AI agent's result, a model response, a transcript, any text) to the Bitcoin chain — without writing a file first. Hashes the UTF-8 text in-process and transmits ONLY the SHA-256/512 fingerprints; the text never leaves the device. Use this to prove an exact output existed at a specific time. Returns a receipt id, a receipt URL, and calendar attestation counts.orphograph_verify_receiptLook up an existing Orphograph receipt and return what the office recorded for it: the anchored hashes, the calendar attestation counts, and (when available) the time the pin to Bitcoin was OBSERVED. This reads the office's record — it does NOT independently verify the Bitcoin chain, and the observed pin time is not the block's own timestamp. For an independent chain check, run the OpenTimestamps client (`ots verify`) against the receipt's .ots files. Does not require an API key.orphograph_verify_lineageWalk the parent links of a receipt's edit lineage and verify each link. Reports anchor-time ordering only — it does not assess content similarity, authorship, or whether siblings exist.orphograph_list_vaultList the signed-in subscriber's anchored receipts. Requires ORPHO_API_KEY in the environment. The key is issued from https://orphograph.com/account.html.
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.
FractalAI Post Quantum Proofs
{
"mcpServers": {
"fractalai-post-quantum-proofs": {
"command": "npx",
"args": [
"-y",
"fractalai-mcp-server"
],
"env": {
"FRACTALAI_BASE_URL": "YOUR_FRACTALAI_BASE_URL_HERE"
}
}
}
}
Orphograph
{
"mcpServers": {
"orphograph": {
"command": "uvx",
"args": [
"orphograph-mcp"
]
}
}
}
Frequently asked questions
FractalAI Post Quantum Proofs is categorized under Cryptography and uses a local stdio subprocess. Orphograph belongs to Cryptography and uses a local stdio subprocess. Pick FractalAI Post Quantum Proofs for cryptography work and Orphograph 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.
FractalAI Post Quantum Proofs is listed as freemium — a free tier with paid plans. Auth: no auth required. Orphograph 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 fractalai-post-quantum-proofs and orphograph as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, FractalAI Post Quantum Proofs has a quality signal of 44/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Orphograph has 56/100 (Good) with 1 views, 0 installs and 0 GitHub stars.