Orphograph

Name: Orphograph
Author: Orphograph

作者：Orphograph版本 0.1.6i★ –i在你的电脑上运行

注册名称io.github.Orphograph/orphograph

安装

概览

作者提供的说明（英文原文）

Anchor a file's SHA-256 fingerprint to Bitcoin. The file never leaves the device.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他
你需要填写：ORPHO_API_KEY

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： ORPHO_API_KEY, ORPHO_BASE_URL, ORPHO_X402_PAYER_KEY_FILE, ORPHO_X402_DAILY_CAP_CENTS, ORPHO_X402_MAX_CENTS_PER_CALL

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

下载作者的 .mcpb 文件

链接指向作者自己的文件；我们不托管也不重新打包它。打开文件后，Claude Desktop 会进行安装。

在终端中运行这条命令

运行前请先填写空着的值。

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

ORPHO_API_KEY 机密 env
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 sub…
ORPHO_BASE_URL env
Base URL for the Orphograph API. Defaults to https://orphograph.com. Override only for testing or self-hosted instances.
ORPHO_X402_PAYER_KEY_FILE env
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 tod…
ORPHO_X402_DAILY_CAP_CENTS env
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 env
Optional. The most one anchor may cost, in cents. Default 5.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 Orphograph 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32403 个服务器的 0%
发布到注册中心的时间比此分类中其他 32403 个服务器的 99% 更新
基础检查结果等于或优于此分类中其他 32403 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Orphograph 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：ORPHO_API_KEY

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.1.6）于今天进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 MCPB。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, LickityClick

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211昨天更新

安装

LickityClick

作者：lickity.click

Create, edit and track LickityClick short links, campaigns and click stats from your AI assistant.

电脑或云端今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Orphograph MCP server

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

License: MIT
Dependencies: Python ≥ 3.9 standard library only. Also on PyPI as orphograph-mcp 0.1.1.
Lines of code: ~310, single file.
Protocol: MCP 2024-11-05 over stdio.

Install

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.

Claude Desktop (`~/Library/Application Support/Claude/claude_desktop_config.json`)

"mcpServers": { "orphograph": { "command": "python3", "args": ["/Users/YOU/bin/orphograph_mcp.py"], "env": { "ORPHO_API_KEY": "" } } } }

Claude Code

claude mcp add orphograph python3 /Users/YOU/bin/orphograph_mcp.py

Or edit ~/.claude/settings.json and add the same mcpServers block.

Cursor (`~/.cursor/mcp.json`)

"mcpServers": { "orphograph": { "command": "python3", "args": ["/Users/YOU/bin/orphograph_mcp.py"], "env": { "ORPHO_API_KEY": "" } } } }

Tools exposed

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

Privacy contract

The file body never leaves the device.
The script computes SHA-256 + SHA-512 in-process and transmits only those fingerprints to https://orphograph.com/api/anchor.
The script makes no network call until a tool is explicitly invoked by the host.
File reads stream in 1 MB chunks; large files do not load into memory.

Configuration

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.

Tiers and limits

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

Verification

The MCP server only issues calls. Every receipt it produces can be checked without this office, in two independent steps:

Structure — the open-source verifier at github.com/Orphograph/Orphograph re-derives the hashes and checks the receipt offline. It makes no network calls of its own.
Chain — the OpenTimestamps client (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.

Reporting issues

Open an issue at the public repo, or write to hello@orphograph.com.