IoTeX Block Explorer API MCP. Query IoTeX accounts, blocks, and tokens via natural chat.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
IoTeX (IoTeX Block Explorer API) connects your AI agent directly to the IoTeX blockchain. Query account balances, transaction history, block data, and token metadata using natural conversation.
Your agent acts as a live blockchain analyst, retrieving real-time data on addresses, blocks, and tokens without needing to open a web explorer.
What your AI agents can do
Get account
Gets the current balance, nonce, and basic metadata for a specific IoTeX account address.
Get account actions
Retrieves a full list of actions and transactions tied to a specific account address.
Get action
Fetches detailed information for a single transaction using its unique hash.
Retrieves the current balance, nonce, and basic metadata for any specified IoTeX address.
Retrieves a full list of all recorded actions and transactions associated with a specific account address.
Fetches detailed data for a single transaction using its unique hash.
Retrieves all data for a block, either by its sequential height or its unique hash.
Gets a list of the most recent transactions and actions occurring across the entire IoTeX network.
Retrieves metadata, total supply, and contract information for specific XRC20/XRC721 tokens.
Lists the addresses that currently hold a specified token.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
IoTeX Block Explorer API: 8 Tools for Blockchain Data
Use these eight tools to query IoTeX data, covering everything from individual account balances to entire block contents and token ownership.
019e5d27get account
Gets the current balance, nonce, and basic metadata for a specific IoTeX account address.
019e5d27get account actions
Retrieves a full list of actions and transactions tied to a specific account address.
019e5d27get action
Fetches detailed information for a single transaction using its unique hash.
019e5d27get block by hash
Retrieves all data for a block using its cryptographic hash.
019e5d27get block by height
Retrieves all data for a block using its sequential block height number.
019e5d27get recent actions
Gets a list of the most recent transactions and actions across the IoTeX network.
019e5d27get token
Retrieves metadata and supply details for a specified XRC20/XRC721 token contract.
019e5d27get token holders
Lists the addresses that currently hold a specified token contract.
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 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
Yo, this MCP server hooks your AI client right into the IoTeX blockchain. You'll be able to ask it to check account balances, look at transaction histories, and pull token info—all without opening a web browser. Your agent acts like a live blockchain analyst, pulling real-time data on addresses, blocks, and tokens straight into your workflow.
To check an account's status, use get_account to grab the current balance, nonce, and basic metadata for any IoTeX address. To see an account's history, run get_account_actions to get a full list of every recorded action and transaction tied to that address. You can also dig into a single transaction's details using get_action with its unique hash.
When you're dealing with blocks, you've got two ways to get the scoop: use get_block_by_height to fetch all data for a block based on its sequential height number, or use get_block_by_hash with the block's cryptographic hash. To monitor what's happening network-wide, get_recent_actions gives you a list of the most recent transactions and actions across the whole IoTeX network.
And for tokens, you can get the rundown on specific XRC20/XRC721 tokens—metadata, total supply, and contract info—by running get_token. You can also list every address that holds a specific token contract using get_token_holders.
Your agent handles all the heavy lifting. You just talk to your AI client, and it uses these tools to pull the structured data you need.
How IoTeX Block Explorer API MCP Works
- 1 Subscribe to the IoTeX MCP Server and provide the necessary API credentials.
- 2 Prompt your AI client to identify the data needed (e.g., 'What was the balance of address X?').
- 3 The agent selects and executes the correct tool (e.g.,
get_account), receiving structured IoTeX data that it presents back to you.
The bottom line is: you talk to your agent, and it runs the blockchain queries for you, giving you instant, structured results.
Who Is IoTeX Block Explorer API MCP For?
Web3 developers and data analysts who spend too much time jumping between web explorers and code editors. This tool saves you from manually copy-pasting hashes and digging through dashboards. You get structured, programmatic access to IoTeX data, making complex queries part of your normal development flow.
Verifies transaction statuses and account balances directly within the code editor without leaving the IDE.
Extracts bulk block and token holder data for research, reporting, and building analytical models.
Monitors network activity and analyzes token metadata to track market trends and address movements.
What Changes When You Connect
- Instant Account Status: Use
get_accountto immediately check a user's balance and nonce. No more waiting on slow web explorer API calls—it's instant, structured data right in your agent's response. - Deep History Tracking: Instead of skimming a dashboard, run
get_account_actionsto pull the complete, chronological list of every action on an address. Then, useget_actionto deep-dive into any single transaction hash. - Full Block Context: Need to know what happened at a specific time? Use
get_block_by_heightorget_block_by_hashto pull the entire block contents. This gives you the full context for research. - Token Ownership Mapping: Use
get_tokento get the contract metadata, andget_token_holdersto instantly list who owns the token. This is key for asset tracking. - Network Pulse Check: Use
get_recent_actionsto monitor the network's current activity level. It shows you the latest transfers and contract executions without needing to filter a massive feed. - Efficiency: By channeling all these functions through your AI client, you eliminate manual API calls and data parsing, making multi-step queries feel like a single conversation.
Real-World Use Cases
Tracking a User's Full Lifecycle
A security analyst needs to verify an address's full history. They prompt their agent: 'Start by getting the current status of address X using get_account. Then, run get_account_actions to pull the last 50 transactions. Finally, use get_action on the most suspicious hash to get full details.' The agent runs the sequence and hands over a clean report.
Investigating a Token's Market Footprint
A crypto researcher wants to know the market size of a new token. They first use get_token to confirm the contract details. Next, they call get_token_holders to get the list of owners. If they need to see who recently moved tokens, they can cross-reference the data with get_recent_actions.
Debugging a Smart Contract Failure
A developer finds a failed transaction. They use get_action with the transaction hash. If the failure relates to the block itself, they use get_block_by_hash to inspect the surrounding block context, diagnosing the issue without leaving the IDE.
Monitoring General Network Health
A developer needs a quick overview of the IoTeX network's current activity. They simply ask the agent to check the 'latest actions' using get_recent_actions. This provides a quick pulse check, saving them from manually pulling data from multiple sources.
The Tradeoffs
Over-querying for history
Asking the agent to run get_account_actions and then asking for the same data again, or running get_account multiple times just to check the balance.
→
To check the current status, just call get_account. For history, always use get_account_actions—it's designed to pull the full list. If you need a single specific transaction, use get_action with the hash.
Confusing block context
Trying to find a transaction's surrounding data by just asking for 'the block' without specifying a hash or height.
→
You must specify. If you know the hash, use get_block_by_hash. If you know the sequence number, use get_block_by_height. Don't leave it ambiguous.
Ignoring token types
Assuming that running get_token will give you holder data, only to find out it's missing the list of addresses.
→
Remember the tools' roles: get_token gives you the contract metadata. You must follow up with get_token_holders to actually get the list of addresses that own it.
When It Fits, When It Doesn't
Use this server if your workflow requires programmatic, structured access to IoTeX's core data layers—account state, transaction history, or token ownership. Specifically, if you need to chain together calls, like checking an address's balance (get_account) and then immediately listing its transactions (get_account_actions), this is built for you.
Don't use this if you only need a quick visual check on a public website, or if your data needs are highly specialized (e.g., querying gas prices, which isn't included). For simple, single-point lookups, your AI client might suffice, but for complex, multi-step data retrieval, this toolset is necessary.
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
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 8 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Sifting through web explorer dashboards takes forever.
Today, checking an address's history means jumping to a separate block explorer tab. You manually search for the address, scroll through pages of transactions, and then copy the hash of the one you care about into a second tool to get details. It's a three-step, copy-paste nightmare.
With the IoTeX Block Explorer API, you just tell your agent to check the address. It handles the entire sequence—getting the account state, fetching the full action list, and providing the structured data you need—all in one prompt. You get clean JSON, not a screenshot.
IoTeX Block Explorer API MCP Server: Get token details and holder lists.
Before, finding out who owned a specific token involved multiple lookups: one query for the contract, another to confirm its type, and a third to get the list of addresses. It was slow and error-prone.
Now, your agent handles it. You ask for the token details, and the system pulls the metadata using `get_token`. Then, you ask for the owners, and it runs `get_token_holders`. The whole process is reliable and instantaneous.
Common Questions About IoTeX Block Explorer API MCP
How do I get the latest transactions on the IoTeX network using `get_recent_actions`? +
You simply ask your agent to 'Show me the recent actions.' The get_recent_actions tool pulls the latest transfers and contract executions directly, giving you a clean, structured list of activity.
Do I need to use `get_account_actions` or `get_action` for transaction history? +
Use get_account_actions when you need the full history for one specific address. Use get_action only when you have the exact transaction hash and want detailed information on that single event.
Can I check a block's data by its height or its hash? +
Yes, the server provides two tools: get_block_by_height for sequential numbering, and get_block_by_hash for the specific cryptographic identifier.
What is the best way to find out who holds a specific token? +
Run get_token_holders with the token's contract address. This tool explicitly returns the list of addresses that currently hold that token.
How do I check an account's current balance and metadata using the `get_account` tool? +
The get_account tool retrieves the account's current balance and metadata. It requires the IoTeX address, and it also returns the current nonce, which is crucial for sending transactions.
If I want to analyze a specific token's ownership, should I use `get_token` or `get_token_holders`? +
Use get_token first to verify the token's contract address and metadata. Then, use get_token_holders to list the addresses that currently hold that token.
What if I need to find a block's data using a hash, but only have the height number? +
You must use get_block_by_height with the block number. If you have the hash, use get_block_by_hash directly. The tools handle these two distinct inputs.
How do I check if a specific transaction hash has already been processed using `get_action`? +
Simply run get_action with the transaction hash. The tool confirms if the action exists on the network and provides its final status and details if it has been completed.
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.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Camunda (BPMN Engine)
Orchestrate business processes via Camunda — deploy BPMN models, start instances, and manage user tasks directly from any AI agent.
AI21 Studio
Unlock AI21's Jamba models and language tools for summarizing, paraphrasing, and grammar correction natively.
Hanko (Passkey Auth)
Manage passkey authentication and user identity via Hanko — initialize registrations, handle logins, and manage WebAuthn credentials directly.
You might also like
Storylane
Interactive, personalized product demos.
Zendesk Sell
Manage sales leads, contacts, and deals via the Zendesk Sell (Base CRM) API.
Vonage Alternative
Manage your Vonage communications — send SMS and audit account data via AI.