1scan MCP Server

Most monitoring and observability work still happens through a UI a human drives. 1scan MCP server moves it into the conversation instead. A unified API gateway for integrating multiple etherscan-like blockchain explorer APIs with Model Context Protocol (MCP) support for AI assistants.

The short version

1. API Gateway: A unified endpoint for accessing multiple blockchain explorer APIs 2. MCP Server: Allows AI models (like Claude in Cursor IDE) to directly query blockchain data

• 🔄 Unified API endpoint for multiple blockchain explorers
• ⚖️ API load balancing
• 🔑 API rate limit management
• 🎯 Custom API key support via URL parameters
• 🤖 MCP server for AI assistants to query blockchain data

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

The tools it exposes

The server publishes 14 tools. What each one is for:

• getAccountBalance — Get the balance of an account on a specific blockchain
• getTokenBalance — Get the token balance of an account on a specific blockchain
• getTransactionByHash — Get transaction details by hash
• getBlockByNumber — Get block information by block number
• getContractABI — Get the ABI for a verified contract
• getContractSourceCode — Get the source code of a verified contract
• getTokenInfo — Get information about an ERC20 token
• getGasPrice — Get current gas price on a specific blockchain
• getLogs — Get event logs matching specified parameters
• getTransaction — Get details of a transaction by its hash
• getTransactionCount — Get the number of transactions sent from an address
• getTransactionReceipt — Get transaction receipt by transaction hash

What it needs from you

Configuration is passed through the environment: YOUR_BSCSCAN_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch 1scan.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Plenty of monitoring and observability servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. 1scan's toolset — getAccountBalance, getTokenBalance, getTransactionByHash and 11 more — is a fair guide to whether it matches your workflow. It is maintained by huahuayu; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.