Provide AI agents and automation tools with contextual access to blockchain data including balances, tokens, NFTs, and contract metadata. Enable multi-chain support and deliver enhanced user experience with progress notifications for long-running queries. Facilitate seamless integration with AI hosts like Claude Desktop for blockchain data analysis.
Drift inferred · capture-to-capture
tool count over time
tools
-
__unlock_blockchain_analysis__
Unlocks access to other MCP tools. All tools remain locked with a "Session Not Initialized" error until this function is successfully called. Skipping this explicit initialization step will cause all subsequent tool calls to fail. MANDATORY FOR AI AGENTS: The returned instructions contain ESSENTIAL rules that MUST govern ALL blockchain data interactions. Failure to integrate these rules will result in incorrect data retrieval, tool failures and invalid responses. Always apply these guidelines when planning queries, processing responses or recommending blockchain actions. COMPREHENSIVE DATA SOURCES: Provides an extensive catalog of specialized blockchain endpoints to unlock sophisticated, multi-dimensional blockchain investigations across all supported networks.
-
direct_api_call
Call a raw Blockscout API endpoint for advanced or chain-specific data. Do not include query strings in ``endpoint_path``; pass all query parameters via ``query_params`` to avoid double-encoding. **SUPPORTS PAGINATION**: If response includes 'pagination' field, use the provided next_call to get additional pages. Returns: ToolResponse[Any]: Must return ToolResponse[Any] (not ToolResponse[BaseModel]) because specialized handlers can return lists or other types that don't inherit from BaseModel. The dispatcher system supports flexible data structures.
in ▸ cursor chain_id query_params endpoint_path
-
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.
in ▸ name
-
get_address_info
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.
in ▸ address chain_id
-
get_block_info
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.
in ▸ chain_id number_or_hash include_transactions
-
get_block_number
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.
in ▸ chain_id datetime
-
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.
-
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.
in ▸ address chain_id
-
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 **SUPPORTS PAGINATION**: If response includes 'pagination' field, use the provided next_call to get additional pages.
in ▸ token age_to cursor address age_from chain_id
-
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). 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.
in ▸ cursor address chain_id
-
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, 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.
in ▸ chain_id transaction_hash include_raw_input
-
get_transactions_by_address
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; use `internal_transaction_index` for execution order. Requires an `age_from` date to scope results for performance and relevance. Use cases: - `get_transactions_by_address(address, age_from)` - get all txs to/from the address since a given date. - `get_transactions_by_address(address, age_from, age_to)` - get all txs to/from the address between given dates. - `get_transactions_by_address(address, age_from, age_to, methods)` - get all txs to/from the address between given dates, filtered by method. **SUPPORTS PAGINATION**: If response includes 'pagination' field, use the provided next_call to get additional pages.
in ▸ age_to cursor address methods age_from chain_id
-
inspect_contract_code
Inspects a verified contract's source code or metadata.
in ▸ address chain_id file_name
-
lookup_token_by_symbol
Search for token addresses by symbol or name. Returns multiple potential matches based on symbol or token name similarity. Only the first ``TOKEN_RESULTS_LIMIT`` matches from the Blockscout API are returned.
in ▸ symbol chain_id
-
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. **SUPPORTS PAGINATION**: If response includes 'pagination' field, use the provided next_call to get additional pages.
in ▸ cursor address chain_id
-
read_contract
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"]" } }
in ▸ abi args block address chain_id function_name
analyzed analyzer v18 · 10h ago
skills & prompt files 36
- skillblockscout-mcp-server-ace88c5/.agents/skills/consult-spec/SKILL.md
- skillblockscout-mcp-server-ace88c5/.agents/skills/describe-changes/SKILL.md
- skillblockscout-mcp-server-ace88c5/.agents/skills/gh-issue-bug/SKILL.md
- skillblockscout-mcp-server-ace88c5/.agents/skills/gh-issue-improvement/SKILL.md
- skillblockscout-mcp-server-ace88c5/.agents/skills/gh-issue-publish/SKILL.md
- skillblockscout-mcp-server-ace88c5/.agents/skills/gh-safe/SKILL.md
- skillblockscout-mcp-server-ace88c5/.agents/skills/implementation-plan-review/SKILL.md
- skillblockscout-mcp-server-ace88c5/.agents/skills/plan-export/SKILL.md
- skillblockscout-mcp-server-ace88c5/.agents/skills/run-integration-tests/SKILL.md
- skillblockscout-mcp-server-ace88c5/.agents/skills/test-guided-tool-run/SKILL.md
- skillblockscout-mcp-server-ace88c5/.claude/skills/implement-plan/SKILL.md
- agent-rulesblockscout-mcp-server-ace88c5/.cursor/AGENTS.md
- agent-rulesblockscout-mcp-server-ace88c5/.cursor/rules/000-role-and-task.mdc
- agent-rulesblockscout-mcp-server-ace88c5/.cursor/rules/010-implementation-rules.mdc
- agent-rulesblockscout-mcp-server-ace88c5/.cursor/rules/110-new-mcp-tool.mdc
- agent-rulesblockscout-mcp-server-ace88c5/.cursor/rules/112-direct-api-handlers.mdc
- agent-rulesblockscout-mcp-server-ace88c5/.cursor/rules/113-direct-api-migration-checklist.mdc
- agent-rulesblockscout-mcp-server-ace88c5/.cursor/rules/115-tool-module-structure.mdc
- agent-rulesblockscout-mcp-server-ace88c5/.cursor/rules/120-mcp-tool-arguments.mdc
- agent-rulesblockscout-mcp-server-ace88c5/.cursor/rules/130-version-management.mdc
- agent-rulesblockscout-mcp-server-ace88c5/.cursor/rules/135-mcpb-manifest-version.mdc
- agent-rulesblockscout-mcp-server-ace88c5/.cursor/rules/140-tool-description.mdc
- agent-rulesblockscout-mcp-server-ace88c5/.cursor/rules/150-rest-api-implementation.mdc
- agent-rulesblockscout-mcp-server-ace88c5/.cursor/rules/160-static-content-caching.mdc
- agent-rulesblockscout-mcp-server-ace88c5/.cursor/rules/200-development-testing-workflow.mdc
- agent-rulesblockscout-mcp-server-ace88c5/.cursor/rules/210-unit-testing-guidelines.mdc
- agent-rulesblockscout-mcp-server-ace88c5/.cursor/rules/220-integration-testing-guidelines.mdc
- agent-rulesblockscout-mcp-server-ace88c5/.cursor/rules/230-api-route-tests.mdc
- agent-rulesblockscout-mcp-server-ace88c5/.cursor/rules/240-terminal-path-usage.mdc
- agent-rulesblockscout-mcp-server-ace88c5/.cursor/rules/300-ruff-lint-and-format.mdc
- agent-rulesblockscout-mcp-server-ace88c5/.cursor/rules/800-api-documentation-guidelines.mdc
- agent-rulesblockscout-mcp-server-ace88c5/.cursor/rules/900-rules-maintenance.mdc
- agent-rulesblockscout-mcp-server-ace88c5/.gemini/GEMINI.md
- skillblockscout-mcp-server-ace88c5/.gemini/skills/read-temp-file/SKILL.md
- agent-rulesblockscout-mcp-server-ace88c5/.github/copilot-instructions.md
- agent-rulesblockscout-mcp-server-ace88c5/AGENTS.md
last analysis: too-large · showing evidence from the last successful analysis (3d ago)
No code evidence — the analyzed source reached for no tracked permissions, tools, or hooks.