Skip to content

Releases: neubuot/doichain-mcp

Release list

v1.5.0: fixes from the external review

v1.5.0: fixes from the external review Latest
Latest

Choose a tag to compare

View all tags
@neubuot neubuot released this 27 Sep 12:34
v1.5.0
c53749e

Fixes from an external review by @NiKrause (issues #3 and #4). Requires Doichain REST API 1.5.0 or later for the
expired-hash protection: older APIs ignore the reanchor flag.

Changed

  • Breaking: check_proof no longer mixes two registrations. The top level describes only the first anchoring,
    including its own record (record_untrusted) and, when known, first_owner_address. Holder, record and expiry of
    a later registration are reported in latest_registration with a kind of re-registration after expiry or
    update by the holder. owner_address and expires_in_blocks stay at the top level only for a single registration.
  • Breaking: anchor_proof returns reanchored_expired_proof instead of renewed_expired_proof.
  • An expired hash is no longer registered again silently. anchor_proof returns the existing proof with a hint,
    and only registers again when reanchor_expired=true is passed.
  • Authorization: Bearer is interpreted as a Doichain API key only when DOI_MCP_ACCEPT_BEARER=true (default false).
  • Wording: no more "notary". The server describes what the chain shows, a tamper-evident timestamp proving that a
    document existed no later than the block time, and explains expiry and who holds the anchored names.
  • The 0.01 DOI per name is described as a cost that is lost at expiry, not as a deposit.
  • Workflows pin all actions to commit SHAs.

Added

  • search_names accepts include_expired to list expired names as well, for example old proofs.
  • api() refuses to combine a response cache with keyed requests (cache entries are not separated per caller).

Contributors

NiKrause
Assets 2
Loading

v1.4.1: first public release

v1.4.1: first public release

Choose a tag to compare

View all tags
@neubuot neubuot released this 26 Sep 15:42
v1.4.1
357718a

First public release of the Doichain MCP server, now listed in the official MCP Registry as io.github.neubuot/doichain.

Endpoint: https://doi-api.sendlabs.de/mcp (Streamable HTTP, stateless, no authentication)

claude mcp add --scope user --transport http doichain https://doi-api.sendlabs.de/mcp

Setup for Claude, ChatGPT, Cursor and VS Code: see the README.

What agents can do

  • Anchor the SHA-256 of a document on the Doichain as proof of existence (anchor_proof) and verify it later (check_proof)
  • Look up names, their history and expiry dates for up to 25 names at once
  • Read chain status, blocks, transactions, address balances and verify signed messages

13 tools in total, only anchor_proof writes. Anchoring is free for users within a daily quota (10 per IP address, 200 per day overall).

Highlights of 1.4.1

  • check_proof always reports the first anchoring of a hash
  • Real expiry dates for expired names, estimates for active ones from the measured block interval
  • Chain-originated names and values are marked _untrusted (prompt injection protection)
  • JSON-RPC error responses for rate limits and oversized requests, hardened systemd sandbox
  • Offline test suite, CI on Python 3.11 to 3.13, automated registry publishing via GitHub OIDC

Full list: CHANGELOG.md

Loading