Orphograph vs Verify
A side-by-side look at the Orphograph 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 Orphograph for cryptography work as a local process; 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 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.
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 | 56/100 · Good | 45/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | 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 | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 6 | Not listed |
| Full listing | View Orphograph | View Verify |
Tools & capabilities
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.
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.
Orphograph
{
"mcpServers": {
"orphograph": {
"command": "uvx",
"args": [
"orphograph-mcp"
]
}
}
}
Verify
{
"mcpServers": {
"verify-4": {
"command": "npx",
"args": [
"-y",
"@forestrie/mcp-verify"
]
}
}
}
Frequently asked questions
Orphograph is categorized under Cryptography and uses a local stdio subprocess. Verify belongs to Cryptography and uses a local stdio subprocess. Pick Orphograph 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.
Orphograph 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 orphograph and verify-4 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Orphograph has a quality signal of 56/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Verify has 45/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.