IoTeX Block Explorer API MCP for AI. Query account history and token ownership instantly.
Works with every AI agent you already use
…and any MCP-compatible client








How this MCP server connects to your AI agent
IoTeX Block Explorer API MCP gives you direct access to real-time IoTeX network data. Query account balances, transaction histories, specific blocks by hash or height, and token metadata (XRC20/XRC721).
Your AI agent acts as a built-in blockchain analyst, eliminating the need for manual web explorer navigation. Check accounts with `get_account`, review past activity using `get_account_actions` or `get_action`, and analyze asset ownership by fetching token details via `get_token` or listing holders with `get_token_holders`.
It’s instant blockchain intelligence, right in your chat interface.
What AI agents can do with IoTeX (IoTeX Block Explorer API) Automation
Get account actions
Fetches a list of all historical transactions associated with an account's address.
Get account
Retrieves the current balance, nonce, and basic details for a specified IoTeX address.
Get action
Retrieves specific details about a single transaction or action using its unique hash.
Retrieve an address's current balance, nonce count, and basic data using get_account.
Fetch a list of all past actions on an address with get_account_actions, or look up details for one specific action by its hash using get_action.
Get full details about a blockchain block using either the block's height number (get_block_by_height) or its unique cryptographic hash (get_block_by_hash).
See what’s happening right now by retrieving a list of the most recent transactions and activity across the entire IoTeX network using get_recent_actions.
Get metadata for specific tokens (XRC20/XRC721) via get_token, or list all addresses that currently hold those tokens using get_token_holders.
Ask an AI about this
Waiting for input…
What AI agents can do with IoTeX (IoTeX Block Explorer API) With 8 Tools
These eight tools allow your agent to query every fundamental aspect of the IoTeX blockchain state, from account balances to token ownership.
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 IoTeX (IoTeX Block Explorer API) on VinkiusGet Account Actions
Fetches a list of all historical transactions associated with an account's address.
Get Account
Retrieves the current balance, nonce, and basic details for a specified IoTeX...
Get Action
Retrieves specific details about a single transaction or action using its unique...
Get Block By Hash
Gets all data for a blockchain block when you provide its full cryptographic hash.
Get Block By Height
Retrieves the details of a specific blockchain block using only its numerical height...
Get Recent Actions
Pulls a feed containing the latest transactions and activity across the entire IoTeX network.
Get Token Holders
Lists all the addresses that currently own tokens associated with a specified contract.
Get Token
Retrieves specific metadata (total supply, decimals) for a given token contract...
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 IoTeX (IoTeX Block Explorer API), 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 IoTeX. 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
Built on the Model Context Protocol (MCP) for 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 8 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Manually cross-referencing blockchain records takes forever., Solved with Vinkius AI Gateway
Today, figuring out what an address did last month is a painful process. You start on the main explorer site to check the balance, then you copy the transaction hash and paste it into a secondary 'action viewer.' If you want token details, you have to find the contract address, open yet another tab, and manually cross-reference supply data against holder lists. It's a massive amount of copying, clicking, and context switching.
With this MCP, your agent handles the whole sequence. You just prompt it with the question—for example, 'What happened with this token?' Your AI client uses `get_token` for metadata and then calls `get_token_holders` automatically to give you the full answer without any manual switching. The result lands cleanly in your chat window.
Get all necessary data points using IoTeX Block Explorer API MCP
The tedious work of gathering related facts—like linking a block's height to the recent actions on that chain, or correlating an account balance with its historical transactions—is gone. You no longer have to manually check `get_block_by_height` and then cross-reference those details against `get_account_actions`. The agent stitches it together.
What's different now is efficiency. Instead of spending time navigating multiple specialized web tools, you get one unified data stream from your AI client that synthesizes the full blockchain picture.
What your AI can actually do with this
This connector lets you treat the IoTeX blockchain like a database. Instead of clicking through dozens of web pages just to find a balance or confirm a transaction detail, your AI agent gets the answer instantly. You can ask it for account details and get balances, nonces, and metadata in one go.
Want to know what happened with an address over the last week? Just ask, and you’ll pull up all associated actions. Need to check if a specific token contract is valid or who owns its supply? The MCP handles that too. It lets your agent query detailed block data by height or hash, keeping track of network activity using recent action feeds.
Connecting this IoTeX Block Explorer API through Vinkius makes it available across any AI client you use; your agent just needs the prompt. No more copy-pasting hashes into separate websites. You get a unified view of the entire chain state.
019e5d27-89cf-7327-a5e2-fcc6d699739b Here's how it actually works
The bottom line is that your AI client handles all the complex API calling logic so you just need to chat with it.
Connect your AI client to this MCP and optionally provide an IoTeX API Key for higher rate limits.
Direct your agent with a prompt: 'What is the balance and history for address X?'
The agent calls the necessary tools (e.g., get_account then get_account_actions) and returns structured, actionable data directly to you.
Who is this actually for?
This MCP targets anyone who needs verifiable, deep blockchain data without manually navigating web explorers. If you spend time cross-referencing transaction hashes or confirming token ownership across different sites, this is for you.
Needs to quickly verify transaction statuses and account balances directly from their IDE while coding.
Requires bulk extraction of block or token holder data for research, reporting, or modeling purposes.
Needs to monitor network activity and analyze complex token metadata through simple chat commands without leaving their workflow.
What Changes When You Connect
Stop juggling tabs. Instead of checking the main explorer site for a balance, use get_account to pull real-time data directly into your chat session. It keeps your workflow contained.
Audit activity in depth. If you suspect an account was involved in something last week, don't scroll through pages. Call get_account_actions or pinpoint the exact moment with get_action using a known hash.
Stay current on network health. You can monitor what’s happening right now by calling get_recent_actions, giving you an immediate pulse check of the entire IoTeX chain without waiting for manual updates.
Master asset tracking. To understand token ownership, use get_token to get contract details, then follow up with get_token_holders to see who holds the supply.
Navigate blocks easily. Need to check a block from two weeks ago? You don't need to search by date; just tell your agent to grab it using get_block_by_height or get_block_by_hash.
See it in action
Verifying a complex transfer chain
A researcher needs to confirm if funds moved from Account A, through an intermediary contract, and landed in Address B. They ask their agent: 'What did account A do recently?' The agent uses get_account_actions to find the initial transaction hash, then uses get_action on that hash to trace the flow and get the final details.
Checking asset distribution for an ICO
A project founder wants to know who holds a specific token (TKN) after a sale. They ask their agent to analyze TKN's contract address, triggering get_token first, and then immediately calling get_token_holders to generate the complete list of owners.
Debugging an outdated record
A developer gets a strange error about a block. Instead of manually searching by date on a web explorer, they ask their agent for data at height 31054201. The agent uses get_block_by_height and returns the exact JSON data needed to debug the application.
Assessing immediate network risk
A trading bot owner wants a real-time feed of major movements before running a script. They ask their agent, 'Show me all activity in the last hour.' The agent uses get_recent_actions to provide an instant overview of transfers and smart contract calls.
The honest tradeoffs
Treating it like a single API call
Asking 'Give me everything about this address.' The agent can't give one answer because the data is split between current status, historical actions, and token ownership.
Break it down. First, use get_account for the balance. Then, follow up with get_account_actions to see history, and finally, specify which tokens you need by using get_token.
Ignoring block context
Just looking at a transaction hash (get_action) without knowing the surrounding data. You might miss details about what block it actually belongs to.
If you know the timeframe, try calling get_block_by_height first. This establishes the context for all subsequent actions and helps verify if your transaction is valid.
Over-relying on one tool
Only using get_token to check the total supply, but not knowing which addresses actually hold it.
After getting token metadata with get_token, always run get_token_holders. This moves you from knowing what exists to knowing who owns it.
When It Fits, When It Doesn't
Use this MCP if your job involves tracing state dependencies—meaning the answer relies on checking multiple, interconnected data points. You must check account balances (get_account), verify historical movement using get_account_actions, and confirm asset ownership with get_token and get_token_holders. Don't use it if you only need a single piece of static information, like just the date or name of an address; in that case, simple database lookups are faster. You absolutely must use this MCP if you need to know why something happened (the actions) and not just that it happened (the balance). If your goal is simply to browse a known block's content, get_block_by_hash is sufficient. But if the flow involves checking current activity against historical data, this tool set provides all necessary functions.
Questions you might have
How do I check an account balance using get_account? +
You simply ask your agent for the details of a specific IoTeX address. The agent calls get_account and returns the current balance, nonce, and metadata immediately.
What is the difference between get_account_actions and get_action? +
get_account_actions fetches a list of all activities for an entire address. Use get_action when you already know the specific transaction hash and need details on just that single event.
Can I find out who owns a token using get_token_holders? +
Yes, calling get_token_holders requires you to first provide the contract address. This tool lists all addresses currently holding tokens for that specific contract.
Do I need get_block_by_hash or get_block_by_height? +
Use get_block_by_hash when you have the block's unique ID. Use get_block_by_height if you only know that the block occurred at a specific numerical height count.
How do I handle rate limits when querying account data using get_account? +
You need to provide your IoTeX API Key for higher capacity. While basic queries work with the default settings, including a key significantly increases your query volume and stability.
What specific token metadata can I retrieve using the get_token tool? +
The tool fetches essential contract data, including the total supply and the decimal count. This lets you verify a token's specifications before running holder analyses.
How real-time is the activity information provided by get_recent_actions? +
This MCP connects directly to the live explorer feed, meaning the actions are near real-time. You can monitor network changes within seconds of them appearing on IoTeX.
What happens if I use get_action with a transaction hash that doesn't exist? +
The tool will return a specific error message indicating the hash is invalid or not found. You simply adjust your input query and resubmit to check another action.
How can I see the transaction history for a specific IoTeX address? +
You can use the get_account_actions tool. Simply provide the IoTeX address, and the agent will return a list of recent actions (transactions) associated with that account.
Can I look up block details if I only have the block height? +
Yes! Use the get_block_by_height tool and provide the numeric height. The agent will fetch the full block details including hash, timestamp, and transaction count.
Is it possible to see who the top holders of a specific token are? +
Yes, by using the get_token_holders tool with the token's contract address, you can retrieve a list of addresses that currently hold that specific XRC20 or XRC721 token.
We've already built the connector for IoTeX Block Explorer API. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 8 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.