Skip to content

CBROS Cardano NFT Minter

by coudrebros.eu · remote · no sign-in to list tools · v1.1.0 · published by eu.coudrebros

Pay-and-mint Cardano NFT (CIP-25) in one atomic tx. Non-custodial. MCP-native. Mainnet.

Final · 1Changes · 3
CompareRegistry entry

6 tools: 1 do something that can't be undone, 3 change things and 2 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http nft-minting https://nftapi.coudrebros.eu/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

6 tools

Can't be undone 1Claude Code: ask
  • prepare_paymentBuild an unsigned transaction that pays the mint fee from from_address to the operator, with change returned to from_address.No findings

    Why it is in this group

    • The name "prepare_payment" says "payment": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    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. Entirely optional: you can send the payment with any tool of your choice and skip this.
Changes things 3Claude Code: ask
  • mintMint 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).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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 never stores files. Each payment transaction hash can only be used once -- a failed mint attempt does not consume it, retry with the same payment_tx. You are solely responsible for the content referenced by ipfs_hash.
  • prepare_atomic_mintBuild 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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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 two witnesses (minting policy + its own fee-covering input) before returning the transaction -- inspect it before signing. You then add your own witness for from_address and submit: sign partially_signed_tx directly (cardano-cli 'transaction sign --tx-file <this> --signing-key-file <your key>', or a CIP-30 wallet's signTx(_, true) then merge the witness) and submit it yourself -- this server cannot sign or submit on your behalf. Pin your asset to IPFS yourself first. You are solely responsible for the content referenced by ipfs_hash.
  • registerRegister a new API key by paying a one-time fee.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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 hash. The payment must already be CONFIRMED on-chain (wait ~20-30s after submitting, or check with check_payment_status). One active key per address -- registering twice with the same address fails. Each payment transaction can only be used once, for registration or for a mint, not both.
Only reads 2Claude Code: allow
  • check_payment_statusCheck whether a payment transaction is confirmed on-chain yet.No findings

    Why it is in this group

    • The name "check_payment_status" says "status": a word for reading.
    Description, as the server wrote it
    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.
  • get_server_infoEverything you need before your first call: where to send ADA, and how much.No findings

    Why it is in this group

    • The name "get_server_info" says "get": a word for reading.
    Description, as the server wrote it
    Everything you need before your first call: where to send ADA, and how much. No API key required -- call this first, before 'register'.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http nft-minting https://nftapi.coudrebros.eu/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__nft-minting__get_server_info",
      "mcp__nft-minting__check_payment_status"
    ],
    "ask": [
      "mcp__nft-minting__register",
      "mcp__nft-minting__prepare_payment",
      "mcp__nft-minting__mint",
      "mcp__nft-minting__prepare_atomic_mint"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as nft-minting. Review it before you use it.