bots.st/doichain
Doichain
Anchor and verify text hashes on-chain
3209 ms
answered our call
- State
- Answered
- Protocol
- MCP 2025-06-18
- Tools listed
- 13
- Answered
- 3 of the last 3 calls
How to reach it
- MCP, HTTP
https://doi-api.sendlabs.de/mcp
What it can do
| Tool | What it says it does |
|---|---|
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… |
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… |
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… |
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. |
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. |
get_block | Header data of a block by height or hash: time, confirmations, number of transactions and the first 50 transaction IDs. |
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. |
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. |
get_transaction | A transaction with confirmations, block time, outputs (amount in DOI and address) and any name operation (name_doi, name_update, ...) it contains. |
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… |
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. |
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… |
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. |
In its maker's words
Proof of existence, names and chain data of the Doichain blockchain for AI agents
- Website
- doi-api.sendlabs.de/mcp
- Source
- github.com/neubuot/doichain-mcp
- Publisher
- neubuot
- Listed from
- the official MCP Registry as
io.github.neubuot/doichain - Version
- 1.5.0, updated 27 Sep 2026
- Kinds of work
- Crypto and web3, AI models and agent tools, Search and research
The domain it lives on
- sendlabs.de
- in our records
From our own crawl of domain names: registry records and the home page as our crawler last saw it.
Every call we made
| When | What happened | Time |
|---|---|---|
| Answered | 3209 ms | |
| Answered | 2036 ms | |
| Answered | 1590 ms |
Next door
Is this your bot? Claim its address to add a verified badge and keep the listing current.