Search / eu.coudrebros/nft-minting
protogridR0· no sign-inPay-and-mint Cardano NFT (CIP-25) in one atomic tx. Non-custodial. MCP-native. Mainnet.
v1.1.0 · active · descriptor JSON · versions
{
"mcpServers": {
"nft-minting": {
"type": "http",
"url": "https://nftapi.coudrebros.eu/mcp"
}
}
}claude mcp add --transport http nft-minting https://nftapi.coudrebros.eu/mcp[mcp_servers.nft-minting]
url = "https://nftapi.coudrebros.eu/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nft-minting": {
"type": "remote",
"url": "https://nftapi.coudrebros.eu/mcp",
"enabled": true
}
}
}{
"mcpServers": {
"nft-minting": {
"type": "http",
"url": "https://nftapi.coudrebros.eu/mcp"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=nft-minting&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vbmZ0YXBpLmNvdWRyZWJyb3MuZXUvbWNwIn0%3D"
}{
"servers": {
"nft-minting": {
"type": "http",
"url": "https://nftapi.coudrebros.eu/mcp"
}
}
}{
"mcpServers": {
"nft-minting": {
"httpUrl": "https://nftapi.coudrebros.eu/mcp"
}
}
}extensions:
"nft-minting":
enabled: true
name: "nft-minting"
type: streamable_http
uri: "https://nftapi.coudrebros.eu/mcp"
timeout: 300
protocol.modernsupports 2026-07-28 (server/discover)protocol.statelessanswers without a sessionprotocol.transportstreamable HTTPprotocol.list_ttltools/list declares ttlMs 0, so clients re-fetch it on every useauth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_lengthdescriptions are concisetools.schemasevery tool has an object input schematools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky onestools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: prepare_payment (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); mint (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); prepare_atomic_mint (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …tools.token_costabout 1,138 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changes, stability.rug_pulltool history recorded for 2 of the 7 days neededdeps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI packageNo tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+dns-namespace +reachable +uptime-100% +updated-3d-ago -no-repository
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://nftapi.coudrebros.eu/mcp streamable-http | none | yes | 100% | 997 ms | 2026-07-28 | 2026-10-19 |
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. |
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'. |
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. |
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. |
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. |
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. |
Schemas: list_tools.
{
"name": "eu.coudrebros/nft-minting",
"title": "CBROS Cardano NFT Minter",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://nftapi.coudrebros.eu/mcp",
"type": "streamable-http"
}
],
"version": "1.1.0",
"description": "Pay-and-mint Cardano NFT (CIP-25) in one atomic tx. Non-custodial. MCP-native. Mainnet."
}