MCP server for local transaction signing on EVM, UTXO, Tron, and XRP — no API calls needed
Most payments and commerce work still happens through a UI a human drives. Cryptoapis MCP Signer MCP server moves it into the conversation instead. MCP server for local transaction signing on EVM, UTXO, Tron, and XRP — no API calls needed.
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.
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 server publishes 7 tools. What each one is for:
Cursor — The Cursor tool exposed by this serverevm_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 serverkaspa_sign — Sign a Kaspa transaction using schnorr (BIP340) via kaspa-wasm. Mainnet onlysvm_sign — Partial-sign a Solana (SVM) x402 payment transaction — the buyer's source-authority signature only (the facilitator's feePayer slot stays unsignedAmong the payments and commerce options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Cryptoapis MCP Signer's toolset — Cursor, evm_sign, utxo_sign and 4 more — is a fair guide to whether it matches your workflow. It is maintained by cryptoapis-io; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Cryptoapis MCP Signer's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| 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, signed at settle). |
{
"mcpServers": {
"cryptoapis-mcp-signer": {
"command": "npx",
"args": ["-y", "@cryptoapis-io/mcp-signer"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Payments infrastructure meets AI — customers, invoices, subscriptions and current API docs from Stripe's server.
Build for Shopify with current APIs — the official Dev MCP server for schema-accurate storefront and admin code.
Give your AI assistant a supervised window into your Interactive Brokers account — balances, positions, live quotes and orders.
Invoices, payments and disputes through PayPal's official server — commerce operations by conversation.
Enables querying and listing Azure resources and costs directly from an MCP client.
Empowers LLMs with Bitcoin Lightning Network payment capabilities via the ZBD API.