MCP server for local transaction signing on EVM, UTXO, Tron, and XRP — no API calls needed
MCP server for local transaction signing on EVM, UTXO, Tron, and XRP — no API calls needed
Is it safe?
No known CVEs for @cryptoapis-io/mcp-signer.
No authentication — any process on your machine can connect to this server.
License not specified.
Last scanned 0 days ago.
Is it maintained?
Last commit 20 days ago.
Will it work with my client?
Transport: stdio, http. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
How much context will it use?
0 tools. Token cost not measured.
What if it doesn't work?
Common issues: JSON syntax errors in config, wrong Node.js version, npx cache, network or firewall blocking. Setup guide covers troubleshooting.
{
"mcpServers": {
"cryptoapis-signer": {
"args": [
"-y",
"@cryptoapis-io/mcp-signer"
],
"command": "npx"
}
}
}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:
Last scanned 2h ago
No known vulnerabilities.
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.