CBROS Notary & Decision Log
eu.coudrebros/notary · v1.0.0 · MCP 2026-07-28
Pay-and-anchor a hash or AI decision log on Cardano (CIP-0190). Non-custodial. MCP-native. Mainnet.
Reachability
reachable
checked 2026-10-26 05:30 UTC
Registry status active
Tools pinned 6
15cd2cc2bee9
Tools last changed
unchanged since first capture 2026-10-26
Provenance
Registry namespace eu.coudrebros
(domain verified by the official registry)
Remote endpoints
https://nftapi.coudrebros.eu/mcp/notary/ (streamable-http)
Observed changes
| When (UTC) | Event | Detail |
|---|---|---|
| 2026-10-26 05:30 | first capture | 6 tools pinned |
Pinned tool definitions (6)
| Tool | Description |
|---|---|
| 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... |
| 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... |
| 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. |
Get alerted when this changes.
Email the moment eu.coudrebros/notary drifts, dies, or revives.
Status badge
[](https://toolpin.dev/servers/eu.coudrebros/notary)
Maintain this server? Add the badge to your README. It links your users to this live status page.