English Français العربية

io.github.CryptoAPIs-io/mcp-signer

السجل الرسمي المالية والمدفوعات

Local transaction signing for EVM, UTXO, Tron, XRP, Kaspa, Solana and Tezos — no API calls

الشيفرة المصدرية التوثيق

التثبيت

أضف هذا إلى إعدادات MCP في عميلك (Claude Desktop: claude_desktop_config.json، وCursor: ‏.cursor/mcp.json، ويستخدم VS Code وغيره الصيغة نفسها «mcpServers»).

NPM package @cryptoapis-io/mcp-signer
Claude Code 
claude mcp add mcp-signer -- npx -y @cryptoapis-io/mcp-signer@0.5.0
إعداد JSON (Claude Desktop وCursor وVS Code) 
{
    "mcpServers": {
        "mcp-signer": {
            "command": "npx",
            "args": [
                "-y",
                "@cryptoapis-io/mcp-signer@0.5.0"
            ]
        }
    }
}

التوثيق

مأخوذ من ملف README للمشروع على GitHub ويُحدَّث أسبوعيًا. تفتح الروابط على GitHub.

المحتويات
  1. @cryptoapis-io/mcp-signer
  2. Security
  3. Installation
  4. Usage
  5. Available Tools
  6. Dependencies
  7. License

@cryptoapis-io/mcp-signer

MCP server for local transaction signing across EVM, UTXO, Tron, XRP, Kaspa, Solana and Tezos. 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

npm install @cryptoapis-io/mcp-signer

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

Usage

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

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

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

{
  "mcpServers": {
    "cryptoapis-signer": {
      "command": "npx",
      "args": ["-y", "@cryptoapis-io/mcp-signer"]
    }
  }
}
MCP Inspector
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).

ActionDescription
sign-from-detailsSign from structured transaction fields (to, value, gasLimit, etc.)
sign-unsigned-hexSign a pre-built unsigned transaction hex
sign-typed-dataSign 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).

ActionDescription
sign-from-detailsSign from a prepared transaction object (inputs, outputs)
sign-unsigned-hexSign a raw unsigned transaction hex with input descriptors
tron_sign

Sign a Tron transaction using secp256k1 (no TronWeb dependency).

ActionDescription
sign-from-detailsSign from a transaction object with raw_data_hex
sign-unsigned-hexSign a pre-built unsigned transaction hex
xrp_sign

Sign an XRP transaction.

ActionDescription
sign-from-detailsSign from structured XRP transaction fields
sign-unsigned-hexSign a pre-built unsigned transaction hex
kaspa_sign

Sign a Kaspa transaction using schnorr (BIP340) via kaspa-wasm. Mainnet only.

ActionDescription
sign-from-detailsSign 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).

ActionDescription
partial-signDeserialize the base64 unsigned TransferChecked tx from the x402 buyer /authorize (scheme svm-transaction), add the buyer signature, re-serialize to base64. Returns { transaction }.
tezos_sign

Sign a Tezos operation for tz1 (ed25519), tz2 (secp256k1) or tz3 (P-256) keys (edsk… / spsk… / p2sk…).

ActionDescription
sign-forged-operationSign the forgedOperation hex from prepare_transactions_tezos. The operation is decoded first: only reveal/transaction ops from the key's own address are signed, and the optional expected (destination, amount in mutez, maxFee) must match. Returns { signedOperation, operationHash, signature, … }; broadcast signedOperation.

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

PackagePurpose
ethersEVM transaction signing
bitcoinjs-lib + ecpair + tiny-secp256k1UTXO transaction signing
ellipticTron transaction signing (secp256k1)
xrplXRP transaction signing

License

MIT

الأسئلة الشائعة

ما هو io.github.CryptoAPIs-io/mcp-signer؟

Local transaction signing for EVM, UTXO, Tron, XRP, Kaspa, Solana and Tezos — no API calls

كيف أثبّت io.github.CryptoAPIs-io/mcp-signer؟

يعمل على جهازك. في Claude Code: claude mcp add mcp-signer -- npx -y @cryptoapis-io/mcp-signer@0.5.0. وفي العملاء الآخرين، الصق إعداد JSON من هذه الصفحة في إعدادات MCP الخاصة بهم.

هل يحتاج io.github.CryptoAPIs-io/mcp-signer إلى مفتاح API؟

لا يذكر إدراجه في السجل أي مفتاح أو سر إلزامي. قد تتطلب بعض الميزات حسابًا لدى الخدمة التي يتصل بها.

هل io.github.CryptoAPIs-io/mcp-signer مفتوح المصدر؟

نعم. شيفرته متاحة على GitHub بترخيص MIT.

من يصون io.github.CryptoAPIs-io/mcp-signer؟

ينشره CryptoAPIs-io. يدرجه AI.tn لكنه لا يصونه ولا يوصي به.

من سجل MCP الرسمي. الإدراج ليس توصية: راجع شيفرة الخادم وصلاحياته قبل منحه الوصول إلى بياناتك.