io.github.neubuot/doichain

Est-ce que io.github.neubuot/doichain est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.neubuot/doichain » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 13 outils

• anchor_proof≈ 587 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • note · ? · optionnel
    Optional public note (max 160 characters), stored on the blockchain forever. No personal data, no secrets
  • sha256 · string · requis
    SHA-256 digest of the document, 64 hexadecimal characters, computed from the actual file. Never guess it and never send the document
  • filename · ? · optionnel
    Optional public file name (max 80 characters), stored forever. Only set it when the user explicitly wants the name public
  • reanchor_expired · boolean · optionnel
    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

  Exemple d'appel

  {"name": "anchor_proof", "arguments": {"sha256": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• check_name_expiry≈ 282 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • names · array · requis
    Up to 25 full names, for example ['d/example', 'poe/<sha256>']
  • warn_days · integer · optionnel
    Names expiring within this many days are flagged expiring_soon

  Exemple d'appel

  {"name": "check_name_expiry", "arguments": {"names": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• check_proof≈ 309 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

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

  Exemple d'appel

  {"name": "check_proof", "arguments": {"sha256": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_address≈ 265 tokens

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

  Paramètres, retour & exemple (3)

  Paramètres

  • address · string · requis
    Doichain address (M... or N..., 6..., or bech32 dc1q...)
  • history_limit · integer · optionnel
    Number of recent transactions when include_history is true
  • include_history · boolean · optionnel
    Also return the most recent transactions

  Exemple d'appel

  {"name": "get_address", "arguments": {"address": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_anchoring_quota≈ 170 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_anchoring_quota", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_block≈ 166 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • block · ? · requis
    Block height (number) or block hash (64 hexadecimal characters)

  Exemple d'appel

  {"name": "get_block", "arguments": {"block": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_chain_status≈ 153 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_chain_status", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_name_history≈ 219 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • name · string · requis
    Full name including namespace
  • limit · integer · optionnel
    Maximum number of entries, newest first

  Exemple d'appel

  {"name": "get_name_history", "arguments": {"name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_transaction≈ 169 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • txid · string · requis
    Transaction ID, 64 hexadecimal characters

  Exemple d'appel

  {"name": "get_transaction", "arguments": {"txid": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• hash_text≈ 225 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

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

  Exemple d'appel

  {"name": "hash_text", "arguments": {"text": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• lookup_name≈ 201 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • name · string · requis
    Full name including namespace, for example poe/<sha256>, d/example or id/alice

  Exemple d'appel

  {"name": "lookup_name", "arguments": {"name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_names≈ 377 tokens

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

  Paramètres, retour & exemple (4)

  Paramètres

  • after · ? · optionnel
    Paging cursor: pass next_after from the previous result unchanged
  • limit · integer · optionnel
    Maximum number of names
  • prefix · string · requis
    Name prefix, for example poe/, d/ or id/
  • include_expired · boolean · optionnel
    Also list expired names, for example proofs whose poe/ name has expired. Default false: active names only

  Exemple d'appel

  {"name": "search_names", "arguments": {"prefix": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• verify_message≈ 285 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • address · string · requis
    Legacy Doichain address (M... or N...) that supposedly signed the message
  • message · string · requis
    The exact signed text
  • signature · string · requis
    Signature in Base64

  Exemple d'appel

  {"name": "verify_message", "arguments": {"address": "texte", "message": "texte", "signature": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://doi-api.sendlabs.de/mcp