# Orphograph MCP server

> Anchors file SHA-256 fingerprints to the Bitcoin blockchain without the files ever leaving the user's device.

- Repository: https://github.com/Orphograph/Orphograph
- Page: https://hostedmcp.org/servers/orphograph/orphograph
- Transport: stdio
- Stars: 0
- License: MIT
- Latest version: 0.1.6

## Environment variables

| Name | Required | Secret | Description |
|---|---|---|---|
| `ORPHO_API_KEY` | no | yes | Optional API key issued from https://orphograph.com/account.html. Without it, anchors are subject to the free-tier rate limit (three anchors per twenty-four hours per IP). With it, the customer's subscription or Pack credits apply. |
| `ORPHO_BASE_URL` | no | no | Base URL for the Orphograph API. Defaults to https://orphograph.com. Override only for testing or self-hosted instances. |
| `ORPHO_X402_DAILY_CAP_CENTS` | no | no | Optional. The most this server may pay in one UTC day, in cents. Paying stays off unless this and ORPHO_X402_PAYER_KEY_FILE are both set. |
| `ORPHO_X402_MAX_CENTS_PER_CALL` | no | no | Optional. The most one anchor may cost, in cents. Default 5. |
| `ORPHO_X402_PAYER_KEY_FILE` | no | no | Optional. Path to a chmod-600 file holding the hex private key of a dedicated Base wallet with USDC. With ORPHO_X402_DAILY_CAP_CENTS set too, anchors past the free tier are paid with x402 (1 cent today). The key never leaves the machine. |

## Tools (8)

- `orphograph_anchor_file`: Anchor 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_folder`: Anchor 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_output`: Anchor 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_receipt`: Look 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_lineage`: Walk 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_vault`: List the signed-in subscriber's anchored receipts. Requires ORPHO_API_KEY in the environment. The key is issued from https://orphograph.com/account.html.
- `orphograph_anchor_run`: Anchor every step of an AI agent run under ONE Bitcoin-anchored receipt. Each step is hashed locally; only one SHA-256 digest per step and the Merkle root are transmitted, never the step text. Any single step stays provable on its own with orphograph_verify_output. Proves the steps existed by the anchor time, not who produced them or that they are correct. Step digests are public on the receipt: add a random nonce to short or guessable steps.
- `orphograph_verify_output`: Check whether an exact output is covered by a receipt, for the agent RECEIVING the output. Works for single anchors and for agent runs. Trusts only the anchored hash: for a run, the manifest is recomputed locally and must match it. Returns match true/false, the anchor time, and the reason when false.

## FAQ

### Does my file leave my computer?

No, the file body never leaves your device; the script only transmits SHA-256 and SHA-512 fingerprints to the API.

### How long does it take for an anchor to be confirmed?

The status remains 'pending' until the calendars commit to a Bitcoin block, which usually takes a few hours.

### What are the limits for the free tier?

The free tier allows for 3 anchors every 24 hours.

### Can I anchor an entire folder?

Yes, you can hash a whole folder into an RFC-6962 Merkle tree to anchor a single root covering every file.
