# Doichain (remote · doi-api.sendlabs.de)

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

- Trust score: 77/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-04

## Components

- remote · `doi-api.sendlabs.de`: 77/100 (this document), [markdown](https://verifymcp.io/servers/neubuot-doichain/doi-api.md), [page](https://verifymcp.io/servers/neubuot-doichain/doi-api)

## Channel facts

- Endpoint: `https://doi-api.sendlabs.de/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.5.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-04.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http neubuot-doichain 'https://doi-api.sendlabs.de/mcp'
```

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.neubuot-doichain]
url = "https://doi-api.sendlabs.de/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "neubuot-doichain": {
      "type": "remote",
      "url": "https://doi-api.sendlabs.de/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add neubuot-doichain --url 'https://doi-api.sendlabs.de/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  neubuot-doichain:
    url: "https://doi-api.sendlabs.de/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "neubuot-doichain": {
      "Transport": "http",
      "Url": "https://doi-api.sendlabs.de/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add neubuot-doichain -t streamable-http -u 'https://doi-api.sendlabs.de/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-04 (score 77, +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.

### 2026-10-02 (score 76, +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.

### 2026-09-30 (score 75, +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.

### 2026-09-28 (score 74, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 73, −1)

- [security] 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
- [functional regression] Schema quality: 126 → 158
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.4.1 → 1.5.0
- [cosmetic] “anchor_proof” added an optional parameter “reanchor_expired”
- [cosmetic] “search_names” added an optional parameter “include_expired”

### 2026-09-26 (score 74)

First indexed and scored.

## MCP tools (13)

### `get_chain_status` (~58 tokens)

Doichain network 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_text` (~119 tokens)

SHA-256 of a 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).

Input parameters:

- `text` (string, required): Text to hash, encoded as UTF-8 exactly as given (whitespace and line breaks count), at most 40,000 characters

### `check_proof` (~181 tokens)

Check a proof of existence

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.

Input parameters:

- `sha256` (string, required): SHA-256 digest of the document, 64 hexadecimal characters (a sha256: or 0x prefix is accepted)

### `anchor_proof` (~353 tokens)

Anchor a proof of existence

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.

Input parameters:

- `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, required): SHA-256 digest of the document, 64 hexadecimal characters, computed from the actual file. Never guess it and never send the document

### `get_anchoring_quota` (~75 tokens)

Remaining 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.

### `lookup_name` (~83 tokens)

Look up a Doichain 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.

Input parameters:

- `name` (string, required): Full name including namespace, for example poe/<sha256>, d/example or id/alice

### `get_name_history` (~75 tokens)

History of a Doichain name

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.

Input parameters:

- `limit` (integer): Maximum number of entries, newest first
- `name` (string, required): Full name including namespace

### `check_name_expiry` (~135 tokens)

Check when names expire

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.

Input parameters:

- `names` (array, required): Up to 25 full names, for example ['d/example', 'poe/<sha256>']
- `warn_days` (integer): Names expiring within this many days are flagged expiring_soon

### `search_names` (~175 tokens)

Search names by prefix

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).

Input parameters:

- `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, required): Name prefix, for example poe/, d/ or id/

### `get_block` (~52 tokens)

Get a block

Header data of a block by height or hash: time, confirmations, number of transactions and the first 50
    transaction IDs.

Input parameters:

- `block` (required): Block height (number) or block hash (64 hexadecimal characters)

### `get_transaction` (~57 tokens)

Get a transaction

A transaction with confirmations, block time, outputs (amount in DOI and address) and any name operation
    (name_doi, name_update, ...) it contains.

Input parameters:

- `txid` (string, required): Transaction ID, 64 hexadecimal characters

### `get_address` (~99 tokens)

Address balance and history

Confirmed and unconfirmed balance of a Doichain address in DOI, optionally with its most recent
    transactions. Invalid addresses return an error with the reason.

Input parameters:

- `address` (string, required): 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

### `verify_message` (~117 tokens)

Verify a signed 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.

Input parameters:

- `address` (string, required): Legacy Doichain address (M... or N...) that supposedly signed the message
- `message` (string, required): The exact signed text
- `signature` (string, required): Signature in Base64

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/neubuot-doichain/doi-api#diagnostics

## Score history

- 2026-10-04: 77
- 2026-10-03: 76
- 2026-10-02: 76
- 2026-10-01: 75
- 2026-09-30: 75
- 2026-09-29: 74
- 2026-09-28: 74
- 2026-09-27: 73
- 2026-09-26: 74

## Common questions

### 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.

## Links

- Remote endpoint: https://doi-api.sendlabs.de/mcp
- Repository: https://github.com/neubuot/doichain-mcp
- Website: https://doi-api.sendlabs.de/mcp
- Changelog RSS feed: https://verifymcp.io/servers/neubuot-doichain/doi-api.xml
- Changelog JSON feed: https://verifymcp.io/servers/neubuot-doichain/doi-api.json
- HTML version of this page: https://verifymcp.io/servers/neubuot-doichain/doi-api