Skip to main content
Glama

crypto-mcp-server

A Model Context Protocol server that lets any MCP client (Claude Desktop, Cursor, etc.) perform EVM blockchain operations — reading balances, reading/writing contracts, simulating and sending transactions, and signing messages — through Alchemy RPC, using a wallet derived from a mnemonic or private key.

Features

  • Multi-chain across Alchemy-backed networks. The target network is selectable per tool call (defaults to the configured DEFAULT_NETWORK).

    • Mainnets: ethereum, base, arbitrum, optimism, polygon

    • Testnets: sepolia, base-sepolia, arbitrum-sepolia, optimism-sepolia, polygon-amoy

  • Both transports: stdio (default, for local clients) and Streamable HTTP (for remote/hosted use).

  • Tools:

    • Reads: get_native_balance, get_token_balance, get_gas_price, get_block, get_transaction, resolve_ens, read_contract

    • Writes: send_native, send_token, write_contract

    • Pre-flight: simulate_transaction (dry-run, never broadcasts)

    • Signing: sign_message (EIP-191), sign_typed_data (EIP-712)

Related MCP server: MCP Crypto Wallet EVM

Prerequisites

  • Node.js ≥ 18

  • An Alchemy API key

  • A wallet mnemonic or private key

Setup

npm install
cp .env.example .env   # then fill in the values
npm run build

Environment variables

Variable

Required

Description

ALCHEMY_API_KEY

yes

Your Alchemy API key. Used to build RPC endpoints for all chains.

MNEMONIC

one of

BIP-39 mnemonic phrase. Provide exactly one of this / key.

PRIVATE_KEY

one of

0x-prefixed hex private key. Provide exactly one.

DERIVATION_PATH

no

HD path used with MNEMONIC (defaults to ethers' default path).

DEFAULT_NETWORK

no

Default chain when a call omits network (mainnet or testnet, e.g. polygon-amoy, sepolia). Default: ethereum.

TRANSPORT

no

stdio (default) or http.

PORT

no

Port for the HTTP transport. Default: 3000.

The server fails to start (non-zero exit) if ALCHEMY_API_KEY is missing, if neither key is provided, or if both keys are provided.

Running

stdio (default — most MCP clients launch the server this way):

npm run start
# or for development with reload:
npm run dev

Streamable HTTP:

TRANSPORT=http PORT=3000 npm run start
# MCP endpoint: http://localhost:3000/mcp

Using with an MCP client (stdio)

Add to your client's MCP config (e.g. Claude Desktop's claude_desktop_config.json, or .cursor/mcp.json). See examples/mcp-client-config.json.

{
  "mcpServers": {
    "crypto": {
      "command": "node",
      "args": ["/absolute/path/to/crypto-mcp-server/dist/index.js"],
      "env": {
        "ALCHEMY_API_KEY": "your-alchemy-key",
        "PRIVATE_KEY": "0xyour-private-key",
        "DEFAULT_NETWORK": "ethereum"
      }
    }
  }
}

Security

This server can spend funds. It holds a mnemonic or private key in process memory and can sign and broadcast transactions.

  • Secrets are read only from environment variables and are never logged, echoed, or returned in tool outputs or error messages.

  • Prefer simulate_transaction before any send_* / write_contract call to preview gas and catch reverts.

  • The HTTP transport exposes spend operations over the network. It performs no authentication of its own — run it only behind a trusted network and/or an authenticating proxy. For local single-user use, prefer stdio.

  • Use a dedicated, low-value wallet. Never point this at a key holding significant funds without your own additional controls.

Development

npm run lint   # type-check only (tsc --noEmit)
npm run test   # vitest
npm run build  # compile to dist/

Available Tools

13 tools
get_blockA

Fetch a block by number, tag (e.g. 'latest'), or hash on a supported network.

Inputs: block (required), network.

get_gas_priceB

Get current fee data (gas price, EIP-1559 fields) for a network.

Inputs: network.

get_native_balanceA

Get the native currency balance (ETH/POL/etc.) of an address on a supported network.

Inputs: address (required), network.

get_token_balanceA

Get an ERC-20 token balance for an address, using the token's on-chain decimals and symbol.

Inputs: token (required), address (required), network.

get_transactionA

Fetch a transaction and, if mined, its receipt by hash on a supported network.

Inputs: hash (required), network.

read_contractB

Call a read-only (view/pure) contract method. Provide the contract address, an ABI fragment array, the method name, and arguments.

Inputs: abi (required), method (required), address (required), args, +1 more.

resolve_ensA

Resolve an ENS name to an address, or an address to its primary ENS name, where the network supports ENS.

Inputs: query (required), network.

send_nativeA

Sign and broadcast a native currency transfer from the configured wallet. STATE-CHANGING: spends funds.

Inputs: to (required), amount (required), network.

send_tokenA

Sign and broadcast an ERC-20 transfer from the configured wallet, converting the amount using the token's decimals. STATE-CHANGING.

Inputs: to (required), token (required), amount (required), network.

sign_messageA

Sign an arbitrary text message (EIP-191 personal_sign) with the configured wallet.

Inputs: message (required).

sign_typed_dataB

Sign EIP-712 typed data with the configured wallet. Provide domain, types, and value.

Inputs: types (required), value (required), domain (required).

simulate_transactionA

Dry-run a transaction (native/erc20/contract) WITHOUT broadcasting. Returns success/revert, gas estimate, and a decoded revert reason when it would fail.

Inputs: kind (required), to, abi, args, +5 more.

write_contractB

Sign and broadcast a call to a state-changing contract method. Provide address, ABI fragments, method, args, and optional native value. STATE-CHANGING.

Inputs: abi (required), method (required), address (required), args, +2 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct operation: block retrieval, balance queries, transfers, signing, simulation, etc. No two tools overlap in purpose; even similar actions like sending native vs token are clearly differentiated by asset type and description.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_block, send_native, sign_message). The verbs are uniform and the structure is predictable, making it easy to infer tool functionality from the name.

    Tool Count5/5

    With 13 tools, the server covers a broad yet focused set of crypto operations (reads, writes, signing, simulation) without being overwhelming. This count is well within the optimal range for a domain-specific MCP server.

    Completeness4/5

    The tool set covers essential read/write operations, ENS resolution, signing, and simulation. Minor gaps exist, such as token approval (required for ERC-20 transfers) and event log retrieval, but core workflows are well-supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      Provides comprehensive access to Ethereum Virtual Machine (EVM) JSON-RPC methods for querying blockchain data, executing smart contract calls, and interacting with any EVM-compatible network including Ethereum, Polygon, Arbitrum, and more. Enables users to check balances, analyze transactions, estimate gas, retrieve logs, and perform blockchain operations through natural language.
      19
      16 npm
      3
      MIT
    • F
      license
      C
      quality
      B
      maintenance
      Enables AI agents to interact with any EVM-compatible blockchain through natural language, supporting token swaps, cross-chain bridges, staking, lending, governance, gas optimization, and portfolio tracking across networks like Ethereum, BSC, Polygon, Arbitrum, and more.
      100
      49 npm
      44
      -