Skip to main content
ClaudeWave
CryptoAPIs-io avatar
CryptoAPIs-io

cryptoapis-mcp-signer

View on GitHub

MCP server for local transaction signing across EVM, UTXO, Tron, and XRP blockchains — no API calls required

MCP ServersOfficial Registry0 stars0 forksTypeScriptUpdated today
ClaudeWave Trust Score
52/100
· OK
Passed
  • Clear description
  • Topics declared
Flags
  • !No standard license detected
Last scanned: 6/11/2026
Install in Claude Code / Claude Desktop
Method: NPX · @cryptoapis-io/mcp-signer
Claude Code CLI
claude mcp add cryptoapis-mcp-signer -- npx -y @cryptoapis-io/mcp-signer
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "cryptoapis-mcp-signer": {
      "command": "npx",
      "args": ["-y", "@cryptoapis-io/mcp-signer"]
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
Use cases

MCP Servers 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` / `secret` as parameters. Keys are never read from environment variables.
- **No network calls** — all signing is done locally using cryptographic libraries.

## Installation

```bash
npm install @cryptoapis-io/mcp-signer
```

Or install all Crypto APIs MCP servers: `npm install @cryptoapis-io/mcp`

## Usage

```bash
npx @cryptoapis-io/mcp-signer
```

### 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):

```json
{
  "mcpServers": {
    "cryptoapis-signer": {
      "command": "npx",
      "args": ["-y", "@cryptoapis-io/mcp-signer"]
    }
  }
}
```

### Cursor

Add to `.cursor/mcp.json` (project) or `~/.cursor/mcp.json` (global):

```json
{
  "mcpServers": {
    "cryptoapis-signer": {
      "command": "npx",
      "args": ["-y", "@cryptoapis-io/mcp-signer"]
    }
  }
}
```

### MCP Inspector

```bash
npx @modelcontextprotocol/inspector npx @cryptoapis-io/mcp-signer
```

## 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
aiblockchainclaudecryptoapiscursorevmmcpmodel-context-protocolsigningtronutxoxrp

What people ask about cryptoapis-mcp-signer

What is CryptoAPIs-io/cryptoapis-mcp-signer?

+

CryptoAPIs-io/cryptoapis-mcp-signer is mcp servers for the Claude AI ecosystem. MCP server for local transaction signing across EVM, UTXO, Tron, and XRP blockchains — no API calls required It has 0 GitHub stars and was last updated today.

How do I install cryptoapis-mcp-signer?

+

You can install cryptoapis-mcp-signer by cloning the repository (https://github.com/CryptoAPIs-io/cryptoapis-mcp-signer) or following the README instructions on GitHub. ClaudeWave also provides quick install blocks on this page.

Is CryptoAPIs-io/cryptoapis-mcp-signer safe to use?

+

Our security agent has analyzed CryptoAPIs-io/cryptoapis-mcp-signer and assigned a Trust Score of 52/100 (tier: OK). See the full breakdown of passed checks and flags on this page.

Who maintains CryptoAPIs-io/cryptoapis-mcp-signer?

+

CryptoAPIs-io/cryptoapis-mcp-signer is maintained by CryptoAPIs-io. The last recorded GitHub activity is from today, with 0 open issues.

Are there alternatives to cryptoapis-mcp-signer?

+

Yes. On ClaudeWave you can browse similar mcp servers at /categories/mcp, sorted by popularity or recent activity.

Deploy cryptoapis-mcp-signer to your cloud

Ship this repo to production in minutes. Each platform spins up its own environment with editable env vars.

Maintain this repo? Add a badge to your README

Drop the badge into your GitHub README to show it's tracked on ClaudeWave. Each badge links back to this page and reflects the live Trust Score.

Featured on ClaudeWave: CryptoAPIs-io/cryptoapis-mcp-signer
[![Featured on ClaudeWave](https://claudewave.com/api/badge/cryptoapis-io-cryptoapis-mcp-signer)](https://claudewave.com/repo/cryptoapis-io-cryptoapis-mcp-signer)
<a href="https://claudewave.com/repo/cryptoapis-io-cryptoapis-mcp-signer"><img src="https://claudewave.com/api/badge/cryptoapis-io-cryptoapis-mcp-signer" alt="Featured on ClaudeWave: CryptoAPIs-io/cryptoapis-mcp-signer" width="320" height="64" /></a>

More MCP Servers

cryptoapis-mcp-signer alternatives