Bobascan MCP. Analyze Boba L2 data directly from your AI client.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Bobascan (Boba L2 Network Block Explorer API) provides direct access to Boba L2 blockchain data. Your AI agent can query Ether balances for single or multiple addresses, list transaction histories (normal, internal, token transfers), and inspect smart contract source code and ABIs.
It also fetches network stats like current gas prices and total ETH supply, letting you analyze the chain right from your AI client.
What your AI agents can do
Get abi
Retrieves the Application Binary Interface (ABI) for a contract's verified source code.
Get block countdown
Calculates the estimated time remaining until the next block is mined.
Get block reward
Retrieves the reward amount for a specific block number.
Get the current ETH balance for one or many addresses on the Boba L2 network.
Fetch a list of normal transactions, internal contract calls, or specific token transfers for an address.
Retrieve the ABI and verified source code for a smart contract address.
Get the balance, total supply, or transfer list for specific ERC20 and ERC721 tokens.
Fetch live data points like gas prices, block rewards, or the total ETH supply.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
Bobascan API Server: 25 Tools for Blockchain Data
Access every function for the Boba L2 network, from checking ETH balances to inspecting raw contract source code. Use these tools to run deep blockchain analysis via your AI agent.
019e5d01get abi
Retrieves the Application Binary Interface (ABI) for a contract's verified source code.
019e5d01get block countdown
Calculates the estimated time remaining until the next block is mined.
019e5d01get block reward
Retrieves the reward amount for a specific block number.
019e5d01get contract execution status
Checks if a contract's execution finished successfully or failed.
019e5d01get eth price
Gets the current market price of Ether.
019e5d01get eth supply
Retrieves the total circulating supply of Ether on the Boba Network.
019e5d01get ether balance
Gets the current Ether balance for a single specified address.
019e5d01get ether balance multi
Gets the Ether balance for a list of multiple addresses.
019e5d01get logs
Retrieves all event logs emitted during a transaction.
019e5d01get source code
Retrieves the full source code for a contract's verified source code.
019e5d01get token balance
Gets the balance of a specific ERC20 token for an address and contract address.
019e5d01get token nft tx
Retrieves a list of ERC721 (NFT) token transfer events for an address.
019e5d01get token supply
Gets the total supply for a specific ERC20 token contract.
019e5d01get token tx
Retrieves a list of ERC20 token transfer events for an address.
019e5d01get tx list
Gets a list of all normal transactions associated with an address.
019e5d01get tx list internal
Gets a list of internal transactions within an address's history.
019e5d01get tx receipt status
Checks the final status and receipt of a specific transaction hash.
019e5d01proxy block number
Fetches the current or historical block number using the standard `eth_blockNumber` call.
019e5d01proxy call
Executes a general read-only call to the blockchain, like `eth_call`.
019e5d01proxy estimate gas
Estimates the gas required for a specific transaction or contract call.
019e5d01proxy gas price
Gets the current estimated gas price for the network.
019e5d01proxy get block by number
Retrieves all block details for a given block number.
019e5d01proxy get code
Gets the compiled bytecode of a contract at a specific address.
019e5d01proxy get transaction by hash
Retrieves full details for a transaction using its unique hash.
019e5d01proxy get transaction receipt
Gets the final transaction receipt, including status and logs, using a transaction hash.
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 Bobascan (Boba L2 Network 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 is your direct line to the Boba L2 blockchain data. Your AI client can act like a full-stack blockchain analyst, pulling real-time data straight from the Boba L2 explorer without you having to mess with RPC calls or jump between tabs. You just ask your agent, and it gets the info.
Check Ether Balances
'You wanna know what's in the wallet?' You can use get_ether_balance to check the current ETH balance for a single address. If you got a bunch of wallets to check, get_ether_balance_multi handles that, too. You can also use get_token_balance to check how much of a specific ERC20 token an address owns at a given contract.
For NFTs, you pull the transfer list with get_token_nft_tx.
Analyze Transaction Streams
'What's been going down with this address?' You can get a list of normal transactions using get_tx_list. You can also pull internal contract calls with get_tx_list_internal, and track specific token movements with get_token_tx for ERC20s or get_logs for all emitted events. You'll also get the full transaction history by running proxy_get_transaction_by_hash to grab all the details for a specific hash, and then proxy_get_transaction_receipt to see the final status and logs.
Inspect Contract Code
'How does this contract work?' You can check a contract's structure by getting its ABI with get_abi, or pull its verified source code with get_source_code. You can also get the raw bytecode using proxy_get_code and check the contract's logic status with get_contract_execution_status. To figure out the contract's rules, you can use get_contract_execution_status.
Track Token Movements
'Yo, where's the NFT went?' You can get the total supply of any ERC20 token with get_token_supply. You can also check the balance of a specific ERC20 token for an address and contract address using get_token_balance. For ERC721s, you get the transfer list using get_token_nft_tx.
Query Network Status
'Yo, what's the deal with the chain right now?' You can pull the current estimated gas price with proxy_gas_price, estimate gas costs for a transaction using proxy_estimate_gas, or check the total ETH supply with get_eth_supply. You can also get the current block number with proxy_block_number, and find out how many blocks are left until the next one is mined using get_block_countdown.
You can retrieve all block details for a specific block number using proxy_get_block_by_number, and figure out the reward amount for a block using get_block_reward.
Low-Level Calls
Need something raw? You can run proxy_call for general read-only calls like an eth_call. You can also fetch the full details of a transaction using its hash with proxy_get_transaction_by_hash, or grab the final receipt using proxy_get_transaction_receipt.
How Bobascan MCP Works
- 1 Subscribe to the server and enter your Bobascan API Key.
- 2 Your AI client sends a natural language request (e.g., 'What was the transaction history for X?').
- 3 The agent selects the right tool (e.g.,
get_tx_list) and executes the call, returning structured data to your client.
The bottom line is that your agent handles the complex API calls, so you just talk to it like you're talking to a person.
Who Is Bobascan MCP For?
Web3 developers, data analysts, and DeFi users who spend time checking blockchain dashboards. If you're tired of opening 15 tabs and manually copying data from block explorers, this is for you. It lets you automate forensic analysis and get data structured for immediate use.
Uses get_abi and get_source_code to pull contract logic and verify how a dApp interacts with a smart contract before deployment.
Automates the retrieval of token transfer lists (get_token_tx) and transaction histories (get_tx_list) for quarterly reporting and deep dives.
Checks wallet balances (get_ether_balance) and transaction statuses (get_tx_receipt_status) using natural language prompts.
What Changes When You Connect
- Check current balances instantly. Instead of visiting a dashboard, ask your agent to use
get_ether_balanceorget_ether_balance_multito get ETH holdings for dozens of addresses in one go. It saves the manual copy-pasting. - Deep dive into contract logic. Use
get_abiandget_source_codeto pull the contract's full logic and ABI right into your IDE. This lets you understand the underlying rules without leaving your coding environment. - Reconstruct transaction paths. You don't just see a list of hashes. You can use
get_tx_list(normal) andget_logsto see exactly which tokens moved and which internal contracts were called, mapping the full event flow. - Save time on network checks. Need to know if a transaction failed or what the gas cost will be? Use
get_contract_execution_statusorproxy_estimate_gasto check the status before you commit code. It stops wasted gas fees. - Track all asset types. Whether it's basic ETH (
get_ether_balance), an ERC20 token (get_token_balance), or an NFT (get_token_nft_tx), you can query the balance and history using the right specialized tool. - Understand the whole network state. Use
get_eth_supplyandproxy_gas_priceto get the current network metrics alongside the data, giving you a complete picture of the market conditions.
Real-World Use Cases
Investigating a Failed Smart Contract Call
A user finds a transaction failed. They ask their agent to check the status using get_tx_receipt_status. If it still isn't clear, the agent runs get_logs and get_abi. This combination reveals whether the failure was a logic bug (seen in the logs) or a gas limit issue (seen in the receipt).
Auditing Token Flows for a Client Report
A data analyst needs to prove how many times a specific token moved. They instruct their agent to run get_token_tx for a specific address. They then run get_tx_list to get the context of the transaction, compiling a complete, auditable report without leaving their terminal.
Checking Multiple Wallet Holdings
A DeFi user needs to check the balances of five different wallets. Instead of running five manual searches, the agent uses get_ether_balance_multi in a single call, immediately providing a consolidated view of all holdings.
Reverse Engineering a dApp's Interaction
A developer sees a transaction on the chain and needs to know what contract functions were used. They use proxy_get_transaction_by_hash to get the raw data, then use get_abi to decode the function calls, finally using get_source_code to understand the contract's full purpose.
The Tradeoffs
Manual Data Stitching
Copying the contract address from the block explorer, then opening a new tab to run get_abi, and another tab to run get_source_code. This is slow, error-prone, and breaks your flow.
→
Tell your agent to perform the analysis. It runs get_abi and get_source_code sequentially and presents the output together, letting you compare the two pieces of data instantly.
Ignoring Transaction Context
Just calling get_token_balance without knowing if the token was recently moved. You only get a number, but you don't know why the number is what it is.
→
First, run get_token_tx to see the recent movement events. Then, use get_token_balance to confirm the current holding. This gives you the full story, not just a single data point.
Over-relying on Single Calls
Running proxy_get_transaction_by_hash and assuming that's all you need. You get the hash, but you don't know if the funds were actually received or if the transaction failed after execution.
→
Always follow up by calling proxy_get_transaction_receipt and get_tx_receipt_status. This confirms the transaction actually succeeded and provides the necessary outcome details.
When It Fits, When It Doesn't
Use this if your task requires deep, multi-layered blockchain forensics. You need to establish not just what the balance is, but how it got there, and why a contract behaved a certain way. The server is perfect when you need to stitch together data points: e.g., 'Check the gas price, then get the ABI, then check the logs.'
Don't use this if you just need a simple number (like the current ETH price). For that, a dedicated, single-purpose API might be faster. Use this if you need the AI agent to coordinate between different data types—like linking a transaction hash to its associated token movements and the contract's source code.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Bobascan. 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 25 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Debugging a smart contract shouldn't feel like opening 15 tabs.
Before, debugging a smart contract meant hopping between the block explorer, the token tracker, and the gas price dashboard. You'd copy an address here, paste it there, wait for the page to load, and manually cross-reference the ABI with the transaction details. It was a slow, painful, multi-browser chore.
Now, you ask your agent to 'Check the contract status and ABI for this address.' It handles the calls to `get_contract_execution_status`, `get_abi`, and `get_source_code` and gives you the full package in one go. You get the data, structured and ready to read.
Get Token Balances with get_token_balance
Manual checking involves finding the token contract address, then querying the specific token balance page. You often have to guess which API endpoint is correct for the token type (ERC20 vs. ERC721).
With this server, you just tell your agent, 'What is the balance of token X at address Y.' It uses `get_token_balance` to fetch the precise data, eliminating the guesswork and the multi-step form filling.
Common Questions About Bobascan MCP
How do I check the total supply of Ether using get_eth_supply? +
Use the get_eth_supply tool. It immediately retrieves the total circulating supply of Ether on the Boba Network, giving you a clear, current metric.
What is the difference between get_tx_list and get_tx_list_internal? +
Use get_tx_list for standard transactions visible to the public. get_tx_list_internal shows the hidden, internal transactions that happen between contracts, which is critical for deep analysis.
Can I use get_abi to find a contract's source code? +
No. Use get_abi to get the interface definition (ABI). Use get_source_code to retrieve the actual human-readable source code for verified contracts.
How do I check if a transaction actually succeeded? +
Always use get_tx_receipt_status or proxy_get_transaction_receipt. These tools check the final state and receipt, which is more reliable than just looking at the transaction list.
How do I check balances for multiple addresses using get_ether_balance_multi? +
Pass a list of addresses to get_ether_balance_multi. It returns a single, consolidated output showing the ETH balance for every address you listed.
What information does the get_logs tool provide about a contract interaction? +
The get_logs tool retrieves all emitted event logs from a specific transaction. These logs detail every action the smart contract executed, including events like token transfers or status changes. This lets you trace exactly what happened during a contract call.
How can I use the get_source_code and get_abi tools together for contract analysis? +
You first use get_source_code to retrieve the contract's full source code. Then, you pass the contract address to get_abi to pull the Application Binary Interface (ABI). Having both lets your agent understand the code's logic and how to interact with it programmatically.
If I need to check the gas cost, which proxy tool should I use: proxy_estimate_gas or proxy_gas_price? +
Use proxy_estimate_gas to calculate the gas needed for a specific transaction or call. Use proxy_gas_price to get the current base gas price for the network. You'll typically combine both figures to estimate the total cost of an action.
Can I check the Ether balance of multiple addresses at once? +
Yes! Use the get_ether_balance_multi tool and provide a comma-separated list of addresses to retrieve all balances in a single query.
How do I view the source code of a verified smart contract? +
You can use the get_source_code tool with the contract's address. If the contract is verified on Bobascan, the AI will return the Solidity source code.
Is it possible to track NFT transfers for a specific wallet? +
Yes, the get_token_nft_tx tool allows you to list ERC721 token transfer events associated with any address on the Boba network.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Wakapi (WakaTime Alternative)
Track coding time, analyze productivity stats, and manage projects via Wakapi — an open-source WakaTime alternative.
RunPod
Integrate your AI securely to RunPod to cleanly quickly provision scalable GPU pods, manage active instances, and inspect serverless endpoints and custom templates natively.
Unleash (Feature Toggles)
Manage feature flags, strategies, and environments via Unleash — evaluate toggles, list projects, and monitor metrics directly from your AI agent.
You might also like
ApplicantStack
Manage your hiring process with ApplicantStack — track jobs, candidates, and hires via AI.
Playground AI
Generate, inpaint, upscale, and transform images using Playground AI's powerful models via natural language.
Extracta
Automate data extraction via Extracta — process documents into structured JSON, handle AI classification, and audit extraction history directly from any AI agent.