Wemix Explorer MCP for AI. Query accounts and track every token transfer.
Works with every AI agent you already use
…and any MCP-compatible client








How this MCP server connects to your AI agent
Wemix Explorer connects your agent directly to the Wemix blockchain ledger. You can audit specific accounts, track every token movement, and inspect block data without opening a separate web explorer.
It gives you structured access to historical transfers, smart contract events, and network details using natural language prompts.
What AI agents can do with Wemix Explorer Automation
Get account info
Retrieves core details, balances, and basic information for a single Wemix account address.
List account tokens
Generates a full list of all different types of tokens currently held by an account address.
List account transfers
Provides a chronological record of every transfer associated with the specified account.
Get basic information and current balances for any specific Wemix address.
Retrieve a complete list of all different tokens associated with an account.
Pull a record of every transfer made or received by a specific address over time.
Fetch detailed data about entire blocks, including the block height and hash for deep analysis.
Analyze specific transactions (extrinsics) or events to understand how smart contracts changed state.
Get a full list of all tokens that currently exist and operate on the Wemix network.
Ask an AI about this
Waiting for input…
What AI agents can do with Wemix Explorer: 11 Tools
These tools give your agent deep access to the Wemix network's ledger, allowing you to query everything from account details and token lists to specific block events.
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 Wemix Explorer on VinkiusGet Account Info
Retrieves core details, balances, and basic information for a single Wemix account address.
List Account Tokens
Generates a full list of all different types of tokens currently held by an account...
List Account Transfers
Provides a chronological record of every transfer associated with the specified...
Get Block
Pulls detailed data for one specific block using its hash or height number.
List Blocks
Grabs a list of recent block hashes and heights for an overview of network activity.
Get Event
Retrieves details on a single recorded event, typically from a smart contract interaction.
List Events
Fetches a paginated list of the most recent smart contract events that occurred on the network.
Get Extrinsic
Gets full information for a specific transaction (extrinsic), including its status...
List Extrinsics
Lists the hashes and summaries of the most recent transactions (extrinsics) on the...
Get Token
Fetches detailed metadata about one particular token using its symbol or ID.
List Tokens
Gets a full list of all token contracts available across the entire Wemix network.
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 Wemix Explorer, 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 Wemix Explorer. 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 11 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Sifting through web explorers takes hours of clicking., Solved with Vinkius AI Gateway
Today, checking an account's history means opening a blockchain explorer. You find the address, then you hit 'Transfers.' If you want to know which tokens were involved, you have to open another tab and query the token list separately. It’s clicking through five different pages just to piece together one person's activity.
With this MCP, your agent does the heavy lifting. You ask it to audit an address, and it pulls every relevant data point—balances, transfers, and even contract interactions—and hands it back in a single, clean response.
Getting structured event details with `get_event`
Without this tool, finding out what triggered a specific state change is nearly impossible. You see the transaction happened, but you don't know *why*. You waste time trying to cross-reference block numbers and contract IDs.
Now, your agent uses `get_event` to pinpoint that exact moment in time. It tells you precisely what was triggered by a smart contract—what data left or entered the system—without needing any manual joins.
What your AI can actually do with this
This MCP lets your AI client query the entire Wemix Network directly. Instead of manually clicking through web explorers to find an account's history or a specific transaction detail, you ask your agent, and it pulls the raw data instantly. You can check account balances, list all tokens held by an address, track recent transfers, and even dive into block details.
This makes complex blockchain analysis as simple as asking a question.
It handles everything from querying the full list of available network tokens to pinpointing specific smart contract interactions via events or extrinsics. When your agent fetches this data, every call generates a cryptographically signed audit trail. This means you know exactly who requested the data and when it was pulled—it's tamper-proof by design.
You can build complex workflows that span multiple platforms, chaining this blockchain read with other services through Vinkius, all while maintaining verifiable data integrity.
019e5d67-691b-7347-9c85-912e515e5471 Here's how it actually works
The bottom line is: you talk naturally, and the MCP returns verifiable, structured ledger data.
First, subscribe to this MCP and enter your required Wemix API key.
Next, connect your AI agent from any compatible client like Cursor or Claude. The connection routes the credentials through a secure zero-trust proxy.
Finally, prompt your agent with natural language (e.g., 'What tokens does address X hold?') to get structured blockchain data back.
Who is this actually for?
Web3 Developers and Crypto Analysts need this. If you're tired of manually switching between terminal commands, web explorers, and spreadsheets just to track a single token flow, this is for you.
Debugging smart contracts or verifying event logs directly from your IDE without leaving your coding environment.
Tracking large movements of funds (whale activity) and identifying token distribution patterns via natural language prompts.
Monitoring block production rates and network event logs without needing to run complex CLI commands manually.
What Changes When You Connect
Stop juggling multiple tabs. You can pull a list of all available tokens using list_tokens and then get specific metadata for any asset with get_token. It keeps everything in one conversation.
Track complex money movements instantly. Instead of reviewing raw logs, you can use list_account_transfers to see who sent what, where, and when, all through natural language.
Analyze deep contract interactions. If you need to know why a specific state changed, use get_extrinsic or get_event. It pulls the exact data needed for debugging.
See network activity at a glance. Use list_blocks and list_events together to get a rapid overview of recent network health without running dedicated monitoring tools.
Get comprehensive account visibility. By calling list_account_tokens, you don't just see the balance; you see every different asset held by that address.
See it in action
Investigating an unknown token movement
A user notices a suspicious transfer. They ask their agent to run list_account_transfers for the receiving wallet, then use get_extrinsic on the transaction hash to see if it was part of a larger contract interaction.
Auditing initial token deployment
A developer wants to check if a new asset is properly registered. They call list_tokens first, then use get_token with the suspected symbol to confirm its metadata and contract address.
Tracking smart contract failures
A user suspects a recent transaction failed due to bad logic. They ask their agent to check list_extrinsics, identify the hash, and use get_extrinsic to see the failure status and associated error message.
Mapping network growth
A crypto analyst wants to understand overall usage. They call list_blocks for a time range, then combine that data with calls to get_event across several blocks to map out the activity of major smart contracts.
The honest tradeoffs
Reading raw block hashes
A user tries to paste a raw block hash into a generic search engine and manually cross-reference it with a separate token list.
Just use your agent. Tell it, 'Give me the details for this block hash.' The get_block tool handles all that complex data retrieval in one step.
Confusing transfer types
A user only sees a balance decrease but doesn't know if it was a direct transfer or a contract interaction.
Don't just check balances. Use list_account_transfers and follow up with get_extrinsic to see the full context of that change.
Over-relying on web UI pagination
A user has to click 'next page' four times just to get a year's worth of transfer data.
Ask your agent directly. It handles the bulk retrieval, using tools like list_account_transfers to pull the entire history you need in one go.
When It Fits, When It Doesn't
Use this MCP if your goal is pure, read-only analysis of historical ledger data—you're tracking balances, transfers, or contract events. For example, you should use list_account_transfers when you need a history timeline, but don't use it to check current balances; for that, get_account_info is faster and simpler. If your goal involves changing data (sending tokens, updating records), this MCP won't help—you need an execution-focused tool instead. Always start with the broadest list available (list_blocks, list_tokens) to scope your query before drilling down into specifics like get_event.
Questions you might have
How do I check all tokens held by an address using list_account_tokens? +
You simply ask your agent to run list_account_tokens against the target address. It returns a full manifest of every token type, not just the primary currency balance.
Is get_block the same as list_blocks? +
No. list_blocks gives you a summary and recent list of blocks. You use get_block when you want all the deep details—the full transaction list, metadata, and content—for one specific block hash.
Can I find out if a transfer was successful using get_extrinsic? +
Yes. You feed get_extrinsic the transaction hash, and it reports the status directly. It tells you if the action succeeded or failed and why.
What is the difference between list_events and get_event? +
Using list_events gives you a summary of recent events across the network. You use get_event to drill down into one specific event's payload for full context.
What kind of API key do I need to run queries with `list_extrinsics`? +
You'll need a valid Wemix/Subscan API Key. You enter this key into Vinkius before querying; it authorizes your agent to access the blockchain data securely. This setup keeps your credentials in transit and never stores them on disk.
Does `get_account_info` show all historical transfers or just current balances? +
It only provides basic, real-time account details like the current balance. For a history of movements, you must use list_account_transfers, which pulls out the full list of past transactions associated with that address.
If I try to pull too many records using `list_blocks` or `list_events`, will I hit a limit? +
Yes, all listing tools enforce rate limits and pagination. If you request more data than the default page size, your agent will need to make subsequent calls with the specific cursor or hash provided in the previous response.
If I want to see all possible assets on the network, should I use `list_tokens` or `get_token`? +
List_tokens pulls a complete roster of every token currently available on the Wemix network. Use that tool first to get metadata for all assets; then, if you know a specific symbol or ID, run get_token to pull its detailed information.
Can I check the token balances for a specific wallet address? +
Yes. Use the list_account_tokens tool by providing the account address. The agent will return a list of all tokens held by that account on the Wemix network.
How do I get details about a specific transaction hash? +
You can use the get_extrinsic tool with the transaction hash. It will provide detailed information including status, block number, and associated events.
Is it possible to list the most recent blocks on the network? +
Absolutely. The list_blocks tool allows you to retrieve a list of recent blocks, and you can use get_block with a block number to see specific details of any block.
We've already built the connector for Wemix Explorer. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 11 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.