CBROS Cardano NFT Minter

eu.coudrebrosPublished by coudrebros.euOfficial publisherv1.1.0Updated Oct 26, 2026

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

VerifiedStreamable HTTPWeb executableFinanceMedia & Design

Overview

AI-generated overview

Remote MCP server that lets an assistant mint CIP-25 NFTs on the Cardano mainnet, paying fees in ADA and building transactions the user signs.

What you can do
  • Read server info: get the operator's payment address and current fee amounts before any other call.
  • Build payments: create an unsigned ADA transaction paying the mint or registration fee, with change returned to the sender.
  • Verify payments: poll a transaction hash to confirm it is on-chain before registering or minting.
  • Register an API key: bind a key to a Cardano address by referencing a confirmed registration-fee payment.
  • Mint NFTs: mint a CIP-25 token after a separately confirmed mint-fee payment, using assets the user has already pinned to IPFS.
  • Atomic mint: build one transaction that pays the fee and mints to a destination address in a single step.
When to use it
Use it when you want an assistant to help create Cardano mainnet NFTs, especially when you prefer a non-custodial flow where you sign and submit transactions yourself and keep your own IPFS pinning.
Requirements
A remote endpoint at nftapi.coudrebros.eu over streamable HTTP; no API key is needed to start, but an API key must be registered by paying a one-time fee in ADA. A Cardano mainnet wallet with ADA for fees and transaction signing, plus your own IPFS pinning for the asset and thumbnail.
Before you install
Every action costs real ADA on mainnet: a one-time registration fee and a per-mint fee sent to the operator's payment address. Payments are on-chain and irreversible, and each payment transaction hash can be used only once. The server never holds private keys, so you sign and submit transactions yourself; verify confirmation with check_payment_status before relying on a hash. Files are not stored by the server, so you must pin assets to IPFS yourself.

Installation

In SourceWeft

  1. Open CBROS Cardano NFT Minter in the dashboard and add it to a workspace.
  2. 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%2Fnft-minting/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "cbros-cardano-nft-minter": {
      "type": "http",
      "url": "https://nftapi.coudrebros.eu/mcp"
    }
  }
}

Tools

6

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'.

Takes no parameters.

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 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.

Parametersfrom_addressrequiredregistration_txrequired

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.

Parameterstxrequiredapi_keyrequired

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. Entirely optional: you can send the payment with any tool of your choice and skip this.

Parametersapi_keyrequiredfrom_addressrequired

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 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.

Parametersapi_keyrequirednft_namerequiredipfs_hashrequiredasset_kindpayment_txrequireddescriptiondestination_addressrequiredipfs_hash_thumbnail

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 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.

Parametersapi_keyrequirednft_namerequiredipfs_hashrequiredasset_kinddescriptionfrom_addressrequireddestination_addressrequiredipfs_hash_thumbnail

Version history

1
  1. v1.1.0LatestOct 16, 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.

Other Coudrebros integrations

CBROS Notary & Decision Log

eu.coudrebrosOfficial publisher

Remote MCP server that lets an assistant anchor hashes and hash-chained AI decision logs on Cardano mainnet and verify them on-chain.

Streamable HTTPWeb executable
Finance6 toolsOct 28, 2026