cardano-mcp-transactions

Sign and submit pre-built unsigned transactions through a configured cardano MCP server. This is a high-risk operation — the MCP server has no server-side approval gate and will sign+submit any CBOR passed to it. Safety depends entirely on the preview-confirm flow defined below.

When to use

• User has a pre-built unsigned transaction (CBOR hex) from a dApp API, MeshTxBuilder, or cardano-cli transaction build.
• User wants to sign and submit that transaction via their MCP-configured wallet.
• A configured cardano MCP server is available.

When NOT to use

• User needs to build a transaction — use cardano-cli-transactions, meshjs-cardano, or koios-agent-wallet. The MCP server cannot construct transactions.
• No cardano MCP server is configured — use koios-agent-wallet (sign-submit mode) or cardano-cli transaction sign + submit.
• User needs testnet submission — current integration assumes mainnet unless testnet support is explicitly validated.
• The transaction CBOR cannot be summarized — refuse to submit (see operating rules).

Operating rules (MUST follow — no exceptions)