evm-recon-mcp
This server gives an AI assistant read-only EVM contract reconnaissance tools to inspect unverified contracts on any EVM chain without an API key.
Fetch deployed runtime bytecode for any contract address.
Disassemble bytecode into opcodes with program counters and detect invalid jump targets.
Read raw storage slots and get uint/address interpretations.
Derive Solidity storage slots for mappings, nested mappings, arrays, keccak word regions, and more.
Decode calldata into selector and 32-byte words, identifying known functions.
Compute function selectors from canonical signatures.
Simulate read-only eth_call probes and report return/revert behavior.
List built-in chains; use custom rpc_url for any other network.
Provides read-only contract reconnaissance on Ethereum, including fetching bytecode, disassembling contracts, reading storage slots, deriving storage layouts, decoding calldata, and simulating eth_call operations.
Provides read-only contract reconnaissance on Optimism, using public RPC endpoints to fetch bytecode, disassemble contracts, read storage, decode calldata, and perform eth_call simulations.
Provides read-only contract reconnaissance on Polygon, including bytecode retrieval, disassembly, storage inspection, calldata decoding, and eth_call simulations via public RPC endpoints.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@evm-recon-mcp Disassemble 0x1234567890abcdef on Ethereum and list invalid jumps"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
evm-recon-mcp
Give your AI assistant the ability to read deployed smart contracts.
An MCP server for EVM contract reconnaissance: fetch bytecode, disassemble it, detect invalid jump targets, read storage slots, derive Solidity storage layouts, and decode calldata — on any EVM chain, with no API key.
Built for security researchers, auditors, and CTF players who keep hitting the same wall: the contract is unverified, there's no source, and you need to understand what it actually does.
Read-only by design. No private keys, no signing, no transactions.
Install
npx evm-recon-mcpClaude Code:
claude mcp add evm-recon -- npx -y evm-recon-mcpClaude Desktop — add to claude_desktop_config.json:
{
"mcpServers": {
"evm-recon": { "command": "npx", "args": ["-y", "evm-recon-mcp"] }
}
}Requires Node 18+.
Related MCP server: gulltoppr
The part you can't get elsewhere: invalid jump detection
Most disassemblers print opcodes. This one also tells you which jumps cannot land.
In the EVM, jumping to anything that isn't a JUMPDEST is an exceptional halt — the call reverts and consumes all gas. When a PUSH is immediately followed by JUMP/JUMPI, the target is statically known, so it can be checked. Hand-written assembly and puzzle contracts get this wrong constantly, sometimes deliberately.
=== 0x60055600005b00
0000: PUSH1 0x05
0002: JUMP
0003: STOP
0004: STOP
0005: JUMPDEST
0006: STOP
All statically-resolvable jump targets are valid JUMPDESTs.Change the push by one byte:
=== 0x60045600005b00
0000: PUSH1 0x04
0002: JUMP
...
!! 1 INVALID JUMP TARGET(S) — these revert if taken:
pc 0x0002 JUMP -> 0x4: target is STOP, not JUMPDEST — taking this jump
halts exceptionally (reverts, consumes all gas)That single line is often the whole answer to "why does this always revert?"
The decoder also skips PUSH immediate data correctly, so a 0x5b byte sitting inside push data is not mistaken for a jump destination — a classic source of wrong disassembly.
Tools
Tool | What it does |
| Fetch deployed runtime bytecode ( |
| Disassemble an address or raw hex, with PC offsets + invalid-jump analysis |
| Read a raw storage slot ( |
| Derive mapping, nested mapping, array, and hand-rolled |
| Split calldata into selector + 32-byte words, name known selectors |
| Compute 4-byte selectors from canonical signatures |
| Simulate a read-only call; reports returned vs reverted |
| List built-in chains |
Storage slot derivation
Reading an unverified contract's state means knowing where the state lives:
mapping—keccak256(pad32(key) . pad32(slot))nested_mapping— applied left to right formapping(a => mapping(b => c))array—keccak256(pad32(slot)) + indexkeccak_words—keccak256over concatenated 32-byte words, which is what hand-written assembly does when itMSTOREs values and hashes the region. Compiler-generated layouts don't cover this; hand-rolled ones need it.
Chains
Built in: ethereum, sepolia, holesky, polygon, polygon-amoy, arbitrum, optimism, base, base-sepolia, bsc, avalanche, gnosis, scroll, linea.
Any other network works by passing rpc_url directly. Each chain has multiple public endpoints and fails over automatically, so a single dead RPC doesn't stop you.
Example prompts
Disassemble
0x…on Base and tell me whether any jump target is invalid.
This contract is unverified. Read storage slot 0 and slot 1, and tell me what they probably are.
What's the storage slot for
balances[0xd8dA…]ifbalancesis at slot 2?
Decode this calldata and tell me which function it calls.
Safety
Every tool is read-only. The server never signs, never broadcasts, and never asks for a private key. eth_call is a simulation — nothing reaches the chain.
Public RPC endpoints see the addresses you query and your IP. For sensitive work, pass your own rpc_url.
License
MIT
Built by Oarkit: small software, Google Sheets add-ons and MCP servers for small teams. Need an MCP server built, fixed or upgraded? oarkit.com · hello@oarkit.com
Available Tools
8 toolscompute_storage_slotDerive a Solidity storage slotBRead-only
Derive storage slots. kind=mapping: keccak256(pad32(key).pad32(slot)). kind=nested_mapping: applied left to right. kind=array: keccak256(pad32(slot))+index. kind=keccak_words: keccak256 over concatenated 32-byte words, which is what hand-written assembly does when it MSTOREs values and hashes the region. kind=keccak_utf8 / keccak_hex: plain hashing.
Inputs: kind (required), key, keys, slot, +3 more.
decode_calldataDecode raw calldataARead-only
Split calldata into a 4-byte selector and 32-byte words, flag word values that look like addresses, and name the function when the selector is a well-known one.
Inputs: data (required).
disassembleDisassemble EVM bytecodeARead-only
Disassemble bytecode into opcodes with program counters. Supply either an on-chain address or a raw hex string. Crucially, this also validates statically-resolvable jump targets: a PUSH followed immediately by JUMP/JUMPI whose target is not a JUMPDEST will halt exceptionally at runtime (revert, all gas consumed). Those are reported separately as invalidJumps — a common intentional trap in CTF and puzzle contracts, and a real bug in hand-written assembly.
Inputs: chain, address, rpc_url, bytecode, +1 more.
eth_callSimulate a read-only callARead-only
Simulate a call with eth_call and report whether it returned or reverted. Nothing is broadcast and no key is used. Useful for probing which calldata and value combinations a contract accepts.
Inputs: to (required), data, from, block, +3 more.
function_selectorCompute function selectorsARead-only
Compute 4-byte selectors from canonical signatures, e.g. transfer(address,uint256).
Inputs: signatures (required).
get_bytecodeFetch deployed bytecodeARead-only
Fetch a contract's deployed runtime bytecode via eth_getCode. Returns size and hex. Empty result means the address is an EOA or has no code.
Inputs: address (required), block, chain, rpc_url.
list_chainsList supported chainsARead-only
List built-in EVM chains with their chain IDs and explorers. Any other network works by passing rpc_url.
Inputs: no named parameters.
read_storageRead a contract storage slotARead-only
Read a raw storage slot via eth_getStorageAt. Returns the 32-byte word plus uint and address interpretations.
Inputs: slot (required), address (required), block, chain, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Each tool targets a distinct recon activity: chains, bytecode, disassembly, storage slots, slot derivation, calldata decoding, selector computation, and call simulation. No two tools overlap in purpose; even the selector-related tools (decode_calldata and function_selector) serve clearly different functions.
Most tools follow a verb_noun pattern (list_chains, get_bytecode, read_storage, compute_storage_slot, decode_calldata). Minor deviations exist with disassemble (bare verb) and function_selector (noun form), but these are still readable and do not introduce confusion.
8 tools is well-scoped for EVM reconnaissance. Each tool earns its place and covers a distinct layer of contract analysis without redundancy or sprawl.
The set covers the core recon workflow: fetch bytecode, disassemble/validate, inspect storage, derive slots, decode calldata, compute selectors, and simulate calls. Minor gaps exist (e.g., no balance/transaction fetching), but they are outside the apparent specialization of smart-contract reconnaissance.
Maintenance
Related MCP Connectors
Read EVM and Solana chains for balances, tokens, eth_call, logs, receipts, gas, blocks and ENS.
Read chain data on 200+ networks and Sui: transactions, logs, balances, objects, ABI-decoded.
Resolve any EVM contract ABI (even unverified, via decompilation), read, simulate, prepare txs.
Read-only smart-contract security intelligence for autonomous agents.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceProvides tools for querying onchain data across 12+ blockchain networks, including token balances, transaction analysis, and smart contract security auditing. It enables users to interact with multiple EVM-compatible chains and perform deep contract evaluations through natural language interfaces.1-
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to resolve smart contract ABIs, read, encode, simulate, and prepare transactions across multiple blockchains via a REST API or MCP server, with no signing required.-
- AlicenseAqualityDmaintenanceEnables AI assistants to audit Solidity smart contracts for security vulnerabilities, fetch verified source code from block explorers, decode calldata, and estimate gas costs across major EVM networks.4MIT
- AlicenseNot gradedqualityBmaintenanceEnables querying blockchains across EVM, Solana, Bitcoin/UTXO, and Cosmos through a unified interface, with tools for resolving addresses, checking balances, fetching transactions and blocks, reading contracts, decoding calldata, and building unsigned transfers.11 npm3MIT