
This server handles local transaction signing for EVM chains (Ethereum, BSC, Polygon, Arbitrum, Base, Optimism), UTXO chains (Bitcoin, Litecoin, Dogecoin), Tron, and XRP without making any network calls. You pass private keys directly to tools like evm_sign, utxo_sign, tron_sign, and xrp_sign, which return signed transaction hex strings ready for broadcast. Each tool supports either signing from structured fields (to, value, gasLimit) or from pre-built unsigned hex. Runs stdio only with no HTTP transport, so nothing listens on a port. Pair it with the mcp-broadcast server to push signed transactions to the blockchain. Good fit when you need offline signing across multiple chains in Claude workflows.
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.
privateKey / privateKeys / secret as parameters. Keys are never read from environment variables.npm install @cryptoapis-io/mcp-signer
Or install all Crypto APIs MCP servers: npm install @cryptoapis-io/mcp
npx @cryptoapis-io/mcp-signer
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows):
{
"mcpServers": {
"cryptoapis-signer": {
"command": "npx",
"args": ["-y", "@cryptoapis-io/mcp-signer"]
}
}
}
Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):
{
"mcpServers": {
"cryptoapis-signer": {
"command": "npx",
"args": ["-y", "@cryptoapis-io/mcp-signer"]
}
}
}
npx @modelcontextprotocol/inspector npx @cryptoapis-io/mcp-signer
evm_signSign an EVM transaction (Ethereum, Ethereum Classic, BSC, Polygon, Avalanche (C-Chain), Arbitrum, Base, Optimism, Tron).
| Action | Description |
|---|---|
sign-from-details | Sign from structured transaction fields (to, value, gasLimit, etc.) |
sign-unsigned-hex | Sign a pre-built unsigned transaction hex |
sign-typed-data | Sign an EIP-712 typed-data message (the x402 gasless path — e.g. the EIP-3009 TransferWithAuthorization from the x402 buyer /authorize). Returns { signature }, not a tx. |
utxo_signSign a UTXO transaction (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash).
| Action | Description |
|---|---|
sign-from-details | Sign from a prepared transaction object (inputs, outputs) |
sign-unsigned-hex | Sign a raw unsigned transaction hex with input descriptors |
tron_signSign a Tron transaction using secp256k1 (no TronWeb dependency).
| Action | Description |
|---|---|
sign-from-details | Sign from a transaction object with raw_data_hex |
sign-unsigned-hex | Sign a pre-built unsigned transaction hex |
xrp_signSign an XRP transaction.
| Action | Description |
|---|---|
sign-from-details | Sign from structured XRP transaction fields |
sign-unsigned-hex | Sign a pre-built unsigned transaction hex |
kaspa_signSign a Kaspa transaction using schnorr (BIP340) via kaspa-wasm. Mainnet only.
| Action | Description |
|---|---|
sign-from-details | Sign a prepared Kaspa transaction (from the prepare-transaction API) |
svm_signPartial-sign a Solana (SVM) x402 payment transaction — the buyer's source-authority signature only (the facilitator's feePayer slot stays unsigned, signed at settle).
| Action | Description |
|---|---|
partial-sign | Deserialize the base64 unsigned TransferChecked tx from the x402 buyer /authorize (scheme svm-transaction), add the buyer signature, re-serialize to base64. Returns { transaction }. |
Most tools return signedTransactionHex — ready to broadcast with @cryptoapis-io/mcp-broadcast. The
x402 paths return { signature } (EVM typed-data) or { transaction } (SVM) instead.
| Package | Purpose |
|---|---|
ethers | EVM transaction signing |
bitcoinjs-lib + ecpair + tiny-secp256k1 | UTXO transaction signing |
elliptic | Tron transaction signing (secp256k1) |
xrpl | XRP transaction signing |
MIT