Doichain MCP Server

Tamper-evident timestamps for your AI agent.
Prove that a document already existed at a given time: anchor its hash on the Doichain (proof of existence), verify proofs and read names, blocks and addresses.
One URL, no account, no API key, no installation.

Quick start · Tools · How it works · Limits · Security · Tool reference · Self-hosting · Deutsch

Endpoint: https://doi-api.sendlabs.de/mcp · Streamable HTTP · stateless · no authentication required

The Doichain is a public blockchain with a built-in name-value store (a Namecoin descendant, merge-mined with Bitcoin). This server makes it usable for any agent that speaks the Model Context Protocol: Claude, ChatGPT, Cursor, VS Code Copilot and many more. Ask your agent in plain language, it picks the right tool itself:

"Anchor the hash of offer-2026.pdf on the Doichain." "Did this contract already exist before October 1?" "Are d/example or id/alice about to expire?" "How is the Doichain doing right now?"

Opening the endpoint in a browser shows the landing page with setup instructions.

Quick start

Claude Code

Terminal

claude mcp add --scope user --transport http doichain https://doi-api.sendlabs.de/mcp

Check with claude mcp list. Without --scope user the server only applies to the current project.

Claude (web and desktop)

Open Customize → Connectors and click +.
Choose Add custom connector, name it Doichain and paste https://doi-api.sendlabs.de/mcp.
In a chat, enable it via + → Connectors.

Custom connectors also work on the free plan (one connector). On Team and Enterprise an owner adds it in the organization settings.

ChatGPT

Turn on Settings → Security and login → Developer mode, then create an app under Plugins → + with the URL above and authentication None. Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education.

Cursor

~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

config.json

{
  "mcpServers": {
    "doichain": { "url": "https://doi-api.sendlabs.de/mcp" }
  }
}

VS Code (Copilot agent mode)

.vscode/mcp.json:

config.json

{
  "servers": {
    "doichain": { "type": "http", "url": "https://doi-api.sendlabs.de/mcp" }
  }
}

Any other client

Setting	Value
URL	`https://doi-api.sendlabs.de/mcp`
Transport	Streamable HTTP (`http` / `streamable-http`), stateless, JSON responses
Authentication	none, optionally your own key in the `X-API-Key` header
Protocol versions	2024-11-05, 2025-03-26, 2025-06-18, 2025-11-25, 2026-07-28

Try it without an AI client using the MCP Inspector: npx @modelcontextprotocol/inspector, choose Streamable HTTP and enter the URL. A small Python example is in examples/check_proof.py.

Tools

Tool	What it does	Access
`anchor_proof`	Anchor the SHA-256 of a document as a tamper-evident timestamp (proof of existence, name `poe/<sha256>`). Already anchored hashes return the existing proof. An expired hash is only registered again with `reanchor_expired: true`.	writes
`check_proof`	Is this hash anchored, since when, in which block? Always reports the first anchoring and shows a later registration of the name separately.	reads
`hash_text`	SHA-256 of a short text (up to 40,000 characters), computed on the server, nothing stored.	server-side
`get_anchoring_quota`	Proofs still available today for the caller's IP address.	reads
`lookup_name`	Current value, owner and expiry of a name such as `d/example` or `id/alice`.	reads
`get_name_history`	Every registration and update of a name, newest first.	reads
`check_name_expiry`	Up to 25 names at once: active, expiring soon, expired or free, with dates.	reads
`search_names`	Names by prefix (for example all `poe/` proofs), with paging. Expired names with `include_expired`.	reads
`get_chain_status`	Block height, sync state, last block, fork check, average block interval.	reads
`get_block`	A block by height or hash.	reads
`get_transaction`	A transaction with outputs, addresses and name operations.	reads
`get_address`	Balance of an address, optionally with recent transactions.	reads
`verify_message`	Check a message signed with a Doichain address (legacy `M…`/`N…` addresses).	reads

All tools return structured JSON (structuredContent) and carry MCP tool annotations. Only anchor_proof is not read-only. Parameters, return fields and examples: docs/tools.md.

How a proof of existence works

mermaid

sequenceDiagram
    participant U as You
    participant A as AI agent
    participant M as Doichain MCP server
    participant D as Doichain
    U->>A: "Anchor offer-2026.pdf"
    A->>A: sha256sum offer-2026.pdf (the file never leaves your machine)
    A->>M: anchor_proof(sha256)
    M->>D: name_doi poe/<sha256> = {"v":1,"alg":"sha256",...}
    D-->>M: transaction id (pending)
    M-->>A: txid, verify URL
    Note over D: next block, usually within 10 minutes
    U->>A: "Did this document exist before October 1?"
    A->>M: check_proof(sha256)
    M->>D: name_show / name_history
    M-->>A: confirmed, block 433,335, 2026-09-25 23:21 UTC

