The read surface is wide enough that many sessions never sign anything: blocks, contracts, prices, TVL, ENS and the whole security-screening set are queries. The write surface sits directly beside it under matching names — execute_swap next to get_swap_quote, write_contract next to read_contract, transfer_nft next to get_nft_info — and those take a private key. Worth deciding up front which half you mean to use, because 720 tool definitions travel with the session either way.
An EVM toolkit exposed as 720 tools, most of them taking a network argument, running from raw chain reads through DeFi positions to signing and contract deployment.
- Chain reads: chain info and supported networks, blocks by hash or number, block ranges and receipts, uncle blocks, gas oracle tiers and network health
- Transactions inspected by hash, simulated before sending, and — while still pending — sped up or cancelled by resubmitting at higher gas
- Contracts read and written by ABI, deployed directly or through CREATE2 and proxies, upgraded and verified
- ERC-20, ERC-721 and ERC-1155 handling: balances, metadata, single and batch transfers, allowances granted and revoked, supply and holder-count estimates
- DEX work end to end — quote, best route across DEXes, price impact, execution — plus liquidity added and removed, including the native-token pairs
- Staking, lending and bridging: positions and rates, health factor, liquidatable positions, Lido stake and wrap, bridge quotes, fees and status
- Governance from proposal detail through voting power, delegation, casting a vote, and queuing or executing the result
- Signing and verification for messages, typed data and permits, signer recovery, and wallet creation and import from mnemonics
- ENS resolved both directions, with text records, avatars, availability, registration, renewal and subdomains
- Pre-signature screening: token security analysis, honeypot and rug-pull detection, approval risk, holder distribution, contract ownership, and the GoPlus checks
- Market and ecosystem data: Chainlink and Uniswap price feeds, and DefiLlama coverage of protocol and chain TVL, yields, fees, stablecoins, bridges, liquidations, hacks and raises
For anything that sends a transaction, a funded EVM account: the signing tools take a privateKey argument and the server reads PRIVATE_KEY from the environment. The read tools need neither.
One command plus a key — npx @nirholas/universal-crypto-mcp, then supply credentials