@cryptoapis-io/mcp-signer
OfficialRelated Servers
Alternatives to @cryptoapis-io/mcp-signer
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceNon-custodial MCP server that routes blockchain transactions to your browser wallet (MetaMask, Rabby, etc.) for signing — private keys never leave your browser.2MIT
- AlicenseAqualityCmaintenanceMCP server that builds unsigned Paraswap token swap transactions for self-custody wallets, holding no keys and signing nothing. It returns raw transaction data for a human to review and approve before execution.1MIT No Attribution
- AlicenseNot gradedqualityBmaintenanceMCP server for self-custodial wallet infrastructure, enabling secure key generation, Shamir secret sharing, signing, and recovery without exposing private keys to LLMs.9MIT
- AlicenseAqualityDmaintenanceA local MCP server for handling X402 payment-protected HTTP endpoints, offering tools for order placement, signing, and payment submission with multiple signing modes and blockchain networks.7201MIT
- AlicenseAqualityBmaintenanceLocal-first MCP server for per-agent key management, generating and using signing keys without external KMS.8721MIT
- AlicenseNot gradedqualityAmaintenanceMCP server that lets any AI agent operate a wallet directly on-chain: create wallets, send, swap, bridge, and deploy contracts across EVM and Bitcoin networks.2MIT
TDQS
Scored across 6 tools
Each tool targets a distinct blockchain (EVM, UTXO, Tron, XRP, Kaspa, SVM), so there is no ambiguity about which tool to use for a given chain. Even within UTXO, the tool covers multiple coins but is clearly scoped to UTXO networks.
All tools follow a consistent pattern: a chain identifier prefix followed by '_sign' (e.g., evm_sign, utxo_sign). This makes the naming predictable and easy to navigate.
Six tools is well within the ideal range for a blockchain signing server. Each tool covers a major blockchain family, and no redundant or excessive tools are present.
The toolset provides signing capabilities for the most prominent blockchains and supports both transaction signing and typed-data/EIP-712 signing for EVM. Minor gaps exist (e.g., no Cosmos or other chains), but the surface is complete for its stated scope.