mcp-otc
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ETHERSCAN_API_KEY | Yes | Your Etherscan API key (get one at https://etherscan.io/apis) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check-balanceB | Check the ETH balance of an Ethereum address |
| get-transactionsB | Get recent transactions for an Ethereum address |
| get-token-transfersC | Get ERC20 token transfers for an Ethereum address |
| get-contract-abiC | Get the ABI for a smart contract |
| get-gas-pricesA | Get current gas prices in Gwei |
| get-ens-nameB | Get the ENS name for an Ethereum address |
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 has a clearly distinct purpose targeting different Ethereum-related functions: checking balances, retrieving contract ABIs, resolving ENS names, getting gas prices, fetching token transfers, and listing transactions. There is no overlap or ambiguity in their intended use cases.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., check-balance, get-contract-abi, get-ens-name). The naming is uniform and predictable across all six tools.
With 6 tools, this server is well-scoped for its Ethereum/blockchain domain. Each tool serves a specific, essential function without redundancy, making the count appropriate and manageable.
The toolset covers key read-only operations for Ethereum interactions, including balance checks, contract data, ENS resolution, gas prices, token transfers, and transactions. A minor gap exists in write operations (e.g., sending transactions or interacting with contracts), but the provided tools are sufficient for common querying tasks.