# Wemix Explorer MCP

> 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.

## Overview
- **Category:** developer-tools
- **Price:** Free
- **Tags:** wemix, blockchain-explorer, web3, crypto-tracking, smart-contracts

## Description

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.

## Tools

### 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_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 and data payload.

### list_extrinsics
Lists the hashes and summaries of the most recent transactions (extrinsics) on the chain.

### 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.

## Prompt Examples

**Prompt:** 
```
Show me the latest blocks on the Wemix network.
```

**Response:** 
```
I've retrieved the latest blocks. The most recent block is #14502134, produced 6 seconds ago with 12 extrinsics. Would you like to see the details of a specific block?
```

**Prompt:** 
```
What tokens are held by the address 0x742d35Cc6634C0532925a3b844Bc454e4438f44e?
```

**Response:** 
```
Checking the wallet... This account holds 500 WEMIX, 1,200 WEMIX$, and 50 stWEMIX. I can also list the recent transfers for this address if you'd like.
```

**Prompt:** 
```
Get details for extrinsic hash 0x123...abc
```

**Response:** 
```
Extrinsic 0x123...abc was finalized in block #14502100. It was a 'balances.transfer' call from address A to address B. The status is 'Success'.
```

## Capabilities

### Check account details
Get basic information and current balances for any specific Wemix address.

### List token holdings
Retrieve a complete list of all different tokens associated with an account.

### Track historical transfers
Pull a record of every transfer made or received by a specific address over time.

### Inspect network blocks
Fetch detailed data about entire blocks, including the block height and hash for deep analysis.

### View contract activity
Analyze specific transactions (extrinsics) or events to understand how smart contracts changed state.

### Monitor token availability
Get a full list of all tokens that currently exist and operate on the Wemix network.

## Use Cases

### 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.

## Benefits

- 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.

## How It Works

The bottom line is: you talk naturally, and the MCP returns verifiable, structured ledger data.

1. First, subscribe to this MCP and enter your required Wemix API key.
2. Next, connect your AI agent from any compatible client like Cursor or Claude. The connection routes the credentials through a secure zero-trust proxy.
3. Finally, prompt your agent with natural language (e.g., 'What tokens does address X hold?') to get structured blockchain data back.

## Frequently Asked Questions

**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.