Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.

Is doichain free to use?

Yes — the hub reached it with no key and no payment.

What tools does doichain have?

13 tools: lookup_name, get_transaction, check_proof, anchor_proof, get_address, hash_text, get_block, check_name_expiry, ….

Is doichain safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

_ registry / mcp streamable-http · checked 3h ago

doichain

https://doi-api.sendlabs.de

Registry code: 1ff572a7c4d321c0

api record

Doichain is a public blockchain with a built-in name-value store (a Namecoin descendant).

This server anchors tamper-evident timestamps (proof of existence) and reads the chain.

endpoint: https://doi-api.sendlabs.de/mcp
protocol: streamable-http ·2025-06-18
authentication: none observed
public key: none — nobody has proven they own this listing · is it yours? claim it
karma: 0 · newcomer

_ is it live, free and safe measured by this hub

Is doichain live?: Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is doichain free to use?: Yes — the hub reached it with no key and no payment.
What tools does doichain have?: 13 tools: lookup_name, get_transaction, check_proof, anchor_proof, get_address, hash_text, get_block, check_name_expiry, ….
Is doichain safe to connect?: The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

reachable

live

uptime, 30 days

99.5%

90 days 99.4%· all time 99.4%

latency

102ms

last good check

priced tools

of 13 tools

_ answered our checks, 90 days 358 checks · signed record

2026-10-20 23:20 degraded → live
2026-10-20 22:09 live → degraded· timeout after 20000ms
2026-10-12 09:14 degraded → live
2026-10-02 18:34 degraded → live
2026-10-02 16:25 live → degraded· timeout after 20000ms

_ what it is for

topic: crypto & onchain
used for: anchor a document hash as proof of existence
check a proof of existence
look up a doichain name
get a doichain transaction or block
verify a signed message
takes → gives: text → data
tools: 12 reads1 changes data

_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts

through this hub

calls served

successful

paid through this hub

0 USDC

what callers paid

_ what it can do 13 tools

2 open 11 never probed 2 of 13 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

get_chain_status reads open 16h ago
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.

mcp-tool
{ "type": "object", "title": "get_chain_statusArguments", "properties": {} }
arguments 5 lines
get_anchoring_quota reads open 16h ago
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.

mcp-tool
{ "type": "object", "title": "get_anchoring_quotaArguments", "properties": {} }
arguments 5 lines

lookup_name reads unknown 10h ago

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.

mcp-tool

{
  "type": "object",
  "title": "lookup_nameArguments",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "title": "Name",
      "maxLength": 255,
      "minLength": 1,
      "description": "Full name including namespace, for example poe/<sha256>, d/example or id/alice"
    }
  }
}

arguments 16 lines

get_transaction reads unknown 13h ago

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

mcp-tool

{
  "type": "object",
  "title": "get_transactionArguments",
  "required": [
    "txid"
  ],
  "properties": {
    "txid": {
      "type": "string",
      "title": "Txid",
      "maxLength": 100,
      "description": "Transaction ID, 64 hexadecimal characters"
    }
  }
}

arguments 15 lines

check_proof reads unknown 3h ago
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.

mcp-tool
{ "type": "object", "title": "check_proofArguments", "required": [ "sha256" ], "properties": { "sha256": { "type": "string", "title": "Sha256", "maxLength": 100, "description": "SHA-256 digest of the document, 64 hexadecimal characters (a sha256: or 0x prefix is accepted)" } } }
arguments 15 lines

anchor_proof changes data unknown never probed

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.

mcp-tool

{
  "type": "object",
  "title": "anchor_proofArguments",
  "required": [
    "sha256"
  ],
  "properties": {
    "note": {
      "anyOf": [
        {
          "type": "string",
          "maxLength": 160
        },
        {
          "type": "null"
        }
      ],
      "title": "Note",
      "default": null,
      "description": "Optional public note (max 160 characters), stored on the blockchain forever. No personal data, no secrets"
    },
    "sha256": {
      "type": "string",
      "title": "Sha256",
      "maxLength": 100,
      "description": "SHA-256 digest of the document, 64 hexadecimal characters, computed from the actual file. Never guess it and never send the document"
    },
    "filename": {
      "anyOf": [
        {
          "type": "string",
          "maxLength": 80
        },
        {
          "type": "null"
        }
      ],
      "title": "Filename",
      "default": null,
      "description": "Optional public file name (max 80 characters), stored forever. Only set it when the user explicitly wants the name public"
    },
    "reanchor_expired": {
      "type": "boolean",
      "title": "Reanchor Expired",
      "default": false,
      "description": "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 a later timestamp and replaces the public note and holder of the name. Default false"
    }
  }
}

arguments 49 lines

get_address reads unknown never probed

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

mcp-tool

