MCP server for local transaction signing on EVM, UTXO, Tron, and XRP — no API calls needed
npx -y @cryptoapis-io/mcp-signerAdd this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"io-github-cryptoapis-io-mcp-signer": {
"command": "npx",
"args": [
"-y",
"@cryptoapis-io/mcp-signer"
]
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
mcp-signer is an MCP server for MCP server for local transaction signing on EVM, UTXO, Tron, and XRP — no API calls needed. It supports STDIO transport.
Use the generated config in Install. This server runs with npx -y @cryptoapis-io/mcp-signer; add any required environment variables before starting your client.
Choose the Claude Desktop tab in Install and copy the config for npx -y @cryptoapis-io/mcp-signer. Add required environment variables before starting Claude Desktop.
Choose the Claude Code tab in Install and copy the config for npx -y @cryptoapis-io/mcp-signer. Add required environment variables before starting Claude Code.
Choose the Codex tab in Install and copy the config for npx -y @cryptoapis-io/mcp-signer. Add required environment variables before starting Codex.
Choose the Cursor or VS Code tab in Install and copy the config for npx -y @cryptoapis-io/mcp-signer. Add required environment variables before starting Cursor or VS Code.
mcp-signer uses STDIO transport. Use the package or command config in Install.
mcp-signer inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
mcp-signer does not advertise a verified auth requirement. If discovery fails, it may still need provider login, an API key, a bearer token, or a session header.
| Package | Registry | Version | Inputs |
|---|---|---|---|
@cryptoapis-io/mcp-signerstdio | npm | 0.3.0 | None advertised |