Block MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FRAXSCAN_API_KEY | Yes | API key for the Fraxscan service. | |
| TELEGRAM_CHAT_ID | Yes | Your numeric Telegram chat ID. | |
| COINGECKO_API_KEY | No | Optional API key for CoinGecko. | |
| TELEGRAM_BOT_TOKEN | Yes | Telegram bot token obtained from BotFather. |
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": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {
"tasks": {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
}
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| convert_cryptoA | Convert cryptocurrency using real-time rates (e.g., BTC to ETH, USDC to USD). Args: amount: Volume to convert (e.g., 1.5) from_coin: Coin ID/Symbol (e.g., 'bitcoin', 'ethereum', 'usdc') to_coin: Target currency (e.g., 'usd', 'eur', 'eth') |
| get_transactionsA | Fetch the 5 latest transactions for a specific address on the FRAX Network Args: address: the wallet address to check |
| send_telegram_messageC | Send a notification to the configured Telegram Chat. Args: message: The text to send to your phone. |
| telegram_read_messagesB | Reads the last few messages sent to the bot by the user. Useful for checking if the user has replied or asked a question. |
| telegram_replyB | Sends a reply to a specific user/chat ID. Args: chat_id: The ID of the user to reply to. text: The message to send back. |
| wait_for_secondsB | Pauses execution for a set number of seconds. REQUIRED for running automated loops to reply messages. |
| wallet_checkB | Check the native token balance of a wallet across multiple blockchains. Args: address: The wallet address (must start with 0x) |
| get_gas_pricesA | Check the current gas fees (in Gwei) across multiple blockchains. Low (<10) is cheap. High (>50) is expensive. |
| health_checkA | Returns a status message that the server is live |
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 9 tools
The tool set has unclear boundaries and overlapping purposes, particularly in the Telegram-related tools. 'send_telegram_message', 'telegram_read_messages', and 'telegram_reply' all handle Telegram messaging but with ambiguous distinctions—'send_telegram_message' and 'telegram_reply' seem to serve similar functions, and 'telegram_read_messages' overlaps with monitoring interactions. Additionally, 'get_transactions' and 'wallet_check' both involve address queries but target different data (transactions vs. balances), which could cause confusion. The descriptions help somewhat, but the overlap is significant.
The naming conventions are mixed, with some tools using verb_noun patterns like 'convert_crypto' and 'get_gas_prices', while others use noun_verb like 'health_check' or inconsistent structures like 'telegram_read_messages' (noun_verb_noun) and 'wait_for_seconds' (verb_preposition_noun). This lack of a consistent pattern makes the set less predictable, though the names remain readable overall. The deviations are notable but not chaotic.
With 9 tools, the count is reasonable and well-scoped for a server covering cryptocurrency conversion, blockchain data, and Telegram integration. It's not excessive, and each tool appears to serve a distinct functional area, though some overlap exists. The number aligns well with the apparent scope, being neither too thin nor too heavy, making it appropriate for the server's purpose.
The server shows notable gaps in coverage for its implied domain of blockchain and messaging operations. For cryptocurrency conversion, tools like 'convert_crypto' and 'get_gas_prices' are present, but there's no tool for executing trades or managing wallets beyond checking balances. In Telegram functionality, basic send/reply/read tools exist, but there's no tool for configuring or managing chats. The surface covers core actions but lacks full lifecycle or advanced operations, which agents might need to work around.