Base MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BLOCKSCOUT_API_KEY | Yes | Your Blockscout Pro API key from https://dev.blockscout.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_wallet_balanceA | Get the native ETH balance of a wallet or contract address on Base. Args: address: The 0x-prefixed address to check. |
| get_recent_transactionsA | Get the most recent transactions for an address on Base. Args: address: The 0x-prefixed address to check. limit: Maximum number of recent transactions to return (default 10, max 50). |
| get_wallet_activityA | Compute a rough 0-100 on-chain activity score for a wallet on Base. Based on transaction count, number of unique active days, contract diversity, and wallet age (all sampled from the most recent 1,000 transactions). This is a heuristic indicator, not an official metric of any airdrop or program. Args: address: The 0x-prefixed wallet address to check. |
| check_contract_verificationA | Check whether a contract on Base has verified source code, and basic metadata. Reports source verification status, whether it's an upgradeable proxy, and whether ownership has been renounced (for contracts following the standard Ownable pattern). Args: address: The 0x-prefixed contract address to check. |
| check_rugpull_riskA | Run a heuristic rug-pull risk screen on a Base contract. Checks source verification, common scam-token code patterns (blacklists, arbitrary fee/limit changes, trading kill-switches, uncapped minting, etc.), ownership status, and proxy/upgradeability. Returns a 0-100 risk score. This is a heuristic tool, NOT a security audit — always verify manually before making decisions involving money. Args: address: The 0x-prefixed contract address to screen. |
| check_token_approvalsA | Check a wallet's active ERC-20 and NFT token approvals on Base. Scans historical Approval/ApprovalForAll events, then verifies the CURRENT on-chain state of each unique pair found (an old event doesn't mean the approval is still active — it may have been reduced or revoked since). Flags unlimited approvals as high-risk. This tool is READ-ONLY and cannot revoke anything. Args: address: The 0x-prefixed wallet address to check. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct aspect of on-chain data—contract verification, rug-pull risk, token approvals, recent transactions, wallet activity, and balance. There is no functional overlap, making it easy for an agent to select the right tool.
All tool names follow a consistent verb_noun pattern with snake_case (check_* and get_*). The verbs are descriptive and the nouns clearly indicate the resource being acted upon, forming a predictable naming scheme.
With 6 tools, the server is lean and focused on essential on-chain analysis functions for the Base ecosystem. Each tool serves a clear purpose without redundancy or unnecessary features, making the set well-scoped.
The tool set covers key queries for contract safety and wallet activity, but lacks tools for fetching specific transaction details or token metadata. These are minor gaps that agents can work around, but the core use cases are addressed.