Anchor a file's SHA-256 fingerprint to Bitcoin. The file never leaves the device.
MCPpedia last refreshed this data
io.github.Orphograph/orphograph is an MCP server that anchor a file's SHA-256 fingerprint to Bitcoin. The file never leaves the device. Its tool list has not been published yet over stdio and http, requires no API key, and scores 87/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"io-github-orphograph-orphograph": {
"args": [
"orphograph-mcp"
],
"command": "uvx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Anchor a file's SHA-256 fingerprint to Bitcoin. The file never leaves the device.
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked orphograph-mcp against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in finance
OKX trading MCP server — connect AI agents to spot, swap, futures, options & grid bots via the Model Context Protocol.
Ledger of AI-agent money on Base: payments, detections, Gate, signed Pass, Agent Books, free checks
Open-source AI Security Operations Center: alert fusion, LLM-agent triage, MITRE ATT&CK investigation, and a replayable decision ledger for every agent step. Self-hostable, runs with no API keys, MIT licensed. Ships an MCP server for Claude, Cursor and Continue.
Crypto briefs and data, Solana pre-trade checks, sanctions, papers, NLP. 102 tools, USDC, 20 chains.
MCP Security Weekly
Get CVE alerts and security updates for io.github.Orphograph/orphograph and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Bitcoin-anchored receipts that a relying party can verify without the issuer. Checking a file against its saved proof needs only the MIT verifier in this repository, with no account and no network call; confirming the timestamp against Bitcoin needs any OpenTimestamps client and a Bitcoin node, not Orphograph. The service can be unreachable or gone. It is for photographers, journalists, indie creators, and developers who need to prove a file existed before a given moment, especially before an AI model saw it, and anchoring a file takes about ten seconds. Files never leave the browser: only their fingerprints are sent, and only the 32-byte SHA-256 is committed to Bitcoin. Free tier (3 anchors every 24 hours), $5 Writer Pack (25 anchors), $20 Pack of Two Hundred (200 anchors), $9/mo Standing Order (unrestricted anchoring, private receipts, vault, API).
Four steps a developer can run from a terminal, no signup, no install
beyond curl and shasum.
Compute the SHA-256 of any file on disk:
shasum -a 256 ~/Pictures/my-photo.jpg
# → 3f8c1b... my-photo.jpg
Submit the hash to the public anchor endpoint:
curl -sS -X POST https://orphograph.com/api/anchor \
-H "Content-Type: application/json" \
-d '{"hash_hex":"<paste the 64-char hex digest>"}'
The response is a JSON receipt with a receipt_id and a list of the
OpenTimestamps calendars that accepted the submission.
Pull the receipt back later by ID (or visit /r/<id>):
curl -sS https://orphograph.com/api/verify/<receipt_id>
Verify offline against the original file with the standalone verifier (no orphograph code, MIT, ~100 lines of stdlib Python):
# Single file with an inclusion proof:
python3 dist/orphograph-verify/verify.py file \
--file ~/Pictures/my-photo.jpg \
--proof receipts/<receipt_id>/proof.json
# Whole folder against its manifest:
python3 dist/orphograph-verify/verify.py folder \
--dir ~/Pictures/evidence \
--manifest receipts/<receipt_id>/manifest.json
The verifier re-hashes the file (or walks the folder) locally and
confirms the result reproduces the manifest's root. Add --ots <path>.ots to also invoke the OpenTimestamps client and check the
chain witness references the same root.
Orphograph ships an MCP server: a single stdlib-only Python file (682
lines, MIT) that implements the Model Context Protocol — JSON-RPC 2.0 over
stdio, protocol version 2024-11-05, with the initialize, tools/list,
and tools/call methods implemented directly, no SDK — so AI agents and
MCP hosts (Claude Code, Claude Desktop, or any MCP client) can anchor and
verify files as tool calls.
Listed in the official MCP registry as io.github.Orphograph/orphograph.
MCP tools exposed (full JSON Schemas in mcp/manifest.json):
| Tool | What it does |
|---|---|
orphograph_anchor_file | Hash a local file (SHA-256/SHA-512 computed in-process) and anchor the fingerprints to Bitcoin via OpenTimestamps. The file body never leaves the machine. |
orphograph_anchor_folder | Build an RFC-6962 Merkle manifest over a folder and anchor one root that covers every file. |
orphograph_anchor_output | Anchor an AI agent's generated output at creation time — provenance receipts for agent actions. |
orphograph_verify_receipt | Look up what this office recorded for a receipt: anchored hashes, calendar attestation counts, and when the Bitcoin pin was observed. A lookup, not an independent chain check — run ots verify for that. No API key required. |
orphograph_verify_lineage | Walk an edit-lineage chain back through its committed parents and report the ordering the anchors establish. |
orphograph_list_vault | List the authenticated subscriber's anchored receipts. |
orphograph_anchor_run |