Blockscout MCP server
{
"mcpServers": {
"blockscout": {
"type": "http",
"url": "https://mcp.blockscout.com/mcp"
}
}
}{
"mcpServers": {
"blockscout": {
"type": "http",
"url": "https://mcp.blockscout.com/mcp"
}
}
}{
"mcpServers": {
"blockscout": {
"type": "http",
"url": "https://mcp.blockscout.com/mcp"
}
}
}{
"servers": {
"blockscout": {
"type": "http",
"url": "https://mcp.blockscout.com/mcp"
}
}
}{
"mcpServers": {
"blockscout": {
"type": "http",
"url": "https://mcp.blockscout.com/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 0.19.0
What it does
This MCP server wraps Blockscout APIs to expose blockchain data—balances, tokens, NFTs, contract metadata—to AI agents and tools like Claude and Cursor. It supports multiple blockchains via Blockscout PRO API configuration and provides a versioned REST API alongside MCP tools.
- Query wallet balances, token holdings, and NFT collections across multiple blockchains.
- Retrieve contract metadata, ABIs, and deployment details for blockchain analysis.
- Access transaction history, token transfers, and on-chain activity data for specific addresses or contracts.
Tools this server exposes
| Tool | Does |
|---|---|
| get_balances | Retrieve native and token balances for a blockchain address. |
| get_tokens | Query token information, holdings, and metadata. |
| get_nfts | Access NFT collections and metadata for an address. |
| get_contract_metadata | Retrieve contract details, ABIs, and deployment information. |
| get_transactions | Query transaction history and on-chain activity data. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.