CBROS Cardano NFT Minter
REMOTE · NFTAPI.COUDREBROS.EU
Pay-and-mint Cardano NFT (CIP-25) in one atomic tx. Non-custodial. MCP-native. Mainnet.
Available components
Last scanned (9 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1132 tokens (~161/item across 7 items; 6 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 16 Oct 26 64
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Probed https://nftapi.coudrebros.eu/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=nftapi.coudrebros.eu | CN=YE1,O=Let's Encrypt,C=US | 11 Oct 2026 | 9 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 52e056493b1ec8cc2b3c3a0472883ba31c8 |
| SANs: nftapi.coudrebros.eu | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of nftapi.coudrebros.eu. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| eu. | present | 35926 | 8 | Verified |
| coudrebros.eu. | present | 32139 | 10 | Verified |
| nftapi.coudrebros.eu. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | default-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://nftapi.coudrebros.eu/mcp | Verified | 200 | |
| http (plaintext) | http://nftapi.coudrebros.eu/mcp | HTTPS enforced | 301 | https://nftapi.coudrebros.eu/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_payment_status ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | – |
| tx | string | yes | – |
No output schema declared.
No examples provided.
get_server_info ~39
Everything you need before your first call: where to send ADA, and how much. No API key required -- call this first, before 'register'.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mint ~163
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | – |
| asset_kind | string | – | – |
| description | string | – | – |
| destination_address | string | yes | – |
| ipfs_hash | string | yes | – |
| ipfs_hash_thumbnail | – | – | – |
| nft_name | string | yes | – |
| payment_tx | string | yes | – |
No output schema declared.
No examples provided.
prepare_atomic_mint ~239
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | – |
| asset_kind | string | – | – |
| description | string | – | – |
| destination_address | string | yes | – |
| from_address | string | yes | – |
| ipfs_hash | string | yes | – |
| ipfs_hash_thumbnail | – | – | – |
| nft_name | string | yes | – |
No output schema declared.
No examples provided.
prepare_payment ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | – |
| from_address | string | yes | – |
No output schema declared.
No examples provided.
register ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from_address | string | yes | – |
| registration_tx | string | yes | – |
No output schema declared.
No examples provided.
How do I install the CBROS Cardano NFT Minter MCP server?
CBROS Cardano NFT Minter is a hosted endpoint at https://nftapi.coudrebros.eu/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · nftapi.coudrebros.eu
claude mcp add --transport http eu-coudrebros-nft-minting 'https://nftapi.coudrebros.eu/mcp'
What is the CBROS Cardano NFT Minter MCP server?
CBROS Cardano NFT Minter is an MCP server listed in the public MCP registry as eu.coudrebros/nft-minting. Pay-and-mint Cardano NFT (CIP-25) in one atomic tx. Non-custodial. MCP-native. Mainnet. This page covers its hosted endpoint (https://nftapi.coudrebros.eu/mcp).
Is the CBROS Cardano NFT Minter MCP server safe to use?
CBROS Cardano NFT Minter scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the CBROS Cardano NFT Minter MCP server expose?
CBROS Cardano NFT Minter exposes 6 tools: get_server_info, register, check_payment_status, prepare_payment, mint, prepare_atomic_mint. Their descriptions and schemas cost roughly 732 tokens of context every time the server is loaded.
Does the CBROS Cardano NFT Minter MCP server require authentication?
No. We connected to CBROS Cardano NFT Minter without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CBROS Cardano NFT Minter MCP server still maintained?
CBROS Cardano NFT Minter is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.