1scan - Blockchain Explorer API Gateway & MCP Server

What is 1scan - Blockchain Explorer API Gateway & MCP Server?

1scan is a unified API gateway that integrates multiple etherscan-like blockchain explorer APIs and provides an MCP (Model Context Protocol) server so AI assistants (e.g., Claude in Cursor IDE) can query on-chain data. It serves developers who need a single endpoint to access balances, transactions, contracts, and more across many EVM networks.

How to use 1scan - Blockchain Explorer API Gateway & MCP Server?

Install via go install github.com/huahuayu/1scan@latest or build from source. Create a config.json with your API keys and rate limits per chain (e.g., for Ethereum chain ID 1). Run the API server with 1scan -config config.json and the MCP server with 1scanmcp -config config.json. In Cursor IDE, add an MCP server with the URL http://localhost:3000/mcp/sse. Customize MCP parameters (-port, -path, -transport for SSE or stdio).

Key features of 1scan - Blockchain Explorer API Gateway & MCP Server

• Unified endpoint for 27+ EVM blockchain explorers
• API load balancing across multiple keys per network
• Rate limit management for each API key
• Custom API key support via URL parameters
• MCP server exposing 20+ blockchain data tools to AI models

Use cases of 1scan - Blockchain Explorer API Gateway & MCP Server

• AI coding assistants (Cursor IDE) checking wallet balances on any supported chain
• Automated contract analysis (ABI, source code) during development
• Multi‑chain gas price comparison in real time
• Monitoring token transfers (ERC-20/ERC-721) for a given address
• Retrieving transaction receipts and logs for debugging

FAQ from 1scan - Blockchain Explorer API Gateway & MCP Server

What does 1scan do that individual explorer APIs do not?

1scan aggregates multiple etherscan‑compatible APIs behind a single gateway, handles load balancing across keys, and adds an MCP interface for AI assistants. You still need your own API keys from each explorer.

What are the runtime dependencies of 1scan?

The server is written in Go and has no external database or runtime beyond the binary. Each user must provide API keys for the blockchains they wish to query.

Where does blockchain data come from?

1scan does not store data itself. It proxies requests to the official explorer APIs (e.g., Etherscan, BscScan) using the API keys you supply. All data originates from the respective blockchains.

What transport protocols does the MCP server support?

The MCP server supports both SSE (Server‑Sent Events) and stdio transports. The default is SSE; you can switch with -transport stdio.

How do I authenticate to use 1scan?

Authentication is done via API keys placed in the configuration file. Each chain entry maps one or more keys to a rate limit. There is no built‑in user authentication for the 1scan server itself.