_ registry / mcp http-sse

blockscout-mcp-server

https://mcp.blockscout.com

Registry code: 4b9a3ad6761a84b2

api record

Blockscout MCP server version: 0.19.0

Operating rules, execution strategies, and the curated `direct_api_call` endpoint reference for analyzing Blockscout data live in the `blockscout-analysis` skill (version 0.6.0). If the skill is already loaded in your context, use that copy. If no copy is loaded, fetch the entry point from `blockscout-mcp://skill/SKILL.md` over MCP resources or `GET /skill/SKILL.md` over HTTP.

endpoint
https://mcp.blockscout.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
unknown
uptime
—
latency
—

last good check

priced tools
0

of 16 tools

_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 16 tools
16 never probed 0 of 16 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • lookup_token_by_symbol unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "title": "lookup_token_by_symbolArguments",
  "required": [
    "chain_id",
    "symbol"
  ],
  "properties": {
    "symbol": {
      "type": "string",
      "title": "Symbol",
      "description": "Token symbol or name to search for"
    },
    "chain_id": {
      "type": "string",
      "title": "Chain Id",
      "description": "The ID of the blockchain"
    },
    "session_id": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Session Id",
      "default": null,
      "description": "Opaque session identifier."
    }
  }
}
    arguments 33 lines
  • get_contract_abi unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "title": "get_contract_abiArguments",
  "required": [
    "chain_id",
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "title": "Address",
      "description": "Smart contract address"
    },
    "chain_id": {
      "type": "string",
      "title": "Chain Id",
      "description": "The ID of the blockchain"
    },
    "session_id": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Session Id",
      "default": null,
      "description": "Opaque session identifier."
    }
  }
}
    arguments 33 lines
  • inspect_contract_code unknown never probed

    Inspects a verified contract's source code or metadata.

    mcp-tool

    {
  "type": "object",
  "title": "inspect_contract_codeArguments",
  "required": [
    "chain_id",
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "title": "Address",
      "description": "The address of the smart contract."
    },
    "chain_id": {
      "type": "string",
      "title": "Chain Id",
      "description": "The ID of the blockchain."
    },
    "file_name": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "File Name",
      "default": null,
      "description": "The name of the source file to inspect. If omitted, returns contract metadata and the list of source files."
    },
    "session_id": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Session Id",
      "default": null,
      "description": "Opaque session identifier."
    }
  }
}
    arguments 46 lines
  • read_contract unknown never probed

    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"]" } }

    mcp-tool

    {
  "type": "object",
  "title": "read_contractArguments",
  "required": [
    "chain_id",
    "address",
    "abi",
    "function_name"
  ],
  "properties": {
    "abi": {
      "type": "object",
      "title": "Abi",
      "description": "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` tool.",
      "additionalProperties": true
    },
    "args": {
      "type": "string",
      "title": "Args",
      "default": "[]",
      "description": "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 strings; Numbers: prefer integers (not quoted); numeric strings like \"1\" are also accepted and coerced to integers. Bytes: keep as 0x-hex strings."
    },
    "block": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "integer"
        }
      ],
      "title": "Block",
      "default": "latest",
      "description": "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'."
    },
    "address": {
      "type": "string",
      "title": "Address",
      "description": "Smart contract address"
    },
    "chain_id": {
      "type": "string",
      "title": "Chain Id",
      "description": "The ID of the blockchain"
    },
    "session_id": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Session Id",
      "default": null,
      "description": "Opaque session identifier."
    },
    "function_name": {
      "type": "string",
      "title": "Function Name",
      "description": "The symbolic name of the function to be called. This must match the `name` field in the provided ABI."
    }
  }
}
    arguments 65 lines
  • get_address_info unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "title": "get_address_infoArguments",
  "required": [
    "chain_id",
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "title": "Address",
      "description": "Address to get information about"
    },
    "chain_id": {
      "type": "string",
      "title": "Chain Id",
      "description": "The ID of the blockchain"
    },
    "session_id": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Session Id",
      "default": null,
      "description": "Opaque session identifier."
    }
  }
}
    arguments 33 lines
  • get_tokens_by_address unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "title": "get_tokens_by_addressArguments",
  "required": [
    "chain_id",
    "address"
  ],
  "properties": {
    "cursor": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Cursor",
      "default": null,
      "description": "The pagination cursor from a previous response to get the next page of results."
    },
    "address": {
      "type": "string",
      "title": "Address",
      "description": "Wallet address"
    },
    "chain_id": {
      "type": "string",
      "title": "Chain Id",
      "description": "The ID of the blockchain"
    },
    "session_id": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Session Id",
      "default": null,
      "description": "Opaque session identifier."
    }
  }
}
    arguments 46 lines
  • nft_tokens_by_address unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "title": "nft_tokens_by_addressArguments",
  "required": [
    "chain_id",
    "address"
  ],
  "properties": {
    "cursor": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Cursor",
      "default": null,
      "description": "The pagination cursor from a previous response to get the next page of results."
    },
    "address": {
      "type": "string",
      "title": "Address",
      "description": "NFT owner address"
    },
    "chain_id": {
      "type": "string",
      "title": "Chain Id",
      "description": "The ID of the blockchain"
    },
    "session_id": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Session Id",
      "default": null,
      "description": "Opaque session identifier."
    }
  }
}
    arguments 46 lines
  • get_transaction_info unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "title": "get_transaction_infoArguments",
  "required": [
    "chain_id",
    "transaction_hash"
  ],
  "properties": {
    "chain_id": {
      "type": "string",
      "title": "Chain Id",
      "description": "The ID of the blockchain"
    },
    "session_id": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Session Id",
      "default": null,
      "description": "Opaque session identifier."
    },
    "transaction_hash": {
      "type": "string",
      "title": "Transaction Hash",
      "description": "Transaction hash"
    },
    "include_raw_input": {
      "anyOf": [
        {
          "type": "boolean"
        },
        {
          "type": "null"
        }
      ],
      "title": "Include Raw Input",
      "default": false,
      "description": "If true, includes the raw transaction input data."
    }
  }
}
    arguments 46 lines
  • get_chains_list unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "title": "get_chains_listArguments",
  "properties": {
    "query": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Query",
      "default": null,
      "description": "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."
    },
    "session_id": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Session Id",
      "default": null,
      "description": "Opaque session identifier."
    }
  }
}
    arguments 32 lines
  • __unlock_blockchain_analysis__ unknown never probed

    Initializes a Blockscout MCP session: returns server reference data, the `blockscout-analysis` skill pointer, and the URI resolution rule. Call this tool exactly once per session, before any other tool, and reuse its payload for the rest of the session; do not call it again.

    mcp-tool

    {
  "type": "object",
  "title": "__unlock_blockchain_analysis__Arguments",
  "properties": {}
}
    arguments 5 lines
  • get_block_info unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "title": "get_block_infoArguments",
  "required": [
    "chain_id",
    "number_or_hash"
  ],
  "properties": {
    "chain_id": {
      "type": "string",
      "title": "Chain Id",
      "description": "The ID of the blockchain"
    },
    "session_id": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Session Id",
      "default": null,
      "description": "Opaque session identifier."
    },
    "number_or_hash": {
      "type": "string",
      "title": "Number Or Hash",
      "description": "Block number or hash"
    },
    "include_transactions": {
      "anyOf": [
        {
          "type": "boolean"
        },
        {
          "type": "null"
        }
      ],
      "title": "Include Transactions",
      "default": false,
      "description": "If true, includes a list of transaction hashes from the block."
    }
  }
}
    arguments 46 lines
  • get_block_number unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "title": "get_block_numberArguments",
  "required": [
    "chain_id"
  ],
  "properties": {
    "chain_id": {
      "type": "string",
      "title": "Chain Id",
      "description": "The ID of the blockchain"
    },
    "datetime": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Datetime",
      "default": null,
      "description": "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."
    },
    "session_id": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Session Id",
      "default": null,
      "description": "Opaque session identifier."
    }
  }
}
    arguments 40 lines
  • get_address_by_ens_name unknown never probed

    Useful for when you need to convert an ENS domain name (e.g. "blockscout.eth") to its corresponding Ethereum address.

    mcp-tool

    {
  "type": "object",
  "title": "get_address_by_ens_nameArguments",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "title": "Name",
      "description": "ENS domain name to resolve"
    },
    "session_id": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Session Id",
      "default": null,
      "description": "Opaque session identifier."
    }
  }
}
    arguments 27 lines
  • get_transactions_by_address unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "title": "get_transactions_by_addressArguments",
  "required": [
    "chain_id",
    "address",
    "age_from"
  ],
  "properties": {
    "age_to": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Age To",
      "default": null,
      "description": "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`."
    },
    "cursor": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Cursor",
      "default": null,
      "description": "The pagination cursor from a previous response to get the next page of results."
    },
    "address": {
      "type": "string",
      "title": "Address",
      "description": "Address which either sender or receiver of the transaction"
    },
    "methods": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Methods",
      "default": null,
      "description": "A method signature to filter transactions by (e.g 0x304e6ade). Filters the (optionally date-bounded) results to a specific method signature."
    },
    "age_from": {
      "type": "string",
      "title": "Age From",
      "description": "Start date and time (e.g 2025-05-22T23:00:00.00Z). Alone, returns all transactions to/from the address since this date."
    },
    "chain_id": {
      "type": "string",
      "title": "Chain Id",
      "description": "The ID of the blockchain"
    },
    "session_id": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Session Id",
      "default": null,
      "description": "Opaque session identifier."
    }
  }
}
    arguments 78 lines
  • get_token_transfers_by_address unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "title": "get_token_transfers_by_addressArguments",
  "required": [
    "chain_id",
    "address",
    "age_from"
  ],
  "properties": {
    "token": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Token",
      "default": null,
      "description": "An ERC-20 token contract address to restrict results to a single token. If omitted, returns transfers of all tokens."
    },
    "age_to": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Age To",
      "default": null,
      "description": "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."
    },
    "cursor": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Cursor",
      "default": null,
      "description": "The pagination cursor from a previous response to get the next page of results."
    },
    "address": {
      "type": "string",
      "title": "Address",
      "description": "Address which either transfer initiator or transfer receiver"
    },
    "age_from": {
      "type": "string",
      "title": "Age From",
      "description": "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."
    },
    "chain_id": {
      "type": "string",
      "title": "Chain Id",
      "description": "The ID of the blockchain"
    },
    "session_id": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Session Id",
      "default": null,
      "description": "Opaque session identifier."
    }
  }
}
    arguments 78 lines
  • direct_api_call unknown never probed

    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).

    mcp-tool

    {
  "type": "object",
  "title": "direct_api_callArguments",
  "required": [
    "chain_id",
    "endpoint_path"
  ],
  "properties": {
    "cursor": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Cursor",
      "default": null,
      "description": "The pagination cursor from a previous response to get the next page of results."
    },
    "method": {
      "enum": [
        "GET",
        "POST"
      ],
      "type": "string",
      "title": "Method",
      "default": "GET",
      "description": "HTTP method used for the upstream call. Use POST with json_body."
    },
    "chain_id": {
      "type": "string",
      "title": "Chain Id",
      "description": "The ID of the blockchain"
    },
    "json_body": {
      "anyOf": [
        {
          "type": "object",
          "additionalProperties": true
        },
        {
          "type": "null"
        }
      ],
      "title": "Json Body",
      "default": null,
      "description": "JSON request body for POST requests."
    },
    "session_id": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Session Id",
      "default": null,
      "description": "Opaque session identifier."
    },
    "query_params": {
      "anyOf": [
        {
          "type": "object",
          "additionalProperties": true
        },
        {
          "type": "null"
        }
      ],
      "title": "Query Params",
      "default": null,
      "description": "Optional query parameters forwarded to the Blockscout API."
    },
    "endpoint_path": {
      "type": "string",
      "title": "Endpoint Path",
      "description": "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."
    }
  }
}
    arguments 84 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/4b9a3ad6761a84b2/badge.svg)](https://brick.blue/agent/4b9a3ad6761a84b2)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on blockscout.com 2 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.