Doichain
REMOTE · DOI-API.SENDLABS.DE · SCANNED OCT 4
Proof of existence, names and chain data of the Doichain blockchain for AI agents
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2062 tokens (~158/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Doichain MCP server?
Doichain is a hosted endpoint at https://doi-api.sendlabs.de/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · doi-api.sendlabs.de
claude mcp add --transport http neubuot-doichain 'https://doi-api.sendlabs.de/mcp'
{
"mcpServers": {
"neubuot-doichain": {
"url": "https://doi-api.sendlabs.de/mcp"
}
}
} {
"servers": {
"neubuot-doichain": {
"type": "http",
"url": "https://doi-api.sendlabs.de/mcp"
}
}
} [mcp_servers.neubuot-doichain] url = "https://doi-api.sendlabs.de/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"neubuot-doichain": {
"type": "remote",
"url": "https://doi-api.sendlabs.de/mcp",
"enabled": true
}
}
} openclaw mcp add neubuot-doichain --url 'https://doi-api.sendlabs.de/mcp' --transport streamable-http
mcp_servers:
neubuot-doichain:
url: "https://doi-api.sendlabs.de/mcp" {
"McpServers": {
"neubuot-doichain": {
"Transport": "http",
"Url": "https://doi-api.sendlabs.de/mcp"
}
}
} assistant mcp add neubuot-doichain -t streamable-http -u 'https://doi-api.sendlabs.de/mcp'
{
"mcpServers": {
"neubuot-doichain": {
"type": "http",
"url": "https://doi-api.sendlabs.de/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “anchor_proof” rewrote its description, which is the text the model reads security
- Tool “check_proof” rewrote its description, which is the text the model reads security
- Tool “search_names” rewrote its description, which is the text the model reads security
- Schema quality: 126 → 158 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.4.1 → 1.5.0 functional
- “anchor_proof” added an optional parameter “reanchor_expired” cosmetic
- “search_names” added an optional parameter “include_expired” cosmetic
- 26 Sept 26 74
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Oct 2026 · Probed https://doi-api.sendlabs.de/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=doi-api.sendlabs.de | CN=YE2,O=Let's Encrypt,C=US | 25 Sept 2026 | 24 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 54d11eed9d75e2c5775f98fb385ef9ab2b3 |
| SANs: doi-api.sendlabs.de | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of doi-api.sendlabs.de. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| de. | present | 26755 | 8 | Verified |
| sendlabs.de. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://doi-api.sendlabs.de/mcp | Verified | 200 | |
| http (plaintext) | http://doi-api.sendlabs.de/mcp | HTTPS enforced | 301 | https://doi-api.sendlabs.de/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
anchor_proof Anchor a proof of existence ~353
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.
| Name | Type | Req | Description |
|---|---|---|---|
| filename | – | – | Optional public file name (max 80 characters), stored forever. Only set it when the user explicitly wants the name public |
| note | – | – | Optional public note (max 160 characters), stored on the blockchain forever. No personal data, no secrets |
| reanchor_expired | boolean | – | Only set to true when an earlier proof of this hash has expired and the user explicitly wants an additional, later registration. The original anchoring stays the proof time. The new registration adds… |
| sha256 | string | yes | SHA-256 digest of the document, 64 hexadecimal characters, computed from the actual file. Never guess it and never send the document |
Structured output declared, but exposes no named fields.
No examples provided.
check_name_expiry Check when names expire ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| names | array | yes | Up to 25 full names, for example ['d/example', 'poe/<sha256>'] |
| warn_days | integer | – | Names expiring within this many days are flagged expiring_soon |
Structured output declared, but exposes no named fields.
No examples provided.
check_proof Check a proof of existence ~181
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.
| Name | Type | Req | Description |
|---|---|---|---|
| sha256 | string | yes | SHA-256 digest of the document, 64 hexadecimal characters (a sha256: or 0x prefix is accepted) |
Structured output declared, but exposes no named fields.
No examples provided.
get_address Address balance and history ~99
Confirmed and unconfirmed balance of a Doichain address in DOI, optionally with its most recent transactions. Invalid addresses return an error with the reason.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Doichain address (M... or N..., 6..., or bech32 dc1q...) |
| history_limit | integer | – | Number of recent transactions when include_history is true |
| include_history | boolean | – | Also return the most recent transactions |
Structured output declared, but exposes no named fields.
No examples provided.
get_anchoring_quota Remaining anchoring quota ~75
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.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_block Get a block ~52
Header data of a block by height or hash: time, confirmations, number of transactions and the first 50 transaction IDs.
| Name | Type | Req | Description |
|---|---|---|---|
| block | – | yes | Block height (number) or block hash (64 hexadecimal characters) |
Structured output declared, but exposes no named fields.
No examples provided.
get_chain_status Doichain network status ~58
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.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_name_history History of a Doichain name ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of entries, newest first |
| name | string | yes | Full name including namespace |
Structured output declared, but exposes no named fields.
No examples provided.
get_transaction Get a transaction ~57
A transaction with confirmations, block time, outputs (amount in DOI and address) and any name operation (name_doi, name_update, ...) it contains.
| Name | Type | Req | Description |
|---|---|---|---|
| txid | string | yes | Transaction ID, 64 hexadecimal characters |
Structured output declared, but exposes no named fields.
No examples provided.
hash_text SHA-256 of a text ~119
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).
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Text to hash, encoded as UTF-8 exactly as given (whitespace and line breaks count), at most 40,000 characters |
Structured output declared, but exposes no named fields.
No examples provided.
lookup_name Look up a Doichain name ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Full name including namespace, for example poe/<sha256>, d/example or id/alice |
Structured output declared, but exposes no named fields.
No examples provided.
search_names Search names by prefix ~175
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).
| Name | Type | Req | Description |
|---|---|---|---|
| after | – | – | Paging cursor: pass next_after from the previous result unchanged |
| include_expired | boolean | – | Also list expired names, for example proofs whose poe/ name has expired. Default false: active names only |
| limit | integer | – | Maximum number of names |
| prefix | string | yes | Name prefix, for example poe/, d/ or id/ |
Structured output declared, but exposes no named fields.
No examples provided.
verify_message Verify a signed message ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Legacy Doichain address (M... or N...) that supposedly signed the message |
| message | string | yes | The exact signed text |
| signature | string | yes | Signature in Base64 |
Structured output declared, but exposes no named fields.
No examples provided.
What is the Doichain MCP server?
Doichain is an MCP server listed in the public MCP registry as io.github.neubuot/doichain. Proof of existence, names and chain data of the Doichain blockchain for AI agents. This page covers its hosted endpoint (https://doi-api.sendlabs.de/mcp).
Is the Doichain MCP server safe to use?
Doichain scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Doichain MCP server expose?
Doichain exposes 13 tools: get_chain_status, hash_text, check_proof, anchor_proof, get_anchoring_quota, and 8 more. Their descriptions and schemas cost roughly 1,579 tokens of context every time the server is loaded.
Does the Doichain MCP server require authentication?
No. We connected to Doichain without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Doichain MCP server still maintained?
Doichain is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.