Blockscout MCP server
{
"mcpServers": {
"blockscout": {
"type": "http",
"url": "https://server.smithery.ai/@blockscout/mcp-server/mcp"
}
}
}{
"mcpServers": {
"blockscout": {
"type": "http",
"url": "https://server.smithery.ai/@blockscout/mcp-server/mcp"
}
}
}{
"mcpServers": {
"blockscout": {
"type": "http",
"url": "https://server.smithery.ai/@blockscout/mcp-server/mcp"
}
}
}{
"servers": {
"blockscout": {
"type": "http",
"url": "https://server.smithery.ai/@blockscout/mcp-server/mcp"
}
}
}{
"mcpServers": {
"blockscout": {
"type": "http",
"url": "https://server.smithery.ai/@blockscout/mcp-server/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.13.1
What it does
This server exposes Blockscout blockchain APIs through the Model Context Protocol, allowing AI agents and automation tools to query balances, tokens, NFTs, and contract metadata across multiple chains. It is for developers integrating blockchain data access into Claude, Cursor, or other MCP-compatible tools.
- Query account balances and token holdings on multiple blockchains within Claude conversations.
- Look up NFT collections, metadata, and ownership information programmatically for analysis or reporting.
- Retrieve contract details, transaction history, and on-chain data to support blockchain research or debugging tasks.
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.