Orphograph

io.github.Orphograph由 GitHub 账号 Orphograph 发布v0.1.6更新于 Nov 6, 2026

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

已验证STDIO仅桌面金融安全与监控

概览

AI 生成的概览

Orphograph 把本地文件、文件夹或生成文本的 SHA-256 指纹锚定到比特币，文件内容不离开本机。

可以做什么
  • 将本地文件或整个文件夹（合并为一个 Merkle 根）锚定到比特币
  • 锚定生成的文本或智能体运行的各个步骤，可选加盐或附带 zk 证明
  • 查询回执并追溯编辑谱系链
  • 按文本或哈希校验某份回执是否覆盖某个确切输出
  • 列出订阅者保险库中的回执
适用场景
当你需要可防篡改、带时间戳地证明某个文件、文件夹或 AI 生成输出在某一时刻以某种形态存在时适用，例如审计留痕、智能体运行溯源或档案记录，同时内容本身保持私密。
运行要求
以 stdio 方式在本机运行，为单个 Python 脚本（需 Python 3.9 及以上，仅用标准库），也可用 mcpb 包安装，PyPI 上亦有发布。调用工具时需要访问 Orphograph API 的网络连接。可选 ORPHO_API_KEY 可提高免费额度；ORPHO_BASE_URL 可覆盖接口地址。
安装前请注意
锚定会把指纹发送给第三方服务，且指纹在回执上是公开的，因此简短或可猜测的输出应加盐。免费额度为每 24 小时 3 次锚定，更多需付费套餐或 x402 支付。启用支付需设置 ORPHO_X402_PAYER_KEY_FILE（存放 Base 钱包私钥、含 USDC 的文件），并配合 ORPHO_X402_DAILY_CAP_CENTS 与 ORPHO_X402_MAX_CENTS_PER_CALL 限制支出。回执查询并不校验链上状态，需用 OpenTimestamps 客户端确认。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Orphograph，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only，通过 STDIO。 STDIO 服务会启动本地进程，因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

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)

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)

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

Tools exposed

ToolPurposeAuth
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 variablePurpose
ORPHO_API_KEYOptional. Issued from orphograph.com/account.html. Without it, the install is rate-limited to the free tier (3 anchors per 24 hours).
ORPHO_BASE_URLOptional. Defaults to https://orphograph.com. Override for testing or self-hosted instances.
ORPHO_X402_PAYER_KEY_FILEOptional (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_CENTSOptional (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_CALLOptional (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

TierCapPrice
Free3 anchors / 24h$0
Writer Pack25 anchors, never expires$5 one-time
Pack of Two Hundred200 anchors, never expires$20 one-time
Standing OrderUnrestricted anchoring$9 / month
Agents (x402)Past the free tier, per anchor1 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:

  1. 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.
  2. 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 [email protected].

来源：mcp/README.md，提交 c770c4d

工具

0
SourceWeft 曾在隔离沙箱中以无凭据方式启动该软件包一次，以列出其工具，但未能完成：该软件包类型无法在沙箱中运行。

版本历史

5
  1. v0.1.6最新Nov 6, 2026
  2. v0.1.5Nov 5, 2026
  3. v0.1.3Nov 5, 2026
  4. v0.1.2Oct 15, 2026
  5. v0.1.1Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手；SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头，或保持端点能够响应探测，以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分