Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HTTP_HOST | No | Host to bind the HTTP server to | 127.0.0.1 |
| HTTP_PORT | No | Port for the HTTP server | 8000 |
Schema
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| __get_instructions__ | This tool MUST be called BEFORE any other tool.
Without calling it, the MCP server will not work as expected.
It MUST be called once in a session. |
| get_block_info | Get block information like timestamp, gas used, burnt fees, transaction count etc. |
| get_latest_block | Get the latest indexed block number and timestamp, which represents the most recent state of the blockchain.
No transactions or token transfers can exist beyond this point, making it useful as a reference timestamp for other API calls. |
| get_address_by_ens_name | Useful for when you need to convert an ENS domain name (e.g. "blockscout.eth")
to its corresponding Ethereum address. |
| get_transactions_by_address | Get transactions for an address within a specific time range.
Use cases:
- `get_transactions_by_address(address, age_from)` - get all transactions to/from the address since the given date up to the current time
- `get_transactions_by_address(address, age_from, age_to)` - get all transactions to/from the address between the given dates
- `get_transactions_by_address(address, age_from, age_to, methods)` - get all transactions to/from the address between the given dates and invoking the given method signature
Manipulating `age_from` and `age_to` allows you to paginate through results by time ranges. |
| get_token_transfers_by_address | Get ERC-20 token transfers for an address within a specific time range.
Use cases:
- `get_token_transfers_by_address(address, age_from)` - get all transfers of any ERC-20 token to/from the address since the given date up to the current time
- `get_token_transfers_by_address(address, age_from, age_to)` - get all transfers of any ERC-20 token to/from the address between the given dates
- `get_token_transfers_by_address(address, age_from, age_to, token)` - get all transfers of the given ERC-20 token to/from the address between the given dates
Manipulating `age_from` and `age_to` allows you to paginate through results by time ranges. For example, after getting transfers up to a certain timestamp, you can use that timestamp as `age_to` in the next query to get the next page of older transfers. |
| lookup_token_by_symbol | Search for token addresses by symbol or name. Returns multiple potential matches based on symbol or token name similarity. |
| get_contract_abi | Get smart contract ABI (Application Binary Interface).
An ABI defines all functions, events, their parameters, and return types. The ABI is required to format function calls or interpret contract data. |
| get_address_info | Get comprehensive information about an address, including:
- Address existence check
- Native token (ETH) balance (provided as is, without adjusting by decimals)
- ENS name association (if any)
- Contract status (whether the address is a contract, whether it is verified)
- Proxy contract information (if applicable): determines if a smart contract is a proxy contract (which forwards calls to implementation contracts), including proxy type and implementation addresses
- Token details (if the contract is a token): name, symbol, decimals, total supply, etc.
Essential for address analysis, contract investigation, token research, and DeFi protocol analysis. |
| get_tokens_by_address | Get comprehensive ERC20 token holdings for an address with enriched metadata and market data.
Returns detailed token information including contract details (name, symbol, decimals), market metrics (exchange rate, market cap, volume), holders count, and actual balance (provided as is, without adjusting by decimals).
Supports pagination.
Essential for portfolio analysis, wallet auditing, and DeFi position tracking. |
| transaction_summary | Get human-readable transaction summaries from Blockscout Transaction Interpreter.
Automatically classifies transactions into natural language descriptions (transfers, swaps, NFT sales, DeFi operations)
Essential for rapid transaction comprehension, dashboard displays, and initial analysis.
Note: Not all transactions can be summarized and accuracy is not guaranteed for complex patterns. |
| nft_tokens_by_address | Retrieve NFT tokens (ERC-721, ERC-404, ERC-1155) owned by an address, grouped by collection.
Provides collection details (type, address, name, symbol, total supply, holder count) and individual token instance data (ID, name, description, external URL, metadata attributes).
Essential for a detailed overview of an address's digital collectibles and their associated collection data. |
| get_transaction_info | Get comprehensive transaction information.
Unlike standard eth_getTransactionByHash, this tool returns enriched data including decoded input parameters, detailed token transfers with token metadata, address information (ENS names, contract verification status, public tags, proxy details), transaction fee breakdown (priority fees, burnt fees) and categorized transaction types.
Essential for transaction analysis, debugging smart contract interactions, tracking DeFi operations. |
| get_transaction_logs | Get comprehensive transaction logs with decoded event data.
Unlike standard eth_getLogs, this tool returns enriched logs including decoded event parameters with types and values, detailed contract information (ENS names, verification status, public tags, proxy details, token metadata), block context, and categorized event signatures.
Each log entry includes raw data, decoded method calls, parameter extraction, and contract classifications.
Essential for analyzing smart contract events, tracking token transfers, monitoring DeFi protocol interactions, debugging event emissions, and understanding complex multi-contract transaction flows. |
| get_address_logs | Get comprehensive logs emitted by a specific address with decoded event data.
Returns enriched log entries including decoded event parameters with types and values, detailed contract information (ENS names, verification status, public tags, proxy details, token metadata), block context, transaction hashes, and event signatures.
Each log entry includes raw data, decoded event names, parameter extraction with indexed/non-indexed classification, and contract classifications.
Essential for analyzing smart contract events emitted by specific addresses, monitoring token contract activities, tracking DeFi protocol state changes, debugging contract event emissions, and understanding address-specific event history flows. |
| get_chains_list | Get the list of known blockchain chains with their IDs.
Useful for getting a chain ID when the chain name is known. This information can be used in other tools that require a chain ID to request information. |