Cryptoapis MCP Signer MCP Server

MCP server for local transaction signing on EVM, UTXO, Tron, and XRP — no API calls needed

Local serverstdio

What is the Cryptoapis MCP Signer MCP Server?

MCP server for local transaction signing on EVM, UTXO, Tron, and XRP — no API calls needed

The short version

MCP server for local transaction signing across EVM, UTXO, Tron, and XRP blockchains. No Crypto APIs HTTP calls — signing happens entirely on your machine. No API key required.

Getting it running

Installation goes through your MCP client rather than a global install: point it at @cryptoapis-io/mcp-signer on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

The tools it exposes

The server publishes 7 tools. What each one is for:

  • Cursor — The Cursor tool exposed by this server
  • evm_sign — Sign an EVM transaction (Ethereum, Ethereum Classic, BSC, Polygon, Avalanche (C-Chain), Arbitrum, Base, Optimism, Tron)
  • utxo_sign — Sign a UTXO transaction (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash)
  • tron_sign — Sign a Tron transaction using secp256k1 (no TronWeb dependency)
  • xrp_sign — The xrp_sign tool exposed by this server
  • kaspa_sign — Sign a Kaspa transaction using schnorr (BIP340) via kaspa-wasm. Mainnet only
  • svm_sign — Partial-sign a Solana (SVM) x402 payment transaction — the buyer's source-authority signature only (the facilitator's feePayer slot stays unsigned

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Recorded tools

  • evm_sign — Sign an EVM transaction (Ethereum, Ethereum Classic, BSC, Polygon, Avalanche (C-Chain), Arbitrum, Base, Optimism, Tron).
  • utxo_sign — Sign a UTXO transaction (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash).
  • tron_sign — Sign a Tron transaction using secp256k1 (no TronWeb dependency).
  • xrp_sign — The xrp_sign tool exposed by this server.
  • kaspa_sign — Sign a Kaspa transaction using schnorr (BIP340) via kaspa-wasm. Mainnet only.
  • svm_sign — Partial-sign a Solana (SVM) x402 payment transaction — the buyer's source-authority signature only (the facilitator's feePayer slot stays unsigned, signed at settle).

More MCP options

Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

ToolWhat it does
ActionDescription
sign-from-detailsSign a prepared Kaspa transaction (from the prepare-transaction API)
sign-unsigned-hexSign a pre-built unsigned transaction hex
sign-typed-dataSign an EIP-712 typed-data message (the x402 gasless path — e.g. the EIP-3009 TransferWithAuthorization from the x402 buyer /authorize). Returns { signature },
partial-signDeserialize the base64 unsigned TransferChecked tx from the x402 buyer /authorize (scheme svm-transaction), add the buyer signature, re-serialize to base64. Ret
sign-forged-operationSign the forgedOperation hex from prepare_transactions_tezos. The operation is decoded first: only reveal/transaction ops from the key's own address are signed,
evm_sign
utxo_sign
tron_sign
xrp_sign
kaspa_sign
svm_sign
tezos_sign

How to install the Cryptoapis MCP Signer MCP Server

{
  "mcpServers": {
    "cryptoapis-signer": {
      "command": "npx",
      "args": [
        "-y",
        "@cryptoapis-io/mcp-signer"
      ]
    }
  }
}

From the project documentation. Replace placeholders and example paths before connecting.

Example prompts to try

  • “Use Cryptoapis MCP Signer to Cursor.”
  • “Use Cryptoapis MCP Signer to evm sign.”
  • “Use Cryptoapis MCP Signer to utxo sign.”

Frequently asked questions

MCP server for local transaction signing on EVM, UTXO, Tron, and XRP — no API calls needed Confirm the tools offered by your installed version in the connected client. Tool availability and permissions depend on the server and account configuration.