get_notary_info
No auth needed. Price, min confirmations, spec version, and supported hash algorithms.
Takes no parameters.
CBROS Notary & Decision Log
eu.coudrebrosPublished by coudrebros.euOfficial publisherv1.0.0Updated Oct 28, 2026
Pay-and-anchor a hash or AI decision log on Cardano (CIP-0190). Non-custodial. MCP-native. Mainnet.
The publisher's own server: CBROS Cardano NFT Minter
Overview
AI-generated overview
Remote MCP server that lets an assistant anchor hashes and hash-chained AI decision logs on Cardano mainnet and verify them on-chain.
- What you can do
- Read notary parameters: price, confirmation depth, spec version and supported hash algorithms
- Prepare anchors: build a partially-signed Cardano transaction for a content hash, with optional idempotency key
- Prepare decision-log entries: append a hash-chained record with sequence number and previous hash
- Check status: look up a prepared anchor or log entry by proof ID using the API key that created it
- Verify proofs: authoritative on-chain check by transaction hash and/or content hash, optionally re-hashing supplied content
- Verify chains: independently check a decision log's integrity from chain data alone
- When to use it
- Useful when an assistant or agent needs a timestamped, publicly verifiable proof that a document hash or a sequence of AI decisions existed at a point in time, and when third parties should be able to verify it without trusting the operator.
- Requirements
- A remote streamable HTTP endpoint; no authentication is declared for the read and verify tools. Anchoring uses Cardano mainnet, so you need a Cardano wallet to sign and submit the returned partially-signed transactions and real ADA to pay the fee. An API key is needed to check the status of anchors you created. Hashes must be computed client-side (sha2-256 or blake2b-256).
Before you install
This deployment writes to Cardano mainnet and spends real ADA; the server does not sign or submit for you, so you handle your own keys and transactions. Only hashes and minimal metadata should be sent, never the underlying content. An API key is required to look up your own anchors. The server states that a record is a timestamped verifiable hash, not a legally binding attestation, and that use is subject to its Legal Notice and Privacy Policy.
Installation
In SourceWeft
- Open CBROS Notary & Decision Log in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/eu.coudrebros%2Fnotary/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"cbros-notary-decision-log": {
"type": "http",
"url": "https://nftapi.coudrebros.eu/mcp/notary/"
}
}
}Tools
6prepare_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.
Parameters
api_keyrequiredalgorithmcontent_hashrequiredfrom_addressrequiredidempotency_keyprepare_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 content_hash (omit only for seq=0). Returns a partially-signed transaction to sign and submit yourself.
Parameters
seqrequiredprevapi_keyrequiredalgorithmcontent_hashrequiredfrom_addressrequiredidempotency_keycheck_anchor_status
Looks up a previously prepared anchor or decision-log entry by proof_id. Requires the api_key that created it.
Parameters
api_keyrequiredproof_idrequiredverify_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).
Parameters
contenttx_hashcontent_hashverify_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.
Parameters
agent_refrequiredVersion history
1- v1.0.0LatestOct 26, 2026
Score
83% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.