CBROS MCP server

• Registry nameeu.coudrebros/nft-mintingverified in the MCP registry

The registry name sits under coudrebros.eu. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-28
• Tools6
• Server calls itselfcbros-nft-minting
• Server version0.1.0
• Protocol version2025-06-18

On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 668 ms.

• Its tools do let AI agents mint Cardano NFTs autonomously, but not delegate ADA to a Cardano stake pool.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP score79 of 100answers 100 · does the job 50 · definitions 69 · context 100 · connects 100
• What an agent can do with it1 of 2 use cases
• Answered100% of days8 of 8 daily checks
• Median first answer695 ms
• Space in an agent's context≈ 1,199 tokensthe definitions of all its tools (6), which an agent carries on every turn
• Tool definitionsC · 69 of 100
• Typed results0 of 6 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 5 of 6
• Not saying whether it only reads or can destroy: 6 of 6

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• get_server_info

  Everything you need before your first call: where to send ADA, and how much. No API key required -- call this first, before 'register'.

• register

  Register a new API key by paying a one-time fee. Pay the registration fee (see get_server_info) from the Cardano address you want your key bound to, sending it to the operator's payment_address, then call this with that transaction's…

• check_payment_status

  Check whether a payment transaction is confirmed on-chain yet. Poll this after paying and before calling 'register', 'mint', or trusting a payment_tx you're about to reference -- submitting a transaction does not mean it is confirmed.

• prepare_payment

  Build an unsigned transaction that pays the mint fee from from_address to the operator, with change returned to from_address. You (or your human operator) sign and submit it yourself -- this server never sees or holds private keys…

• mint

  Mint an NFT after separately paying the mint fee (see prepare_payment or pay any other way, then wait for on-chain confirmation -- check_payment_status). Pin your asset (and a thumbnail, for video) to IPFS yourself first; this server…

• prepare_atomic_mint

  Build a single transaction that pays the mint fee from from_address AND mints the NFT to destination_address at the same time -- no separate payment step, no payment_tx. Either both happen or neither does. The operator co-signs its own…

• eu.coudrebros/notaryanswers, 6 toolsverified in the MCP registry