Lineascan MCP. Query ETH Balances, Track Transfers, and Inspect Contract Code.
Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Lineascan MCP Server connects your AI agent directly to the Linea blockchain data. Check ETH balances for multiple addresses, track ERC-20 and NFT transfers in real time, or fetch ABI and source code for smart contracts—all via tool calls.
It lets you analyze complex L2 transactions without leaving your IDE.
What your AI agents can do
Balance multi
Gets ETH balances for a list of multiple addresses at once.
Check verify status
Checks the current status of a contract verification request.
Eth block number
Returns the number of the most recent block on the network.
Get ETH balances for single or multiple addresses on the Linea network.
Retrieve lists of ERC-20 and ERC-721 (NFT) transfers associated with an address, including full metadata.
Fetch the ABI or Solidity source code for verified smart contracts to understand their logic.
Query specific transaction details, including normal transfers, internal calls, and full receipt status via hash.
Generate estimates for required gas to prevent failed transactions during execution planning.
Ask AI about this MCP
Supported MCP Clients
Waiting for input…
Lineascan MCP Server: 25 Tools for Blockchain Data Access
Use these tools to query specific details from the Linea blockchain. From checking ETH balances to retrieving smart contract source code, this server provides deep access into EVM state changes.
019e5d2dbalance multi
Gets ETH balances for a list of multiple addresses at once.
019e5d2dcheck verify status
Checks the current status of a contract verification request.
019e5d2deth block number
Returns the number of the most recent block on the network.
019e5d2deth call
Executes a read-only message call without spending gas or creating a transaction.
019e5d2deth estimate gas
Calculates an estimate of the gas required for a specific transaction operation.
019e5d2deth get block by number
Retrieves all information associated with a specified block number.
019e5d2deth get transaction by hash
Returns full details about a single transaction using its hash.
019e5d2deth get transaction receipt
Retrieves the receipt data for a completed transaction using its hash.
019e5d2deth price
Gets the current market price of ETH in both USD and BTC.
019e5d2deth supply
Returns the total circulating supply amount of ETH on Linea.
019e5d2dget abi
Fetches the Application Binary Interface (ABI) for a verified smart contract.
019e5d2dget balance
Gets the ETH balance for one specific address.
019e5d2dget block countdown
Provides an estimate of time until the next block is mined.
019e5d2dget block no by time
Finds the corresponding block number given a specific timestamp.
019e5d2dget block reward
Retrieves block and uncle rewards for a given block number.
019e5d2dget logs
Gets event logs from a contract with filtering options like address or topic.
019e5d2dget mined blocks
Lists all blocks that were mined by a specific wallet address.
019e5d2dget source code
Retrieves the original source code for a verified smart contract.
019e5d2dget status
Checks the live execution status of an ongoing transaction.
019e5d2dget tx receipt status
Verifies the final outcome and status of a past transaction receipt.
019e5d2dtoken nft tx
Lists all ERC-721 (NFT) token transfer events for a specified address.
019e5d2dtoken tx
Lists all ERC-20 standard token transfer events for a specified address.
019e5d2dtx list
Gets a list of normal, successful transactions associated with an address.
019e5d2dtx list internal
Retrieves internal transactions that occurred during the execution flow for an address.
019e5d2dverify source code
Submits a contract's source code to Lineascan for official verification.
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 Lineascan, 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, listen up. The Lineascan MCP Server hooks your AI agent right into the Linea blockchain data. It gives you a ton of tools to read and inspect everything happening on the EVM—no leaving your IDE for this mess. You're gonna be able to track complex L2 transactions without breaking a sweat.
Checking Balances and Supply
When you need to know who's got cash, you can use get_balance to grab the ETH balance for just one address. If ya gotta check multiple accounts at once, hit up balance_multi; it gets ETH balances for a list of addresses all in one go. For big picture stuff, eth_supply returns the total circulating supply amount of ETH on Linea.
You can also see how much gas you're gonna spend by running eth_estimate_gas, which calculates the required gas for any specific transaction operation.
Tracking Assets and Transfers
To follow token movements, use token_tx to list every ERC-20 standard token transfer event associated with an address. If you're tracking NFTs (those are ERC-721s), token_nft_tx lists all those specific NFT transfer events for a given address and includes full metadata. For general activity, tx_list gets a list of normal, successful transactions tied to an address, while tx_list_internal pulls in the internal calls that happened during execution.
Analyzing Transactions Deeply
Need the nitty-gritty on a transaction? You can get full details about a single transfer using its hash with eth_get_transaction_by_hash. Once the transaction's done, you retrieve the final results—the receipt data—using eth_get_transaction_receipt. If you need to monitor something live, get_status checks the execution status of an ongoing transaction. To confirm a past transaction finished right, use get_tx_receipt_status to verify the final outcome and status from a previous receipt.
You can also check event logs from any contract using get_logs, giving you filtering options like address or topic. For tracking general activity history on an account, get_mined_blocks lists every block mined by that specific wallet address.
Understanding the Network State
If you wanna know what's going down with the network itself, you can grab the number of the most recent block using eth_block_number. Need data for a specific historical moment? Run eth_get_block_by_number to pull all info related to a specified block. You can also find out which block corresponds to a certain time stamp with get_block_no_by_time, or figure out the timestamp from a block number using get_block_countdown.
For rewards, get_block_reward retrieves the block and uncle rewards for any given block number. If you wanna know what's going on right now, eth_price gives you the current market price of ETH in both USD and BTC.
Reading Smart Contract Code
When you need to understand how a contract works, these tools are your ticket. To read its logic, you can fetch the Application Binary Interface (ABI) using get_abi. If you wanna see the original code, get_source_code retrieves the source for verified smart contracts. You also have control over submitting new code by running verify_source_code, which sends a contract's source to Lineascan for official verification.
When that submission is in progress, you can check its live status using check_verify_status.
Advanced Data Retrieval and Calls
Sometimes ya don't wanna send a transaction just to read data. For that, run eth_call; it executes a read-only message call without spending gas or creating any actual transaction. You can also get all the event logs from a contract using get_logs, giving you filtering options like address or topic.
This server gives ya everything: tracking assets with token_tx and token_nft_tx, checking balances with balance_multi and get_balance, pulling code with get_source_code and get_abi, analyzing transaction history using eth_get_transaction_by_hash and get_status, and monitoring the network state using eth_block_number and eth_price. It's everything you need, period.
How Lineascan MCP Works
- 1 Subscribe to the Lineascan server and provide your API key.
- 2 Instruct your AI client (like Cursor or Claude) to use a specific tool, like
balance_multi, providing the target addresses. - 3 The agent executes the call; the server returns the requested ETH balances directly.
The bottom line is: you write natural language instructions, and your AI client converts them into precise blockchain data queries.
Who Is Lineascan MCP For?
This tool is for developers, auditors, and deep-dive crypto analysts. If you spend time clicking through multiple blockchain explorer tabs—checking a balance here, pulling the code there, then scrolling to find transfer logs—you need this. It moves that entire manual process into an automated query.
Inspects contract ABIs and source code in their IDE without switching tabs or leaving the development environment.
Tracks token movements, volumes, and transaction patterns across a defined set of addresses to build reports.
Checks contract source code for known vulnerabilities and verifies the execution status of complex transactions.
What Changes When You Connect
- Automated Balance Checks: Use
balance_multito check the ETH balances of dozens of addresses in one query. No need to paste them into a spreadsheet and check them manually. - Deep Transaction History: Get full records by running
token_txortoken_nft_tx. This goes beyond basic transaction hashes, giving you every associated token transfer event metadata. - Code Inspection on Demand: Need to know what a contract does? Use
get_source_codeorget_abi. Your agent pulls the Solidity code directly into your workspace for review. - Pre-Flight Gas Checks: Run
eth_estimate_gasbefore submitting anything. This stops failed transactions due to unexpected gas costs, saving you time and Ether. - Comprehensive Status Tracking: Don't trust a simple 'success' flag. Use
get_tx_receipt_statusto confirm the final outcome of any transaction hash.
Real-World Use Cases
Auditing a DeFi Pool
A security auditor needs to know if an address dumped funds recently. They ask their agent: 'Show me all ERC-20 and NFT transfers for 0x...'. The agent runs token_tx and token_nft_tx, giving the auditor a single, filtered list of all asset movements across time.
Monitoring Investor Holdings
A data analyst needs to check the holdings of five major venture funds. Instead of running five manual balance checks, they use balance_multi to get the ETH balances for all five addresses instantly, building a quick overview.
Debugging Smart Contract Logic
A developer runs into an unexpected function call. They ask their agent: 'What is the source code and ABI for contract 0x...?' The agent executes get_source_code and get_abi, allowing the developer to debug the logic without leaving their IDE.
Tracing Failed Transactions
A user submitted a transaction that failed. They ask: 'Why did this fail?'. The agent first runs eth_get_transaction_by_hash for context, then uses get_tx_receipt_status to pinpoint the exact failure state and potential cause.
The Tradeoffs
Checking status too late
A user checks a transaction hash (eth_get_transaction_by_hash) right after submission, sees 'pending,' and assumes nothing is wrong. They don't realize the state might change.
→
Always use get_tx_receipt_status or get_status to confirm final execution status, not just initial transaction details. This confirms if the contract finished executing successfully.
Ignoring token types
The user runs a general 'list transactions' tool (tx_list) and only sees ETH movements. They miss the crucial USDC or NFT transfers that happened within the same window.
→
Always follow up with specific tools: run token_tx for fungible tokens (ERC-20) and token_nft_tx for non-fungible assets (NFTs).
Over-relying on simple reads
The user tries to figure out gas costs just by reading the transaction details without an estimate. They submit, and the transaction fails due to underflow.
→
Before attempting any write or complex operation, always run eth_estimate_gas. This gives a necessary pre-check on cost.
When It Fits, When It Doesn't
Use this server if your core requirement is reading immutable state data directly from the Linea blockchain. If you need to know what happened with funds or code, these tools are mandatory.
Don't use it if: 1) You only need generalized market metrics (use a dedicated price feed API). 2) Your data comes from an internal system that hasn't been written to the chain. For those cases, you need database access tools instead of blockchain explorers. If your goal is just 'to see what happened,' start with tx_list. If it was token-related, use token_tx or token_nft_tx. This combination lets you move from a high-level view to the absolute granular details.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Lineascan. 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
Tracking asset flows across an L2 shouldn't require opening five different browser tabs.
Today, tracing a single token movement—say, finding out if funds passed through a contract and ended up as NFTs—is a multi-step headache. You check the basic transaction hash in one tab. Then you open a second tab to find the internal calls. A third tab is needed for the ABI to understand what functions were run. Finally, you might need a fourth just to see if the token was ERC-20 or an NFT.
With Lineascan MCP Server, your agent handles this chain of queries in one go. You ask: 'What happened with these funds?' The system runs `eth_get_transaction_by_hash`, then pulls the specific logs using `get_logs`. It delivers a single, coherent report detailing every asset movement and contract interaction.
Using Lineascan MCP Server: Get live balances and source code with simple queries.
Manually checking an address's ETH balance requires one click. But if you need to check five addresses, then trace the history of token movements for each, and finally verify that a specific contract is audited, it becomes a repetitive cycle of copy-pasting hashes into multiple explorer interfaces.
Now, your agent handles all of this. You simply list the tasks: 'Check balances for these 5; list ERC-20 transfers for them; check the source code for X.' The data streams back structured and ready to use—zero manual clicks required.
Common Questions About Lineascan MCP
How do I find out what tokens were transferred? (using token_tx) +
The token_tx tool lists all ERC-20 transfers for a given address. This is the right tool if you are tracking standard, fungible tokens like USDC or WETH.
What's the difference between `get_balance` and `balance_multi`? +
get_balance checks one single address. Use balance_multi when you need to check ETH balances for a list of multiple addresses at once.
Can I see the source code without leaving my IDE? (using get_source_code) +
Yes, that's exactly what this tool does. You ask your agent to run get_source_code for a contract hash, and it pulls the Solidity code directly into your environment.
Which tool should I use to see all transaction types? (using tx_list) +
tx_list gives you normal transactions. However, if you are looking for token movements, you must use token_tx or token_nft_tx instead.
How do I check the status of a transaction that failed? (using get_tx_receipt_status) +
You run get_tx_receipt_status using the hash. This provides final confirmation on whether the contract completed, failed, or reverted, giving you more detail than just viewing the raw transaction.
How do I estimate the required gas for a transaction using `eth_estimate_gas`? +
It generates an accurate cost prediction. You pass in the function parameters, and the tool returns the estimated amount of gas needed. This lets you plan your budget before running a live transaction.
How can I find out what block was mined at a specific time using `get_block_no_by_time`? +
It takes a Unix timestamp and returns the corresponding block number. This is critical for historical analysis when you only have a date, not a transaction hash.
What kind of data can I pull for an entire block using `eth_get_block_by_number`? +
You provide the block number, and it returns comprehensive details about that specific block. This includes timestamps, parent hashes, and a list of all transactions confirmed within it.
Can I check the ETH balance of multiple wallet addresses at once? +
Yes! Use the balance_multi tool and provide a comma-separated list of addresses. The agent will return the current ETH balance for each one in a single request.
How can I see the history of NFT transfers for a specific address? +
You can use the token_nft_tx tool. Just provide the wallet address, and optionally a contract address, to list all ERC-721 token transfer events associated with that account.
Is it possible to read the source code of a verified smart contract? +
Absolutely. Use the get_source_code tool with the contract's address. If the contract is verified on Lineascan, the agent will retrieve the full source code for your inspection.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Nmap Online
Perform network discovery and security auditing via Nmap — track port scans, DNS lookups, and traceroutes directly from your AI agent.
OceanBase
Enterprise distributed relational database — manage clusters, tenants, and databases via AI.
Blockchair (Universal Blockchain Search Engine & API)
Query blocks, transactions, and addresses across multiple blockchains like Bitcoin and Ethereum using Blockchair's universal API.
You might also like
HubSpot
Grow better with an integrated CRM that unifies marketing, sales, service, and operations in one powerful platform.
Bazaarvoice
Analyze and manage user-generated content via Bazaarvoice — list products, reviews, and customer questions directly from any AI agent.
ZoomInfo
Equip your AI agent with direct access to ZoomInfo — search company and contact records, enrich lead data, and build prospect lists without opening the ZoomInfo platform.