Base Intel MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| address_reportA | One-call snapshot of any Base address: ETH balance, USDC balance, transaction count, and whether it is a smart contract or a regular wallet. Use it to sanity-check a counterparty or a payment address before sending funds. Input: a 0x address. |
| token_infoA | ERC-20 token metadata on Base, read on-chain: name, symbol, decimals, and total supply, plus whether the address really behaves like an ERC-20. Use it to verify a token contract before trusting or displaying it. Input: the token contract address (0x + 40 hex). |
| token_balanceA | How much of an ERC-20 token a wallet holds on Base, returned both human-formatted (using the token's decimals) and raw. Pass the token contract address and the holder address, both 0x + 40 hex. Example: USDC 0x833589fcd6edb6e08f4c7c32d4f71b54bda02913. |
| gas_nowA | Current gas price on the Base network (Coinbase's Ethereum L2), in gwei and wei, read live from a Base RPC node. Use before sending a Base transaction or estimating its cost. Takes no input. |
| tx_statusA | Look up a Base transaction by hash and report whether it is pending, succeeded, or failed, with from, to, value, block number, and gas used. Use it to confirm a payment or contract call landed. Input: the transaction hash (0x + 64 hex; the 0x is optional). |
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 5 tools
Tools mostly target distinct resources: address_report gives a wallet/contract snapshot, token_info gives ERC-20 metadata, token_balance gives ERC-20 holdings, gas_now gives network gas, and tx_status checks transactions. The only mild overlap is that address_report already includes USDC balance, which could overlap with token_balance for USDC, but descriptions make the intended use clear.
All names use concise snake_case noun phrases (address_report, token_info, token_balance, gas_now, tx_status) with a consistent two-word pattern. There is no mixing of camelCase, verb styles, or arbitrary conventions.
Five tools is well-scoped for a read-only Base intelligence server. Each tool earns its place by covering a distinct core query type: address, token metadata, token balance, gas, and transaction status.
The set covers the main read-only intel needs: address sanity checks, token verification, balances, gas estimation, and transaction confirmation. Minor gaps exist for block-level data, transaction history, and event/contract reads, but agents can work around these for the stated core purposes.