Blockscout MCP. Analyze any on-chain data from your chat.
Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Blockscout lets your AI agent query Ethereum-based blockchains directly. It gives you tools to check addresses, track token portfolios (ERC-20, ERC-721, etc.), inspect transaction details, and audit smart contract code.
Use it to pull real-time on-chain metrics and data without leaving your chat interface.
What your AI agents can do
Get account balance
Gets the native coin balance for a specified address.
Get account internal transactions
Retrieves internal transactions associated with a given address.
Get account transactions
Fetches all transactions linked to a specific address.
Retrieves native coin balances, ENS names, and full transaction logs for a specific wallet or contract address.
Aggregates and reports all types of tokens (ERC-20, ERC-721, ERC-1155) associated with an address.
Pulls the status, gas usage, and input data for a specific transaction hash.
Fetches the contract's ABI and its original source code for deep technical review.
Executes standard Ethereum JSON-RPC 2.0 methods directly against the network state.
Ask AI about this MCP
Supported MCP Clients
Waiting for input…
Blockscout MCP Server: 14 Tools for Blockchain Data
Use these tools to query addresses, transactions, contract code, and token balances across Ethereum-based chains.
019e5d01get account balance
Gets the native coin balance for a specified address.
019e5d01get account internal transactions
Retrieves internal transactions associated with a given address.
019e5d01get account transactions
Fetches all transactions linked to a specific address.
019e5d01get address
Retrieves basic details and metadata for a blockchain address.
019e5d01get block
Fetches detailed metadata for a specified block number.
019e5d01get contract abi
Gets the Application Binary Interface (ABI) used by a smart contract.
019e5d01get contract source code
Retrieves the original source code for a smart contract.
019e5d01get indexing status
Checks the operational indexing health of the Blockscout explorer instance.
019e5d01get logs
Retrieves event logs emitted during a specific transaction.
019e5d01get token
Fetches detailed information about a specific token contract.
019e5d01get total supply
Retrieves the total circulating supply of the native coin.
019e5d01get transaction
Gets detailed status and metadata for a specific transaction hash.
019e5d01json rpc
Executes any standard Ethereum JSON-RPC 2.0 method call.
019e5d01list token balances
Lists and aggregates all token balances for a given address.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Blockscout, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
Blockscout lets your AI agent query Ethereum-based blockchains directly. You'll get tools to check addresses, track token portfolios (ERC-20, ERC-721, etc.), inspect transaction details, and audit smart contract code. You can pull real-time on-chain metrics and data without ever leaving your chat interface.
Audit account balances and history
- You can get a specified address's native coin balance using
get_account_balance. You'll also pull all transactions linked to that address withget_account_transactions, and you'll find all internal transactions associated with it viaget_account_internal_transactions. You can check the basic metadata for any address withget_address. * - To list every single token—ERC-20, ERC-721, and ERC-1155—associated with an address, you use
list_token_balances. You can also pull detailed information for a specific token contract usingget_token.
Inspect transaction details
- You can check the status, gas used, and input data for a specific transaction hash using
get_transaction. You can also get event logs emitted during a transaction usingget_logs.
Analyze smart contract code
- You can fetch the Application Binary Interface (ABI) used by a smart contract with
get_contract_abi. You can pull the original source code for a smart contract usingget_contract_source_code.
Query raw blockchain state and network data
- You can execute any standard Ethereum JSON-RPC 2.0 method call directly against the network state using
json_rpc. This lets you query raw data withget_block(fetching block metadata) and check the operational indexing health of the explorer instance withget_indexing_status. - You can also pull detailed metadata for a specific block number using
get_block.
Utility Tools
- You can check the total circulating supply of the native coin using
get_total_supply. - You can get detailed metadata for a specific block number using
get_block.
How Blockscout MCP Works
- 1 Subscribe to the server and give it the Base URL for your Blockscout instance.
- 2 Your AI client calls a specific tool, like
get_tokenorget_account_balance, passing the required address or hash. - 3 The server executes the tool against the blockchain and returns structured, usable data to your AI client.
The bottom line is: you ask your AI client a question, and it runs the necessary blockchain tools to give you a direct, data-backed answer.
Who Is Blockscout MCP For?
The Web3 developer who needs to verify contract logic without leaving their IDE. The security auditor who has to check transaction flows across dozens of addresses. The data analyst who needs to pull on-chain metrics and token distributions into a report, fast. If you work with Ethereum assets, this is for you.
Verifies contract deployments and debugs transaction logic by calling get_contract_abi or get_contract_source_code directly from their IDE.
Extracts on-chain metrics, like total supply or token distribution, by using natural language prompts with tools like get_total_supply.
Monitors multiple wallet balances and tracks portfolio movements by calling list_token_balances to get a single view.
What Changes When You Connect
- Audit full account health. Use
get_account_balanceandget_addressto get a single view of an address's native balance, ENS name, and transaction count. - Track complex portfolios.
list_token_balancesaggregates all token types (ERC-20, ERC-721, ERC-1155) for one address, eliminating the need for multiple API calls. - Deep dive into transactions.
get_transactionprovides gas usage and full status details, so you know exactly what happened with a specific hash. - Review smart contract logic. Use
get_contract_abiandget_contract_source_codeto pull the contract's technical blueprint directly into your workflow. - Check network health.
get_indexing_statuslets you confirm the underlying data source is working before you run complex queries. - Run custom queries. The
json_rpctool lets you execute any standard Ethereum JSON-RPC 2.0 method if a dedicated tool doesn't exist.
Real-World Use Cases
Auditing a suspect wallet
A security auditor needs to know if a wallet is involved in shady activity. They prompt their agent: 'Get the balance, transaction count, and all tokens for 0x...'. The agent runs get_account_balance, list_token_balances, and get_address to build a complete profile.
Debugging a failed smart contract
A developer finds a contract failing. They use the agent to run get_contract_source_code and get_contract_abi. They then check the transaction history with get_transaction to see the exact inputs and error logs, solving the bug without leaving the IDE.
Calculating total market supply
A data analyst needs the total circulating supply of a coin. They ask the agent to run get_total_supply, immediately getting the metric needed for a market report. They then follow up with get_token for specific token details.
Tracing asset movement
A crypto power user wants to know where a specific NFT went. They use the agent to check the get_logs for a transaction hash, which reveals the token IDs and contract interaction that moved the asset.
The Tradeoffs
Over-querying history
Asking the agent to run get_account_transactions without filtering or pagination, hoping for everything. This will time out or hit rate limits.
→
Instead, start by using get_address to get the basic metadata. If you need history, use get_account_transactions and specify a date range or a starting block number to limit the scope.
Ignoring specialized tools
Just using the generic json_rpc for simple balance checks. This is slow and verbose when a dedicated tool exists.
→
Always use the specific tool first. For simple balances, run get_account_balance. For token lists, run list_token_balances. Only fall back to json_rpc when the tool doesn't exist.
Assuming data completeness
Asking for a token balance but forgetting the contract address. The request fails because the tool needs specific contract parameters.
→
Always provide the necessary identifiers. For token info, use get_token and include the token contract address and the target address.
When It Fits, When It Doesn't
Use this if your primary job is reading and analyzing immutable blockchain state. You need to answer questions like, 'What was the state of this address at block 123?' or 'What was the source code for this contract?' If your goal is simply sending messages or managing tasks, this isn't for you. If you only need to know the current price of a coin, check a dedicated price feed tool instead. You should use the specialized tools (get_account_balance, list_token_balances) first. Only use json_rpc as a last resort when the required function doesn't have a dedicated tool.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Blockscout. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 14 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Manually checking blockchain data is a painful, multi-tab process.
Today, you have to copy a wallet address, jump to a web explorer, find the 'Token' tab, then run a separate query for ERC-20, then copy the address again to check the 'Transactions' tab. This is tedious clicking, copying, and switching tabs just to get a full picture of an account.
With Blockscout, you tell your agent: 'Give me the full profile for 0x...'. It runs `get_account_balance`, `list_token_balances`, and `get_address` and hands you a clean, compiled answer. You don't touch a browser.
Blockscout MCP Server: Get the full contract profile.
Previously, getting a contract's ABI meant finding the contract address, then navigating to the 'Contract' tab, and finally hitting a button to view the ABI. You had to do this for every single contract you wanted to audit.
Now, you just ask the agent to `get_contract_abi` and `get_contract_source_code`. It gives you the full technical specs immediately. It's a direct, single-step data pull.
Common Questions About Blockscout MCP
How do I use the `get_account_balance` tool? +
You pass the target address to the tool. It returns the native coin balance. If you need to check token holdings, use list_token_balances instead, as it handles multiple token types.
Can `get_transaction` show me the gas used? +
Yes. get_transaction pulls the status, gas used, and total fee for any specific transaction hash. This is crucial for auditing transaction costs.
What is the difference between `get_logs` and `get_account_transactions`? +
The difference is the data layer. get_account_transactions shows the high-level history of the address. get_logs retrieves specific, emitted event logs from a transaction, detailing what happened inside the contract call.
How do I query a custom Ethereum function? +
Use the json_rpc tool. This lets you execute any standard Ethereum JSON-RPC 2.0 method call, giving you access to the full network API suite.
Does Blockscout support ERC-721 tokens? +
Yes. The list_token_balances tool handles ERC-20, ERC-721, and ERC-1155 tokens in a single query, giving you a complete asset picture.
How does `list_token_balances` handle different token standards (like ERC-20 vs. ERC-721)? +
It lists balances for all supported token types in one call. The tool supports standard ERC-20, ERC-721, and ERC-1155 tokens, giving you a comprehensive view of the address's entire portfolio.
What happens if I try to get data for a non-existent address using `get_address`? +
The tool returns a specific error message detailing that the address was not found. This structured error allows your agent to handle the failure gracefully and prompt the user for a correction.
Is `json_rpc` better than using `get_contract_abi` for advanced data retrieval? +
They serve different purposes. Use get_contract_abi to retrieve the contract's interface definition. Use json_rpc when you need to execute a specific, raw Ethereum JSON-RPC 2.0 method call directly.
Can I see all the different tokens owned by a specific wallet address? +
Yes. By using the list_token_balances tool with the wallet's address hash, the agent will return a comprehensive list of all ERC-20, ERC-721, and ERC-1155 tokens associated with that account.
Is it possible to check if the Blockscout explorer is fully updated with the latest chain data? +
Absolutely. You can use the get_indexing_status tool to check the synchronization progress, including the indexing ratios for blocks and internal transactions.
Can I retrieve the ABI of a verified smart contract to interact with it? +
Yes, for verified contracts, you can use the get_contract_abi tool. This provides the Application Binary Interface required for decoding transactions or making contract calls.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
ContentStack (Management)
Grant your AI agent read-write capabilities using ContentStack CMA. Update, publish, and manage contents, schemas, and environments from chat.
HTML XSS Sanitizer
Protect your database from malicious code. Clean and sanitize user-generated HTML payloads instantly local.
Runlayer
AI enterprise control plane: manage MCP servers, skills, agents, and security policies via agents.
You might also like
IBGE Full Access — Dados Brasileiros
The ultimate Brazil data Mega-Server: 15 tools spanning census, cities, CNAE economy, name trends, survey indicators, IBGE news, and country comparisons — all of Brazil's official statistics in one zero-auth integration.
Datos.gob.es (Catálogo Nacional)
Access Spain's National Open Data Catalog — search datasets, filter by theme, publisher, or format, and retrieve public sector information directly.
DOJ NCVS Crime Data
Access US crime statistics — audit victimization data and safety via AI.