A
licenseA
qualityB
maintenanceMCP server with 43 tools for blockchain data — token lookups, wallet balances, live chain queries across 10+ networks, and full API documentation search.
27
120 npm
Apache 2.0
blockscout-mcp-server
by imelon2
Related Servers
Alternatives to blockscout-mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP server for Blockscout, providing agent-ready access to blockchain explorer data via natural language. It exposes tools generated from the Blockscout API spec, requiring no authentication.-
- AlicenseAqualityCmaintenanceA read-only MCP server that lets you interact with the Ethereum blockchain via natural language, providing tools for reading blocks, transactions, token metadata, events, and more, with provenance tracking and no private key access.10MIT
Pharos MCP Serverofficial
FlicenseAqualityCmaintenanceEnables querying Pharos blockchain data (EVM-compatible) through MCP, with read-only tools for blocks, transactions, balances, and contract calls, plus optional transaction broadcasting when self-hosted.14-- AlicenseNot gradedqualityCmaintenanceProvides multichain block-explorer data from Etherscan via MCP tools for token balances, contract ABI, and source code.6 npmMIT
- AlicenseAqualityAmaintenanceRead-only MCP server for Sui blockchain analytics with 44 tools covering wallets, DeFi, NFTs, token prices, transactions, fund tracing, pools, staking, Move decompilation, and MVR name resolution.191,041 npm1MIT
TDQS
A3.6/5.0
Scored across 16 tools
Disambiguation5/5
Each tool targets a distinct blockchain data type or operation—address, block, transaction, token, contract, chain, logs, etc. No two tools have overlapping purposes; even the escape hatch `direct_api_call` is clearly separate from dedicated tools.
Naming Consistency3/5
The majority of tools follow a `get_<resource>` pattern, but there are exceptions like `lookup_token_by_symbol`, `inspect_contract_code`, `nft_tokens_by_address`, and the unusual `__unlock_blockchain_analysis__`. While still readable, this mix of conventions introduces inconsistency.
Tool Count4/5
With 16 tools covering core blockchain explorer functionality—addresses, blocks, transactions, tokens, contracts, chains—the count is well-scoped. It is slightly above the ideal 3-15 range but still reasonable for the domain.
Completeness4/5
The tool set covers the main blockchain query needs: address details, block info, transactions, token balances, transfers, contract ABI/source, logs, and chains list. Minor gaps like pending transactions or general search exist, but the escape hatch `direct_api_call` mitigates them effectively.