mcpbeat Sign in

Doichain MCP Server

answering

Doichain is answering right now. Last checked 3 min ago. It exposes 13 tools. Last commit 27 Sep 2026.

Proof of existence, names and chain data of the Doichain blockchain for AI agents

Uptime history 16 days of history · worst day 99%
16 days agonow
100.0%
Uptime 24h
92 of 92 checks
13
Tools
read from the server
139 ms
Response time
average over 24h
0
Stars
last commit 27 Sep 2026

What changed 6

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 27 September 2026. No other catalogue keeps this.

27 Sep 3 tool descriptions were rewritten anchor_proof, check_proof, search_names
27 Sep 2 tools changed the parameters they ask for anchor_proof, search_names
27 Sep a tool changed version

Doichain missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

run in your terminal
claude mcp add doichain --transport http https://doi-api.sendlabs.de/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "doichain": {
      "url": "https://doi-api.sendlabs.de/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.doichain]
url = "https://doi-api.sendlabs.de/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "doichain": {
      "url": "https://doi-api.sendlabs.de/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "doichain": {
      "url": "https://doi-api.sendlabs.de/mcp"
    }
  }
}

Available tools 13

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

name
check_name_expiry
Check up to 25 names at once: status (active, expiring_soon, expired, not_registered), blocks left, an estimated expiry date for active names (from the measured block interval) and the real expiry date for expired names. Names expire 36,000 blocks after their last update and are renewed by updating them from the owning wallet.
get_name_history
All registrations and updates of a name, newest first: block height, transaction, owner address and the value at that time. Shows who held a name when, and every value it ever had.
address
get_address
Confirmed and unconfirmed balance of a Doichain address in DOI, optionally with its most recent transactions. Invalid addresses return an error with the reason.
anchor
anchor_proof
Anchor a SHA-256 hash on the Doichain as a tamper-evident timestamp (proof of existence, name poe/<sha256>). Free for users, limited per IP address and day (see get_anchoring_quota). Confirms with the next block, usually within 10 minutes, then check_proof returns block height and time. If the hash is already anchored or pending, the existing proof is returned instead of creating a second one. If an earlier proof of the hash has expired, it stays valid and is returned with expired true. Nothing is registered unless reanchor_expired is true. Only the hash and the optional note and file name become public, never the document itself. The operator of this server pays for the name and holds it. The proof shows that a document with this hash existed no later than the block time, not who submitted it.
anchoring
get_anchoring_quota
How many proofs can still be anchored today (UTC day) within the free public quota for the caller's IP address. Hosted chat apps connect from their own servers, so their users share one quota. Callers that send their own API key in the X-API-Key header have no quota.
block
get_block
Header data of a block by height or hash: time, confirmations, number of transactions and the first 50 transaction IDs.
chain
get_chain_status
Current state of the Doichain network as seen by the node behind this server: block height, sync state, time of the last block, fork check, node version, peers, mempool size and whether public anchoring is available.
hash
hash_text
Compute the SHA-256 digest of a short text (UTF-8) on the server, for example to anchor a statement or a message with anchor_proof. The text is sent to the server but not stored or logged. For files and for confidential texts compute the hash locally instead (sha256sum file, or Get-FileHash -Algorithm SHA256).
lookup
lookup_name
Read the current value, owner address and expiry of a Doichain name. Unregistered names come back with exists false and status not_registered (the name is free). Expired names have status expired and the real expiry date.
names
search_names
List names that start with a prefix, in the node's order (shorter names first, then byte order). Lists only active names unless include_expired is true. Expired names (for example old poe/ proofs) stay in the chain history and are listed with include_expired. Page through large results with next_after until exhausted is true. Names and values are chosen by arbitrary users (name_untrusted, value_untrusted).
proof
check_proof
Check whether a SHA-256 hash is anchored on the Doichain (name poe/<sha256>) and since when. Returns status (confirmed, pending, expired, unknown) and at the top level block height, block time, transaction and links of the first anchoring, which is the proof time. If the name was updated later or registered again after it expired (possibly by someone else), that registration is reported separately in latest_registration with its own holder and record, which are not part of the original proof. A confirmed or expired proof shows that a document with exactly this hash existed no later than the block time, not who submitted it.
transaction
get_transaction
A transaction with confirmations, block time, outputs (amount in DOI and address) and any name operation (name_doi, name_update, ...) it contains.
verify
verify_message
Check whether a message was signed with the private key of a Doichain address (signmessage format). Only legacy addresses (M... or N...) can sign messages, bech32 addresses (dc1q...) are not supported. Useful to confirm that a statement really comes from the holder of an address.

Endpoints

URLTransportStateLatencyChecked
https://doi-api.sendlabs.de/mcp streamable-http answering 155 ms 3 min ago

Alternatives to Doichain

same job, measured the same way
Taste
by humantaste

Expert review for AI agents. On-chain proof of human review.

20 tools answering
Steledger
by steledger

Durable identity and memory for AI agents, anchored on the Emercoin blockchain.

9 tools answering
Proctor
by louissarvin

Human oversight for AI agents: block a tool call on a verified human, with on-chain proof.

29 installs/wk local only
Supership Scan
by andysalvo

Buy any x402 API or data on Base, Solana, Polygon. No wallet on the seller's chain. For AI agents.

53 installs/wk local only
Blockscout MCP Server
by smithery

Provide AI agents and automation tools with contextual access to blockchain data including balance…

answering
Raptr Domains
by kody-w

Check and price up to 20 domain names at once; agents can register them, paying per request.

3 tools answering
Rapp Domains
by kody-w

Check and price up to 20 domain names at once; agents can register them, paying per request.

3 tools answering
Evmscope
by calintzy

EVM blockchain intelligence toolkit for AI agents. 20 tools across 5 chains. Zero config.

46 installs/wk local only

Doichain — questions

Answers built from our own checks of this server.

What can Doichain do?
It exposes 13 tools, read directly from the server on our last check. Among them: anchor_proof, check_name_expiry, check_proof, get_address, get_anchoring_quota, get_block and 7 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Doichain working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 139 ms. The bar chart above shows every period we have measured.
How do I connect Doichain?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Doichain need an API key?
No. Doichain completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 13 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Doichain?
It answers our handshake in 139 ms on average, which is faster than 74% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Doichain open source?
Yes — it is published under the MIT licence, written in Python, 0 stars on GitHub and 3 open issues. The source link is on this page, so you can read exactly what it does with your data before you connect it.