MCP server for local transaction signing on EVM, UTXO, Tron, and XRP — no API calls needed
MCPpedia last refreshed this data
Signer MCP Server is an MCP server that MCP server for local transaction signing on EVM, UTXO, Tron, and XRP — no API calls needed. Its tool list has not been published yet over stdio and http, requires no API key, and scores 87/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"cryptoapis-signer": {
"args": [
"-y",
"@cryptoapis-io/mcp-signer"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
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.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@cryptoapis-io/mcp-signer' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked @cryptoapis-io/mcp-signer against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in finance
Real-time financial market data: stocks, forex, crypto, commodities, and economic indicators
MCP server for QuickBooks Online — accounts, customers, invoices, bills, and reports.
HoneyBook client-portal MCP server for Claude — view contracts and invoices from wedding vendors
Self-custody Ethereum agent wallet (MCP/stdio). Keys stay in a local Docker volume.
MCP Security Weekly
Get CVE alerts and security updates for Signer MCP Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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