# CBROS Cardano NFT Minter (remote · nftapi.coudrebros.eu)

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

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `nftapi.coudrebros.eu`: 65/100 (this document), [markdown](https://verifymcp.io/servers/eu-coudrebros-nft-minting/nftapi.md), [page](https://verifymcp.io/servers/eu-coudrebros-nft-minting/nftapi)

## Channel facts

- Endpoint: `https://nftapi.coudrebros.eu/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

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

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "eu-coudrebros-nft-minting": {
      "url": "https://nftapi.coudrebros.eu/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "eu-coudrebros-nft-minting": {
      "type": "http",
      "url": "https://nftapi.coudrebros.eu/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.eu-coudrebros-nft-minting]
url = "https://nftapi.coudrebros.eu/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "eu-coudrebros-nft-minting": {
      "type": "remote",
      "url": "https://nftapi.coudrebros.eu/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add eu-coudrebros-nft-minting --url 'https://nftapi.coudrebros.eu/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  eu-coudrebros-nft-minting:
    url: "https://nftapi.coudrebros.eu/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "eu-coudrebros-nft-minting": {
      "Transport": "http",
      "Url": "https://nftapi.coudrebros.eu/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add eu-coudrebros-nft-minting -t streamable-http -u 'https://nftapi.coudrebros.eu/mcp'
```

### Other

```json
{
  "mcpServers": {
    "eu-coudrebros-nft-minting": {
      "type": "http",
      "url": "https://nftapi.coudrebros.eu/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-18 (score 65, +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.

### 2026-10-17 (score 64, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-16 (score 64)

First indexed and scored.

## MCP tools (6)

### `get_server_info` (~39 tokens)

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

### `register` (~135 tokens)

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.

Input parameters:

- `from_address` (string, required)
- `registration_tx` (string, required)

### `check_payment_status` (~68 tokens)

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.

Input parameters:

- `api_key` (string, required)
- `tx` (string, required)

### `prepare_payment` (~88 tokens)

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.

Input parameters:

- `api_key` (string, required)
- `from_address` (string, required)

### `mint` (~163 tokens)

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.

Input parameters:

- `api_key` (string, required)
- `asset_kind` (string)
- `description` (string)
- `destination_address` (string, required)
- `ipfs_hash` (string, required)
- `ipfs_hash_thumbnail`
- `nft_name` (string, required)
- `payment_tx` (string, required)

### `prepare_atomic_mint` (~239 tokens)

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.

Input parameters:

- `api_key` (string, required)
- `asset_kind` (string)
- `description` (string)
- `destination_address` (string, required)
- `from_address` (string, required)
- `ipfs_hash` (string, required)
- `ipfs_hash_thumbnail`
- `nft_name` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/eu-coudrebros-nft-minting/nftapi#diagnostics

## Score history

- 2026-10-18: 65
- 2026-10-17: 64
- 2026-10-16: 64

## Common questions

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

## Links

- Remote endpoint: https://nftapi.coudrebros.eu/mcp
- Changelog RSS feed: https://verifymcp.io/servers/eu-coudrebros-nft-minting/nftapi.xml
- Changelog JSON feed: https://verifymcp.io/servers/eu-coudrebros-nft-minting/nftapi.json
- HTML version of this page: https://verifymcp.io/servers/eu-coudrebros-nft-minting/nftapi