com.blockscout/mcp-server
REMOTE · MCP.BLOCKSCOUT.COM · SCANNED AUG 3
MCP server for Blockscout
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability46
- 5% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 3319 tokens (~89/item across 37 items; 16 tools + 21 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.blockscout.com
claude mcp add --transport http com-blockscout-mcp-server https://mcp.blockscout.com/mcp
[mcp_servers.com-blockscout-mcp-server] url = "https://mcp.blockscout.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-blockscout-mcp-server": {
"type": "remote",
"url": "https://mcp.blockscout.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-blockscout-mcp-server --url https://mcp.blockscout.com/mcp --transport streamable-http
mcp_servers:
com-blockscout-mcp-server:
url: "https://mcp.blockscout.com/mcp" {
"mcpServers": {
"com-blockscout-mcp-server": {
"type": "http",
"url": "https://mcp.blockscout.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +5
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes. Other categories moved too: Schema Quality & AI Usability fell 1.
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 62
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://mcp.blockscout.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=blockscout.com | CN=YE2,O=Let's Encrypt,C=US | 2 Aug 2026 | 31 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 5062c57a3f0ea57b115adb8afd5f360244f |
| SANs: *.blockscout.com, blockscout.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
DNSSEC insecure
Validation of mcp.blockscout.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| blockscout.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.blockscout.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.blockscout.com/mcp | HTTPS enforced | 301 | https://mcp.blockscout.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
__unlock_blockchain_analysis__ Unlock Blockchain Analysis ~94
Mandatory initialization step for any session against the Blockscout MCP server. Returns server reference data plus the `blockscout-analysis` skill pointer and URI resolution rule. MANDATORY FOR AI AGENTS: Call this tool first in every session. The returned payload identifies where the operating rules and analysis framework live and how to read referenced skill files before executing further tool calls.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| content_text | — | — | Optional human-readable summary used for MCP content responses. |
| data | — | yes | The main data payload of the tool's response. |
| data_description | — | — | A list of notes explaining the structure, fields, or conventions of the 'data' payload. |
| instructions | — | — | A list of suggested follow-up actions or instructions for the LLM to plan its next steps. |
| notes | — | — | A list of important contextual notes, such as warnings about data truncation or data quality issues. |
| pagination | — | — | Pagination information, present only if the 'data' is a single page of a larger result set. |
No examples provided.
direct_api_call Direct Blockscout API Call ~307
Call a raw Blockscout API endpoint for advanced or chain-specific data. Before the first call to this tool in a session, read `blockscout-mcp://skill/SKILL.md` (the operating rules), then `blockscout-mcp://skill/references/blockscout-api-index.md` (the authoritative index of callable endpoints); skip both reads only if this skill content is already in context. Recalled Blockscout API knowledge is not a substitute: endpoint paths, parameters, and response shapes vary across Blockscout versions and per-chain deployments. Supports POST requests with a JSON body for endpoints like JSON RPC. **SUPPORTS PAGINATION**: If response includes 'pagination' field, use the provided next_call to get additional pages (GET only).
| Name | Type | Req | Description |
|---|---|---|---|
| chain_id | string | yes | The ID of the blockchain |
| cursor | — | — | The pagination cursor from a previous response to get the next page of results. |
| endpoint_path | string | yes | The Blockscout API path to call (e.g., '/api/v2/stats'); do not include query strings — pass all query parameters via query_params to avoid double-encoding. |
| json_body | — | — | JSON request body for POST requests. |
| method | string | — | HTTP method used for the upstream call. Use POST with json_body. |
| query_params | — | — | Optional query parameters forwarded to the Blockscout API. |
| Name | Type | Req | Description |
|---|---|---|---|
| content_text | — | — | Optional human-readable summary used for MCP content responses. |
| data | — | yes | The main data payload of the tool's response. |
| data_description | — | — | A list of notes explaining the structure, fields, or conventions of the 'data' payload. |
| instructions | — | — | A list of suggested follow-up actions or instructions for the LLM to plan its next steps. |
| notes | — | — | A list of important contextual notes, such as warnings about data truncation or data quality issues. |
| pagination | — | — | Pagination information, present only if the 'data' is a single page of a larger result set. |
No examples provided.
get_address_by_ens_name Get Address by ENS Name ~55
Useful for when you need to convert an ENS domain name (e.g. "blockscout.eth") to its corresponding Ethereum address.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | ENS domain name to resolve |
| Name | Type | Req | Description |
|---|---|---|---|
| content_text | — | — | Optional human-readable summary used for MCP content responses. |
| data | — | yes | The main data payload of the tool's response. |
| data_description | — | — | A list of notes explaining the structure, fields, or conventions of the 'data' payload. |
| instructions | — | — | A list of suggested follow-up actions or instructions for the LLM to plan its next steps. |
| notes | — | — | A list of important contextual notes, such as warnings about data truncation or data quality issues. |
| pagination | — | — | Pagination information, present only if the 'data' is a single page of a larger result set. |
No examples provided.
get_address_info Get Address Information ~185
Get comprehensive information about an address, including: - Address existence check - Native token (ETH) balance (provided as is, without adjusting by decimals) - First transaction details (block number and timestamp) for age calculation - 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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Address to get information about |
| chain_id | string | yes | The ID of the blockchain |
| Name | Type | Req | Description |
|---|---|---|---|
| content_text | — | — | Optional human-readable summary used for MCP content responses. |
| data | — | yes | The main data payload of the tool's response. |
| data_description | — | — | A list of notes explaining the structure, fields, or conventions of the 'data' payload. |
| instructions | — | — | A list of suggested follow-up actions or instructions for the LLM to plan its next steps. |
| notes | — | — | A list of important contextual notes, such as warnings about data truncation or data quality issues. |
| pagination | — | — | Pagination information, present only if the 'data' is a single page of a larger result set. |
No examples provided.
get_block_info Get Block Information ~115
Get block information like timestamp, gas used, burnt fees, transaction count etc. Can optionally include the list of transaction hashes contained in the block. Transaction hashes are omitted by default; request them only when you truly need them, because on high-traffic chains the list may exhaust the context.
| Name | Type | Req | Description |
|---|---|---|---|
| chain_id | string | yes | The ID of the blockchain |
| include_transactions | — | — | If true, includes a list of transaction hashes from the block. |
| number_or_hash | string | yes | Block number or hash |
| Name | Type | Req | Description |
|---|---|---|---|
| content_text | — | — | Optional human-readable summary used for MCP content responses. |
| data | — | yes | The main data payload of the tool's response. |
| data_description | — | — | A list of notes explaining the structure, fields, or conventions of the 'data' payload. |
| instructions | — | — | A list of suggested follow-up actions or instructions for the LLM to plan its next steps. |
| notes | — | — | A list of important contextual notes, such as warnings about data truncation or data quality issues. |
| pagination | — | — | Pagination information, present only if the 'data' is a single page of a larger result set. |
No examples provided.
get_block_number Get Block Number ~152
Retrieves the block number and timestamp for a specific date/time or the latest block. Use when you need a block height for a specific point in time (e.g., "block at 2024-01-01") or the current chain tip. If `datetime` is provided, finds the block immediately preceding that time. If omitted, returns the latest indexed block.
| Name | Type | Req | Description |
|---|---|---|---|
| chain_id | string | yes | The ID of the blockchain |
| datetime | — | — | The date and time (ISO 8601 format, e.g. 2025-05-22T23:00:00.00Z) to find the block for. If omitted, returns the latest block. |
| Name | Type | Req | Description |
|---|---|---|---|
| content_text | — | — | Optional human-readable summary used for MCP content responses. |
| data | — | yes | The main data payload of the tool's response. |
| data_description | — | — | A list of notes explaining the structure, fields, or conventions of the 'data' payload. |
| instructions | — | — | A list of suggested follow-up actions or instructions for the LLM to plan its next steps. |
| notes | — | — | A list of important contextual notes, such as warnings about data truncation or data quality issues. |
| pagination | — | — | Pagination information, present only if the 'data' is a single page of a larger result set. |
No examples provided.
get_chains_list Get List of Chains ~153
Get supported blockchain chains with their chain IDs. Ethereum Mainnet is `chain_id` `1`; use this tool to resolve any other chain. Use this when another tool needs a supported `chain_id` and only the chain name, ecosystem, or native currency is known. Prefer a narrow `query` to avoid returning the full registry to the agent. Do not rely on partial numeric chain ID queries such as `1`, because matching is substring-based and may return many chains.
| Name | Type | Req | Description |
|---|---|---|---|
| query | — | — | Optional case-insensitive substring filter applied to chain name, chain ID, native currency, and ecosystem. Prefer narrow text terms over partial numeric chain IDs because matching is substring-based. |
| Name | Type | Req | Description |
|---|---|---|---|
| content_text | — | — | Optional human-readable summary used for MCP content responses. |
| data | array | yes | The main data payload of the tool's response. |
| data_description | — | — | A list of notes explaining the structure, fields, or conventions of the 'data' payload. |
| instructions | — | — | A list of suggested follow-up actions or instructions for the LLM to plan its next steps. |
| notes | — | — | A list of important contextual notes, such as warnings about data truncation or data quality issues. |
| pagination | — | — | Pagination information, present only if the 'data' is a single page of a larger result set. |
No examples provided.
get_contract_abi Get Contract ABI ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Smart contract address |
| chain_id | string | yes | The ID of the blockchain |
| Name | Type | Req | Description |
|---|---|---|---|
| content_text | — | — | Optional human-readable summary used for MCP content responses. |
| data | — | yes | The main data payload of the tool's response. |
| data_description | — | — | A list of notes explaining the structure, fields, or conventions of the 'data' payload. |
| instructions | — | — | A list of suggested follow-up actions or instructions for the LLM to plan its next steps. |
| notes | — | — | A list of important contextual notes, such as warnings about data truncation or data quality issues. |
| pagination | — | — | Pagination information, present only if the 'data' is a single page of a larger result set. |
No examples provided.
get_token_transfers_by_address Get Token Transfers by Address ~237
Get ERC-20 token transfers for an address within a specific time range. **SUPPORTS PAGINATION**: If response includes 'pagination' field, use the provided next_call to get additional pages.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Address which either transfer initiator or transfer receiver |
| age_from | string | yes | Start date and time (e.g 2025-05-22T23:00:00.00Z). Alone, returns all ERC-20 transfers to/from the address since this date. |
| age_to | — | — | End date and time (e.g 2025-05-22T22:30:00.00Z). Adding this bounds the upper end of the date range started by `age_from`; if omitted, transfers up to the current time are returned. |
| chain_id | string | yes | The ID of the blockchain |
| cursor | — | — | The pagination cursor from a previous response to get the next page of results. |
| token | — | — | An ERC-20 token contract address to restrict results to a single token. If omitted, returns transfers of all tokens. |
| Name | Type | Req | Description |
|---|---|---|---|
| content_text | — | — | Optional human-readable summary used for MCP content responses. |
| data | array | yes | The main data payload of the tool's response. |
| data_description | — | — | A list of notes explaining the structure, fields, or conventions of the 'data' payload. |
| instructions | — | — | A list of suggested follow-up actions or instructions for the LLM to plan its next steps. |
| notes | — | — | A list of important contextual notes, such as warnings about data truncation or data quality issues. |
| pagination | — | — | Pagination information, present only if the 'data' is a single page of a larger result set. |
No examples provided.
get_tokens_by_address Get Tokens by Address ~154
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). Essential for portfolio analysis, wallet auditing, and DeFi position tracking. **SUPPORTS PAGINATION**: If response includes 'pagination' field, use the provided next_call to get additional pages.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet address |
| chain_id | string | yes | The ID of the blockchain |
| cursor | — | — | The pagination cursor from a previous response to get the next page of results. |
| Name | Type | Req | Description |
|---|---|---|---|
| content_text | — | — | Optional human-readable summary used for MCP content responses. |
| data | array | yes | The main data payload of the tool's response. |
| data_description | — | — | A list of notes explaining the structure, fields, or conventions of the 'data' payload. |
| instructions | — | — | A list of suggested follow-up actions or instructions for the LLM to plan its next steps. |
| notes | — | — | A list of important contextual notes, such as warnings about data truncation or data quality issues. |
| pagination | — | — | Pagination information, present only if the 'data' is a single page of a larger result set. |
No examples provided.
get_transaction_info Get Transaction Information ~152
Get comprehensive transaction information. Unlike standard eth_getTransactionByHash, this tool returns enriched data including decoded input parameters, detailed token transfers with token metadata, transaction fee breakdown (priority fees, burnt fees) and categorized transaction types. By default, the raw transaction input is omitted if a decoded version is available to save context; request it with `include_raw_input=True` only when you truly need the raw hex data. Essential for transaction analysis, debugging smart contract interactions, tracking DeFi operations.
| Name | Type | Req | Description |
|---|---|---|---|
| chain_id | string | yes | The ID of the blockchain |
| include_raw_input | — | — | If true, includes the raw transaction input data. |
| transaction_hash | string | yes | Transaction hash |
| Name | Type | Req | Description |
|---|---|---|---|
| content_text | — | — | Optional human-readable summary used for MCP content responses. |
| data | — | yes | The main data payload of the tool's response. |
| data_description | — | — | A list of notes explaining the structure, fields, or conventions of the 'data' payload. |
| instructions | — | — | A list of suggested follow-up actions or instructions for the LLM to plan its next steps. |
| notes | — | — | A list of important contextual notes, such as warnings about data truncation or data quality issues. |
| pagination | — | — | Pagination information, present only if the 'data' is a single page of a larger result set. |
No examples provided.
get_transactions_by_address Get Transactions by Address ~315
Retrieves native currency transfers and smart contract interactions (calls, internal txs) for an address. **EXCLUDES TOKEN TRANSFERS**: Filters out direct token balance changes (ERC-20, etc.). You'll see calls *to* token contracts, but not the `Transfer` events. For token history, use `get_token_transfers_by_address`. A single tx can have multiple records from internal calls. Requires an `age_from` date to scope results for performance and relevance. **SUPPORTS PAGINATION**: If response includes 'pagination' field, use the provided next_call to get additional pages.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Address which either sender or receiver of the transaction |
| age_from | string | yes | Start date and time (e.g 2025-05-22T23:00:00.00Z). Alone, returns all transactions to/from the address since this date. |
| age_to | — | — | End date and time (e.g 2025-05-22T22:30:00.00Z). Adding this bounds the upper end of the date range started by `age_from`. |
| chain_id | string | yes | The ID of the blockchain |
| cursor | — | — | The pagination cursor from a previous response to get the next page of results. |
| methods | — | — | A method signature to filter transactions by (e.g 0x304e6ade). Filters the (optionally date-bounded) results to a specific method signature. |
| Name | Type | Req | Description |
|---|---|---|---|
| content_text | — | — | Optional human-readable summary used for MCP content responses. |
| data | array | yes | The main data payload of the tool's response. |
| data_description | — | — | A list of notes explaining the structure, fields, or conventions of the 'data' payload. |
| instructions | — | — | A list of suggested follow-up actions or instructions for the LLM to plan its next steps. |
| notes | — | — | A list of important contextual notes, such as warnings about data truncation or data quality issues. |
| pagination | — | — | Pagination information, present only if the 'data' is a single page of a larger result set. |
No examples provided.
inspect_contract_code Inspect Contract Code ~73
Inspects a verified contract's source code or metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The address of the smart contract. |
| chain_id | string | yes | The ID of the blockchain. |
| file_name | — | — | The name of the source file to inspect. If omitted, returns contract metadata and the list of source files. |
| Name | Type | Req | Description |
|---|---|---|---|
| content_text | — | — | Optional human-readable summary used for MCP content responses. |
| data | — | yes | The main data payload of the tool's response. |
| data_description | — | — | A list of notes explaining the structure, fields, or conventions of the 'data' payload. |
| instructions | — | — | A list of suggested follow-up actions or instructions for the LLM to plan its next steps. |
| notes | — | — | A list of important contextual notes, such as warnings about data truncation or data quality issues. |
| pagination | — | — | Pagination information, present only if the 'data' is a single page of a larger result set. |
No examples provided.
lookup_token_by_symbol Lookup Token by Symbol ~80
Search for token addresses by symbol or name. Returns multiple potential matches based on symbol or token name similarity. Only the first 7 matches from the Blockscout API are returned.
| Name | Type | Req | Description |
|---|---|---|---|
| chain_id | string | yes | The ID of the blockchain |
| symbol | string | yes | Token symbol or name to search for |
| Name | Type | Req | Description |
|---|---|---|---|
| content_text | — | — | Optional human-readable summary used for MCP content responses. |
| data | array | yes | The main data payload of the tool's response. |
| data_description | — | — | A list of notes explaining the structure, fields, or conventions of the 'data' payload. |
| instructions | — | — | A list of suggested follow-up actions or instructions for the LLM to plan its next steps. |
| notes | — | — | A list of important contextual notes, such as warnings about data truncation or data quality issues. |
| pagination | — | — | Pagination information, present only if the 'data' is a single page of a larger result set. |
No examples provided.
nft_tokens_by_address Get NFT Tokens by Address ~163
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. **SUPPORTS PAGINATION**: If response includes 'pagination' field, use the provided next_call to get additional pages.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | NFT owner address |
| chain_id | string | yes | The ID of the blockchain |
| cursor | — | — | The pagination cursor from a previous response to get the next page of results. |
| Name | Type | Req | Description |
|---|---|---|---|
| content_text | — | — | Optional human-readable summary used for MCP content responses. |
| data | array | yes | The main data payload of the tool's response. |
| data_description | — | — | A list of notes explaining the structure, fields, or conventions of the 'data' payload. |
| instructions | — | — | A list of suggested follow-up actions or instructions for the LLM to plan its next steps. |
| notes | — | — | A list of important contextual notes, such as warnings about data truncation or data quality issues. |
| pagination | — | — | Pagination information, present only if the 'data' is a single page of a larger result set. |
No examples provided.
read_contract Read from Contract ~490
Calls a smart contract function (view/pure, or non-view/pure simulated via eth_call) and returns the decoded result. This tool provides a direct way to query the state of a smart contract. Example: To check the USDT balance of an address on Ethereum Mainnet, you would use the following arguments: { "tool_name": "read_contract", "params": { "chain_id": "1", "address": "0xdAC17F958D2ee523a2206206994597C13D831ec7", "abi": { "constant": true, "inputs": [{"name": "_owner", "type": "address"}], "name": "balanceOf", "outputs": [{"name": "balance", "type": "uint256"}], "payable": false, "stateMutability": "view", "type": "function" }, "function_name": "balanceOf", "args": "["0xF977814e90dA44bFA03b6295A0616a897441aceC"]" } }
| Name | Type | Req | Description |
|---|---|---|---|
| abi | object | yes | The JSON ABI for the specific function being called. This should be a dictionary that defines the function's name, inputs, and outputs. The function ABI can be obtained using the `get_contract_abi` t… |
| address | string | yes | Smart contract address |
| args | string | — | A JSON string containing an array of arguments. Example: "["0xabc..."]" for a single address argument, or "[]" for no arguments. Order and types must match ABI inputs. Addresses: use 0x-prefixed stri… |
| block | — | — | The block identifier to read the contract state from. Can be a block number (e.g., 19000000) or a string tag (e.g., 'latest'). Defaults to 'latest'. |
| chain_id | string | yes | The ID of the blockchain |
| function_name | string | yes | The symbolic name of the function to be called. This must match the `name` field in the provided ABI. |
| Name | Type | Req | Description |
|---|---|---|---|
| content_text | — | — | Optional human-readable summary used for MCP content responses. |
| data | — | yes | The main data payload of the tool's response. |
| data_description | — | — | A list of notes explaining the structure, fields, or conventions of the 'data' payload. |
| instructions | — | — | A list of suggested follow-up actions or instructions for the LLM to plan its next steps. |
| notes | — | — | A list of important contextual notes, such as warnings about data truncation or data quality issues. |
| pagination | — | — | Pagination information, present only if the 'data' is a single page of a larger result set. |
No examples provided.