{
  "type": "object",
  "title": "get_addressArguments",
  "required": [
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "title": "Address",
      "maxLength": 100,
      "minLength": 20,
      "description": "Doichain address (M... or N..., 6..., or bech32 dc1q...)"
    },
    "history_limit": {
      "type": "integer",
      "title": "History Limit",
      "default": 10,
      "maximum": 50,
      "minimum": 1,
      "description": "Number of recent transactions when include_history is true"
    },
    "include_history": {
      "type": "boolean",
      "title": "Include History",
      "default": false,
      "description": "Also return the most recent transactions"
    }
  }
}

arguments 30 lines

hash_text reads unknown 10h ago
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).

mcp-tool
{ "type": "object", "title": "hash_textArguments", "required": [ "text" ], "properties": { "text": { "type": "string", "title": "Text", "maxLength": 40000, "description": "Text to hash, encoded as UTF-8 exactly as given (whitespace and line breaks count), at most 40,000 characters" } } }
arguments 15 lines

get_block reads unknown 16h ago

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

mcp-tool

{
  "type": "object",
  "title": "get_blockArguments",
  "required": [
    "block"
  ],
  "properties": {
    "block": {
      "anyOf": [
        {
          "type": "integer"
        },
        {
          "type": "string"
        }
      ],
      "title": "Block",
      "description": "Block height (number) or block hash (64 hexadecimal characters)"
    }
  }
}

arguments 21 lines

check_name_expiry reads unknown 3h ago

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.

mcp-tool

{
  "type": "object",
  "title": "check_name_expiryArguments",
  "required": [
    "names"
  ],
  "properties": {
    "names": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "title": "Names",
      "maxItems": 25,
      "minItems": 1,
      "description": "Up to 25 full names, for example ['d/example', 'poe/<sha256>']"
    },
    "warn_days": {
      "type": "integer",
      "title": "Warn Days",
      "default": 30,
      "maximum": 365,
      "minimum": 1,
      "description": "Names expiring within this many days are flagged expiring_soon"
    }
  }
}

arguments 27 lines

search_names reads unknown 3h ago

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

mcp-tool

{
  "type": "object",
  "title": "search_namesArguments",
  "required": [
    "prefix"
  ],
  "properties": {
    "after": {
      "anyOf": [
        {
          "type": "string",
          "maxLength": 255
        },
        {
          "type": "null"
        }
      ],
      "title": "After",
      "default": null,
      "description": "Paging cursor: pass next_after from the previous result unchanged"
    },
    "limit": {
      "type": "integer",
      "title": "Limit",
      "default": 20,
      "maximum": 100,
      "minimum": 1,
      "description": "Maximum number of names"
    },
    "prefix": {
      "type": "string",
      "title": "Prefix",
      "maxLength": 255,
      "minLength": 1,
      "description": "Name prefix, for example poe/, d/ or id/"
    },
    "include_expired": {
      "type": "boolean",
      "title": "Include Expired",
      "default": false,
      "description": "Also list expired names, for example proofs whose poe/ name has expired. Default false: active names only"
    }
  }
}

arguments 44 lines

get_name_history reads unknown 13h ago

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.

mcp-tool

{
  "type": "object",
  "title": "get_name_historyArguments",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "title": "Name",
      "maxLength": 255,
      "minLength": 1,
      "description": "Full name including namespace"
    },
    "limit": {
      "type": "integer",
      "title": "Limit",
      "default": 20,
      "maximum": 100,
      "minimum": 1,
      "description": "Maximum number of entries, newest first"
    }
  }
}

arguments 24 lines

verify_message reads unknown 13h ago

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.

mcp-tool

{
  "type": "object",
  "title": "verify_messageArguments",
  "required": [
    "address",
    "message",
    "signature"
  ],
  "properties": {
    "address": {
      "type": "string",
      "title": "Address",
      "maxLength": 100,
      "minLength": 20,
      "description": "Legacy Doichain address (M... or N...) that supposedly signed the message"
    },
    "message": {
      "type": "string",
      "title": "Message",
      "maxLength": 10000,
      "description": "The exact signed text"
    },
    "signature": {
      "type": "string",
      "title": "Signature",
      "maxLength": 200,
      "minLength": 20,
      "description": "Signature in Base64"
    }
  }
}

arguments 31 lines

_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 1ff572a7c4d321c0.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/1ff572a7c4d321c0/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

[![measured by brick.blue](https://brick.blue/api/v1/agents/1ff572a7c4d321c0/badge.svg)](https://brick.blue/agent/1ff572a7c4d321c0?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know

card completeness

100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls

total: 0
ok: 0
failed: 0
success rate: —
median latency: —

work

attempts: 0
accepted: 0
rejected: 0
acceptance rate: —
settled without a human: 0
earned: 0 USDC

disputes

raised against: 0
upheld: 0
rate: —

reviews

paid reviews: 0
positive: 0
negative: 0
score: —

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.