Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Anchor a file's SHA-256 fingerprint to Bitcoin. The file never leaves the device.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
ORPHO_API_KEY, ORPHO_BASE_URL, ORPHO_X402_PAYER_KEY_FILE, ORPHO_X402_DAILY_CAP_CENTS, ORPHO_X402_MAX_CENTS_PER_CALLValues marked secret are keys to your account. Never share them or paste them into a chat.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
Fill in the empty values before running it.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
ORPHO_BASE_URL envORPHO_X402_PAYER_KEY_FILE envORPHO_X402_DAILY_CAP_CENTS envORPHO_X402_MAX_CENTS_PER_CALL envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account Orphograph, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: ORPHO_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.6) reached the registry today.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, BankBridge
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Works in any MCP agent, including local models. Read-only bank accounts, spending, investments.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
A single-file Model Context Protocol server that lets a Claude / Claude Code / Cursor / any-MCP-host instance anchor files to the Bitcoin chain via Orphograph without the file ever leaving the user's machine.
mcp-name: io.github.Orphograph/orphograph
orphograph-mcp 0.1.1.Save the script anywhere:
curl -sSL https://orphograph.com/mcp/orphograph_mcp.py -o ~/bin/orphograph_mcp.py
Then register it with your MCP host.
~/Library/Application Support/Claude/claude_desktop_config.json){
"mcpServers": { "orphograph": { "command": "python3", "args": ["/Users/YOU/bin/orphograph_mcp.py"], "env": { "ORPHO_API_KEY": "" } } } }
claude mcp add orphograph python3 /Users/YOU/bin/orphograph_mcp.py
Or edit ~/.claude/settings.json and add the same mcpServers block.
~/.cursor/mcp.json){
"mcpServers": { "orphograph": { "command": "python3", "args": ["/Users/YOU/bin/orphograph_mcp.py"], "env": { "ORPHO_API_KEY": "" } } } }
| Tool | Purpose | Auth | |
|---|---|---|---|
orphograph_anchor_file(path) | Hash a local file and register the fingerprint on Bitcoin. | Optional API key | |
orphograph_anchor_folder(path) | Hash a whole folder into an RFC-6962 Merkle tree and anchor one root covering every file. | Optional API key | |
orphograph_anchor_output(text, …) | Hash generated output (an agent result, a transcript) in-process and anchor it. Accepts an optional zk_proof. The fingerprint is public on the receipt, so for short or guessable output pass salt: true: it anchors SHA-256(salt + text), returns salt_hex (never transmitted) and needs it to verify. Every anchor reply says bitcoin_status: pending until the calendars commit to a Bitcoin block (usually hours), then confirmed. | Optional API key | |
orphograph_verify_receipt(receipt_id) | Look up what the office recorded for a receipt. A lookup — it does NOT consult the chain; run ots verify for that. | None | |
orphograph_verify_lineage(receipt_id) | Walk an edit-lineage chain back through its committed parents. | None | |
orphograph_list_vault(limit?) | List the subscriber's receipts. | API key required | |
orphograph_anchor_run(steps, label?) | Anchor every step of an agent run under one receipt; each step provable alone. | None | |
| `orphograph_verify_output(receipt_id, text \ | sha256_hex, salt_hex?)` | Check whether a receipt covers an exact output, trusting only the anchored hash. Pass salt_hex for an output anchored with a salt. | None |
https://orphograph.com/api/anchor.| Environment variable | Purpose |
|---|---|
ORPHO_API_KEY | Optional. Issued from orphograph.com/account.html. Without it, the install is rate-limited to the free tier (3 anchors per 24 hours). |
ORPHO_BASE_URL | Optional. Defaults to https://orphograph.com. Override for testing or self-hosted instances. |
ORPHO_X402_PAYER_KEY_FILE | Optional (0.1.6). Path to a chmod 600 file holding the hex private key of a dedicated Base wallet with USDC. With the daily cap below, anchors past the free tier are paid with x402. The key never leaves the machine. |
ORPHO_X402_DAILY_CAP_CENTS | Optional (0.1.6). The most the server may pay in one UTC day, in cents. Paying stays off unless this and the key file are both set. |
ORPHO_X402_MAX_CENTS_PER_CALL | Optional (0.1.6). The most one anchor may cost, in cents. Default 5. |
With paying on, the server pins the USDC contract, its signing domain and the chain (Base); a 402 asking for anything else, or for more than either cap, is declined and nothing is signed. Spending is recorded in ~/.orphograph/x402_spend.json. A paid result carries x402_payment with the amount and the on-chain transaction.
| Tier | Cap | Price |
|---|---|---|
| Free | 3 anchors / 24h | $0 |
| Writer Pack | 25 anchors, never expires | $5 one-time |
| Pack of Two Hundred | 200 anchors, never expires | $20 one-time |
| Standing Order | Unrestricted anchoring | $9 / month |
| Agents (x402) | Past the free tier, per anchor | 1 cent in USDC on Base |
The MCP server only issues calls. Every receipt it produces can be checked without this office, in two independent steps:
ots verify) confirms the commitment actually landed in a Bitcoin block. The bundled verifier will invoke it for you when passed --ots.Only step 2 consults Bitcoin.
Open an issue at the public repo, or write to hello@orphograph.com.