M
Mcp Signer
MCP server for local transaction signing on EVM, UTXO, Tron, and XRP — no API calls needed
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
Not yet automatically verified
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.
Manual Client & Custom JSON ConfigExpand JSON ▾
Install Config Generator
Choose your client
💡 Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows)
Capabilities & Tool Schemas (6)
Inspect callable tools, capabilities, and parameters exposed to AI agents by Mcp Signer.
evm_signSign an EVM transaction (Ethereum, Ethereum Classic, BSC, Polygon, Avalanche (C-Chain), Arbitrum, Base, Optimism, Tron).
utxo_signSign a UTXO transaction (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash).
tron_signSign a Tron transaction using secp256k1 (no TronWeb dependency).
xrp_signSign an XRP transaction.
kaspa_signSign a Kaspa transaction using schnorr (BIP340) via `kaspa-wasm`. Mainnet only.
svm_signPartial-sign a Solana (SVM) x402 payment transaction — the buyer's source-authority signature only
Documentation Overview
@cryptoapis-io/mcp-signer
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.
Security
- Stdio only — no HTTP transport. The server does not listen on any port.
- Private keys in tool input — each tool receives
privateKey/privateKeys/secretas parameters. Keys are never read from environment variables. - No network calls — all signing is done locally using cryptographic libraries.
Installation
Or install all Crypto APIs MCP servers: npm install @cryptoapis-io/mcp
Usage
Claude Desktop
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows):
Cursor
Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):
MCP Inspector
Available Tools
evm_sign
Sign 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_sign
Sign 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_sign
Sign 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_sign
Sign 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_sign
Sign 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_sign
Partial-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.
Dependencies
| Package | Purpose |
|---|---|
ethers | EVM transaction signing |
bitcoinjs-lib + ecpair + tiny-secp256k1 | UTXO transaction signing |
elliptic | Tron transaction signing (secp256k1) |
xrpl | XRP transaction signing |
License
MIT
Related MCP Servers
Frequently Asked Questions about Mcp Signer
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/mcp-signer)HTML Embed
<a href="https://allmcps.com/mcp/mcp-signer"><img src="https://allmcps.com/api/badge/mcp-signer?style=directory" alt="Mcp Signer on AllMCPs" /></a>Technical Specs & Signals
CategoryFinance & Fintech
5/5 checks healthy over the last 6h
52Quality signal: Good · 52/100How this signal is calculated ▾
Server availabilityNot measured
Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.
Verified ownership10/20
Documentation & tools25/30
Adoption & activity4/15
Community engagement0/10
A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.
Own this project?
This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to get the verified badge and attach your website.
Free dofollow backlink: after claiming, verify your product site and place a dofollow AllMCPs badge — we recheck it stays live.
Claim & get free dofollowShare & Embed
Add our SVG badge (dark/light directory styles) or embeddable widget to your site.