Zetachain Explorer MCP. Audit and trace any asset movement on ZetaChain.

You're dealing with blockchain data. You need more than just a pretty web interface; you need raw access for your AI agent. The Zetachain Explorer API is an MCP Server that hands your agent direct command-line power over the ZetaChain ledger. It lets your client skip the manual clicking, turning complex tasks—like tracking asset movements or reverse-engineering smart contract calls—into simple, executable commands.

Your agent uses 17 specialized tools to interrogate every layer of the network. You can build sophisticated data pipelines that read block headers, check token ownership, and trace internal logic without leaving your chat window.

When you need a high-level overview, start by seeing what's happening across the whole chain. You'll use list_blocks to pull a list of recently mined blocks, or run list_transactions to see every executed transaction across ZetaChain. If you want an inventory of available assets, list_tokens gives you the full directory of token types in circulation.

To dive into specific addresses, your agent first uses get_address to fetch core details for any given address. For a complete history check, it runs get_address_transactions, which pulls every single transaction and its associated data linked to that wallet. If you want to know what assets the wallet currently holds, get_address_tokens retrieves all unique token types belonging to that address.

But knowing what they hold isn't enough. You can use get_token_balances to get the current balance for every asset associated with an address. For deeper forensic work on assets, you first call get_address_tokens to list every unique token type held, then use that data to execute specific checks like getting detailed metadata via get_token, or tracking exactly who owns a certain asset using get_token_holders.

To see the movement of funds, you run get_token_transfers, which returns records detailing specific transfers between two addresses.

When investigating activity on a single transaction, your agent starts with get_transaction to fetch all details for one unique hash. If that primary transaction triggered secondary contract actions—those internal calls—you'll use get_transaction_internal. For the absolute deepest level of debugging, you can pull the raw event logs emitted by any transfer using get_transaction_logs.

You also get a full picture of what happened within an address's history by running get_address_internal_transactions, which specifically targets contract calls that ran internally during a transaction associated with that address.

Need to inspect the block itself? Use get_block to pull detailed information about any specific block, either by its hash or its number. If you want to see every single transfer contained within that exact block, you run get_block_transactions. For smart contract analysis—the real heavy lifting—you use get_smart_contract to fetch the source code and Application Binary Interface (ABI) for a contract address, letting you inspect its structure.

Finally, if you only have a transaction hash but need the full data payload, you can get it using get_transaction.