CBROS Notary & Decision Log

Reliability

Status and outage history · Atom feed · Watch with other listings

How to connect

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "cbros-notary-decision-log": {
      "type": "http",
      "url": "https://nftapi.coudrebros.eu/mcp/notary/"
    }
  }
}

6 tools

• get_notary_info

  No auth needed. Price, min confirmations, spec version, and supported hash algorithms.

• prepare_anchor

  Anchors content_hash on chain. Returns a partially-signed transaction (operator co-signed its fee input) -- add your own witness for from_address and submit. idempotency_key (optional) returns the same prior result on retry instead of building a new transaction.

• prepare_decision_log

  Appends one entry to your hash-chained decision log. content_hash is the hash of your own RFC-8785-canonicalized decision record (never send the record itself -- see docs/decision-record-v1.md). seq starts at 0 and increments by 1 each call; prev must equal the previous entry's…

• check_anchor_status

  Looks up a previously prepared anchor or decision-log entry by proof_id. Requires the api_key that created it.

• verify_proof

  Authoritative on-chain check by tx_hash (and/or content_hash to compare against). No auth needed -- anyone holding a tx hash can verify it, like a receipt. Optionally pass content to re-hash locally server-side (never stored/logged).

• verify_decision_chain

  Independently checks a decision-log chain's integrity from chain data alone (gap-free seq, prev matches, each entry anchored). No auth needed.

Security scan

Recent checks