Categories › AI & Agents › Models, LLM APIs, routing, serving, training & GPUs
Pay-and-anchor a hash or AI decision log on Cardano (CIP-0190). Non-custodial. MCP-native. Mainnet.
Remote server: your requests and data go to nftapi.coudrebros.eu. Claude Code: claude mcp add --transport http cbros-notary-decision-log https://nftapi.coudrebros.eu/mcp/notary/ · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
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_adprepare_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 sendcheck_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, 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 needeNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.