Blockscout MCP for AI. Analyze on-chain data from your chat or IDE.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
Blockscout connects any blockchain explorer directly to your AI agent. You can query addresses, track tokens, and analyze transactions across Ethereum-based chains without leaving your chat or IDE.
Get real-time data on balances, contract code, and block metadata instantly.
What your AI can do
Get account balance
Checks the native cryptocurrency balance for a specified address.
Get account internal transactions
Retrieves internal transactions associated with an account address.
Get account transactions
Lists all historical transactions linked to a specific address.
Retrieve the native coin balance, transaction count, and ENS name for any given wallet or contract address.
List all ERC-20, ERC-721, and ERC-1155 tokens associated with an address using a single query.
Get full details on any transaction hash, including status, gas consumption, and input data.
Retrieve the contract's Application Binary Interface (ABI) or its original source code for debugging purposes.
Check block metadata, including miner details and timestamps, or verify the explorer's current indexing status.
Ask an AI about this
Waiting for input…
Blockscout: 14 Tools for On-Chain Analysis
This collection of tools lets you deep dive into Ethereum's data layer. You can check everything from simple account balances to complex contract source code and event logs.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Blockscout on VinkiusGet Account Balance
Checks the native cryptocurrency balance for a specified address.
Get Account Internal Transactions
Retrieves internal transactions associated with an account address.
Get Account Transactions
Lists all historical transactions linked to a specific address.
Get Address
Fetches general metadata and details about a given blockchain address.
Get Block
Retrieves complete data for a specified block number, including miner information.
Get Contract Abi
Returns the Application Binary Interface (ABI) required to interact with a contract.
Get Contract Source Code
Retrieves the original human-readable source code for a verified smart contract.
Get Indexing Status
Verifies if the underlying block explorer instance is fully synced and indexed.
Get Logs
Extracts specific event logs that occurred during a transaction or block period.
Get Token
Gets detailed information about a specific token contract, like its symbol and...
Get Total Supply
Calculates the total circulating supply for a native coin or token.
Get Transaction
Retrieves full details, including gas costs and recipient data, for one transaction hash.
Json Rpc
Executes any standard Ethereum JSON-RPC 2.0 method call directly through the agent.
List Token Balances
Lists all types of tokens (ERC-20, NFTs) held by a specific address in one query.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
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 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ 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
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 connection provides 14 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Manually tracking asset ownership is a nightmare of tabs and APIs.
Today, checking an address's full holdings means jumping between the native coin tracker, then finding the ERC-20 section, switching to the NFT marketplace view, and maybe running a separate API call just for governance tokens. You copy-paste addresses into five different web pages, risking data mismatch every time.
With this MCP, you ask your agent one question: 'Show me all assets at address X.' The system consolidates everything—the native balance, the list of ERC-20s, and the NFTs—and presents it in a single output. It’s an instant audit.
Using `list_token_balances` gives you a complete picture of all asset types.
Before, you'd have to run separate queries for standard tokens versus non-fungible assets. You'd get one list and then another list, forcing you to mentally merge the data points to know the true scope of holdings.
Now, running `list_token_balances` aggregates all those types into a single payload. It’s simple; it cuts out the multi-step process.
What your AI can actually do with this
Need to know what's happening on a smart contract? This MCP lets you ask complex blockchain questions using natural language. Forget switching between multiple explorer tabs; just ask your agent directly for the raw data. You can get native balances for any wallet or contract address, list every ERC-20 and NFT token an address holds in one go, and pull detailed information about specific transactions—including gas usage and decoded input data.
Want to audit a smart contract? Use this toolset to fetch verified ABIs and source code directly from the chain. It's deep on-chain analysis delivered through simple conversation. By connecting Blockscout via Vinkius, you get a single point of access to read block metadata and check indexing status for immediate verification.
019e5d01-6441-730b-a707-ef1f8119cf06 Here's how it actually works
The bottom line is that your AI client handles all the complex API calls so you just have to ask a question.
Subscribe to this MCP and provide the base URL of your preferred Blockscout instance.
Your AI client routes the request through the connection, targeting specific blockchain data points (e.g., a transaction hash or address).
The agent returns clean, structured data—like balances or contract source code—ready for you to read or use in subsequent prompts.
Who is this actually for?
Web3 developers and data analysts need this. Specifically, anyone who spends time verifying contract interactions or auditing asset ownership across multiple blockchain explorers. It saves hours of manual tab-switching and API integration work.
Checks the get_contract_abi output to confirm a deployed contract matches expected standards before writing a vulnerability report.
Uses natural language queries to pull token distributions and transaction counts for client reports, avoiding manual data scraping.
Runs json_rpc calls directly from their IDE when debugging a new smart contract feature or verifying an endpoint.
What Changes When You Connect
Audit token ownership instantly. Instead of running multiple API calls, use list_token_balances to pull a complete picture of all assets held by an address.
Debug contracts faster. You can grab the ABI using get_contract_abi or see the original source code with get_contract_source_code, letting you confirm logic without leaving your terminal.
Track history in one go. Need to know every movement? Use get_account_transactions for a full list, and then use get_account_internal_transactions to trace deeper calls the contract made.
Verify chain health immediately. Before running complex queries, check the status with get_indexing_status to make sure your data source is up-to-date.
Access raw power when needed. If a specific function call isn't covered by a dedicated tool, you can fall back on json_rpc to execute any standard Ethereum RPC method.
See it in action
A client needs a full portfolio audit.
The analyst asks the agent for all holdings at address X. The agent uses list_token_balances, returning counts for USDT, LINK, and NFTs simultaneously. This replaces manually checking five different smart contract endpoints.
A developer needs to debug a failed transaction.
The dev provides the failing transaction hash. The agent uses get_transaction to check the gas usage and status, then runs get_logs to see exactly which event triggered the failure.
A researcher needs contract details for a paper.
The researcher asks about Contract Y. The agent uses get_contract_source_code and get_contract_abi, providing both the code and the required interface definitions in one response.
Monitoring institutional movements.
The team leader submits a list of addresses to check. The agent uses get_account_balance for each, quickly compiling a report showing current ETH holdings for multiple high-profile wallets.
The honest tradeoffs
Over-relying on generic API calls.
Trying to use json_rpc when all you really need is a simple token balance check. This adds complexity and forces manual input of obscure method names.
Always check for specific tools first. If you just want balances, use list_token_balances. For a single native coin balance, stick to the dedicated get_account_balance tool.
Confusing transaction types.
Getting confused about whether an action is part of the main transaction or if it happened internally within a contract call. You end up missing crucial context.
Don't just use get_account_transactions. Always follow up with get_account_internal_transactions to trace all calls made by the contract.
Assuming data completeness.
Asking for a balance without checking if the explorer is current, leading to stale or incorrect financial data being used in decisions. This is dangerous.
Always start by running get_indexing_status when analyzing critical data sets. Verify the source before trusting the numbers.
When It Fits, When It Doesn't
Use this MCP if your work requires querying verifiable, immutable blockchain state—specifically balances, contract logic, or transaction history. It's perfect for developers who need to call get_contract_abi and data analysts needing to list token balances across multiple standards. Don't use it if you just need general market sentiment or news updates; those are unstructured tasks. If your goal is simply to calculate a total supply, the dedicated get_total_supply tool handles that cleanly. But if you need something truly custom—like running a unique calculation not covered by an existing function—then jump straight to json_rpc. It’s powerful, but it requires knowing exactly what RPC method you're calling.
Questions you might have
How do I find out if an address holds NFTs using list_token_balances? +
The list_token_balances tool covers all token types, including ERC-721s and ERC-1155s. It returns a grouped list that tells you exactly how many non-fungible tokens the address owns.
Can I get contract source code using get_contract_source_code? +
Yes, get_contract_source_code pulls the original code from the explorer. This is critical for verifying that a deployed contract matches its intended design.
What's the difference between get_account_transactions and get_account_internal_transactions? +
Use get_account_transactions to see every transaction initiated by the address. Then, use get_account_internal_transactions to trace any calls made by contracts that were called during those transactions.
Should I use get_transaction or json_rpc for raw data? +
get_transaction is best for viewing a specific, known transaction's status and gas. Use json_rpc only when you need to execute an obscure, standard Ethereum method not covered by the dedicated tools.
How do I check rate limits or increase my query allowance when using `get_account_balance`? +
You improve your rate limits by providing a dedicated API Key during setup. This key authenticates you and allows the MCP to make more requests without hitting standard usage caps. Use this if you plan on running large-scale audits or querying many addresses.
What does `get_indexing_status` tell me about the data I'm pulling? +
This tool confirms whether the Blockscout instance is fully synced with the blockchain. If the status reports 'synced,' you know that all transaction and block data up to the latest confirmed height is available for querying.
Does `get_address` give me more details than just a native coin balance? +
Yes, it provides key metadata about an address. Beyond the current native balance, you get essential data points like its associated ENS name and the total count of transactions linked to that wallet.
If a specific tool doesn't exist, can I still query custom methods using `json_rpc`? +
Absolutely. The json_rpc tool lets you execute any standard Ethereum JSON-RPC 2.0 method directly. This gives you access to niche or highly specialized data calls not covered by the predefined tools.
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.
We've already built the connector for Blockscout. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 14 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.