Scrollscan MCP for AI. Read Any On-Chain Data, Instantly.

Scrollscan gives your AI client direct access to all data flowing through the Scroll L2 blockchain. Forget jumping between explorer tabs just to check a few details; you ask your agent, and it pulls the raw chain data instantly.

Checking Balances

You need to know how much Ether is sitting in a wallet? You can use get_account_balance to grab the current ETH balance for one address. If you're auditing multiple wallets or checking several accounts at once, pull in get_account_balance_multi; it saves you from running dozens of separate calls.

For tokens, it’s similar but more detailed. You can check a specific ERC20 contract's balance for an address using get_token_balance, or calculate the total circulating supply of any given token with get_token_supply. If you want to know about all the ETH floating around on Scroll generally, use get_eth_supply to get that figure.

You also can track market movement by checking the current Ether price via get_eth_price.

Tracking Token Movements

When it comes to tokens, you're not limited to just standard ERC20 transfers. Your agent pulls transfer events for every type of digital asset. To see all recorded movements for basic ERC20 tokens by an address, run get_erc20_token_tx. For single-edition NFTs (ERC721), use get_erc721_token_tx to map out where those unique assets moved.

If you're dealing with multi-standard contracts that handle both ERC20 and NFTs, get_erc1155_token_tx tracks those complex transfers.

Understanding Contract Logic

Sometimes you gotta know what the smart contract is actually doing—it’s not enough to just see a transaction. You can pull the Application Binary Interface (ABI) for verified contracts using get_contract_abi. This details all the functions available, telling you exactly how the code is structured. If that isn't enough, you can retrieve the entire source code of a verified contract address with get_contract_source_code, letting you see the raw logic behind it.

Tracing Transaction History

To build a full audit trail, your agent pulls transaction data in layers. You get standard, user-initiated actions using get_normal_tx_list for an address. For deeper dives into what happened inside the contract, you can list all internal transactions with get_internal_tx_list, or narrow that down further by a block range using get_internal_tx_list_by_block_range, or even find them by hash using get_internal_tx_list_by_hash.

You always gotta check the outcome: you can verify if a transaction finished processing and what the result was using get_tx_receipt_status, or confirm it successfully went through the network with get_tx_status. Every single transaction detail, including all event logs generated by smart contracts for analysis, is available via get_logs.

Low-Level Network Mechanics

For deep protocol work, your agent accesses raw blockchain state data. You can find the current block number with proxy_block_number, or check what block number corresponds to a specific time using get_block_number_by_time. Need to know how much gas you're gonna spend? Run proxy_estimate_gas for an estimate, or get the current cost of gas on the network with proxy_gas_price.

You can also check what kind of reward miners are getting using get_block_reward, and even list every block number mined by a specific address using get_mined_blocks. If you want to look at all the raw data attached to a single block, use proxy_get_block_by_number or grab all details for a transaction hash with proxy_get_transaction_by_hash, and finally, get the complete outcome of that transaction using proxy_get_transaction_receipt.

You can even simulate a contract call—seeing what would happen without actually spending gas—using proxy_call, or reading specific pieces of data stored in a contract at a particular slot with proxy_get_storage_at.