TON Data MCP Server
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_balanceA | Получить баланс TON кошелька по адресу. Адрес начинается с EQ или UQ. |
| get_token_priceA | Получить цену токена на STON.fi по его контракту. Для TON используй адрес EQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAM9c |
| get_market_overviewB | Обзор рынка TON: текущий блок блокчейна, цена TON к USDT |
| search_tokensB | Поиск токенов на STON.fi по названию или символу |
| get_transactionsC | Последние транзакции TON кошелька |
| get_blockchain_infoA | Текущее состояние блокчейна TON (номер блока, шард) |
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 TON data: wallet balance, blockchain state, market overview, token price, transactions, and token search. No two tools have overlapping purposes.
All tools follow a consistent snake_case verb_noun pattern (e.g., get_balance, search_tokens), making the set predictable and easy to navigate.
6 tools is well-scoped for a TON data server, covering key data points without being too sparse or bloated.
The set covers essential TON data operations (balance, transactions, blockchain info, market data, token queries). Minor gaps exist, such as missing account state or NFT data, but core workflows are supported.