Only the hash, and optionally a public note or file name, goes on chain. A SHA-256 cannot be turned back into the document. Anyone can verify a proof later with check_proof or on verifile.it, and changing a single byte of the document produces a different hash.

What a proof shows, and for how long:

The timestamp is permanent. The anchoring transaction and its block time stay in the blockchain history for good.
The name is not. poe/<sha256> stays active for 36,000 blocks (about 250 days at ten minutes per block). After that anyone can register it again, with their own note and address. check_proof keeps reporting the first anchoring as the proof time and shows a later registration separately in latest_registration. anchor_proof does not register an expired hash again unless you ask for it with reanchor_expired, and search_names lists expired proofs with include_expired.
Existence, not authorship. A proof shows that a document with this hash existed no later than the block time. It does not show who submitted it. The hosted endpoint registers the names from the operator's wallet, which pays for them and holds them.

Agents need access to the file to hash it (Claude Code, Cursor, VS Code). In a plain chat, Verifile is the easiest way: drop the file, it is hashed in the browser and anchored with one click.

Limits and quotas

Limit	Value
Anchoring	free for users, 10 proofs per IP address per UTC day, at most 200 per day for all users together
Requests	10 per second per IP address (burst 40), JSON-RPC error `-32000` with `Retry-After: 1` when exceeded
Request size	256 KB, `hash_text` up to 40,000 characters
Reading and checking	unlimited within the request rate

Hosted chat apps (Claude on the web, ChatGPT) connect from their providers' data centers, so all their users share the quota of those addresses. For regular anchoring use a client that connects from your own machine (Claude Code, Cursor, VS Code) or ask DOI Labs for an own key. Anchoring pauses automatically when the operating balance of the node wallet falls below a reserve, reading keeps working.

Security and privacy

Hashes only. The server accepts no files. hash_text sees a short text and forgets it immediately.
No wallet functions. The server cannot send coins, change names or call node RPCs. Its only write operation is anchor_proof, for which the REST API registers the name from the operator's wallet. It runs as a separate service under its own system user, without read access to the API's key file, and may only open local connections.
Prompt injection protection. Names and values written to the chain by strangers are returned in fields ending in _untrusted together with a notice, and the server instructions tell agents to treat them as data only.
DNS rebinding protection. Host and Origin headers are validated.
No tracking. No cookies, no third-party resources on the landing page. Like any web server, IP addresses appear in access logs and count toward the daily quota. Content is not stored.

Found a vulnerability? Please use private vulnerability reporting, see SECURITY.md.

Protocol behavior

Streamable HTTP in stateless mode with JSON responses, so any number of workers can serve requests without session affinity.
POST /mcp for all MCP messages. GET /mcp from a browser returns the landing page, any other GET or HEAD returns 405 with Allow: POST (there is no server-to-client SSE stream in stateless mode).
No JSON-RPC batches (removed from the protocol in 2025-06-18). No CORS, so clients running directly inside a web page are not supported.
GET /mcp/health for monitoring.

Architecture

Code

AI agent ──HTTPS──▶ nginx ──▶ doichain-mcp (this repo, 127.0.0.1:8081)
                                  │  REST calls only, client IP passed on for the quota
                                  ▼
                          Doichain REST API (127.0.0.1:8080) ──▶ Doichain Core v31.1.6 + ElectrumX

The MCP server is a thin, stateless layer over the Doichain REST API (interactive docs), which runs next to a full Doichain Core node. See docs/self-hosting.md to run your own instance.

Development

bash

python -m venv .venv
. .venv/bin/activate          # Windows: .venv\Scripts\activate
pip install -e ".[dev]"
pytest -q                     # offline tests, the REST API is mocked
ruff check .

# run locally against the public REST API (reading works, anchoring needs your own key)
DOI_MCP_API_URL=https://doi-api.sendlabs.de python -m doichain_mcp
npx @modelcontextprotocol/inspector   # connect to http://127.0.0.1:8081/mcp

Releases follow semantic versioning. Pushing a tag vX.Y.Z runs the tests and publishes server.json to the official MCP Registry via GitHub Actions (OIDC, no secrets). The tag, server.json and pyproject.toml must carry the same version. See CONTRIBUTING.md and CHANGELOG.md.

Verifile: proof of existence by drag and drop, no upload
Doichain REST API: the HTTP interface behind this server, with a live playground
Doichain Core: the reference node
Doichain Explorer: blocks, transactions and names

Doichain README