Tegro Wallet MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TONAPI_KEY | No | Optional TonAPI key to lift the public rate limit |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ton_get_accountB | Get a TON account's GRAM balance (the native token, formerly Toncoin), status, and wallet flag. Network is TON; balances are 1:1 GRAM↔TON. |
| ton_get_jettonsB | List jetton (token) balances held by a TON address, with fiat value where the token is priced. |
| ton_get_transactionsB | Recent transactions/events for a TON address — type, GRAM amount, counterparty, comment. |
| ton_get_rateB | Current price of GRAM (the native TON token) or any jetton in a fiat currency, plus 24h change. |
| ton_get_jetton_infoB | Metadata for a jetton (token) by its master contract address: symbol, name, supply, verification. |
| ton_get_nftsC | NFTs owned by a TON address (name, collection, image). |
| ton_resolve_dnsB | Resolve a TON DNS name (e.g. foundation.ton) to its wallet address. |
| ton_validate_addressA | Validate and normalize a TON address (raw or friendly) offline — returns format, normalized raw form, and bounceable/testnet flags with a real CRC check. No network call. |
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 8 tools
Each tool targets a distinct data point: native balance, jetton balances, transactions, price rate, jetton metadata, NFTs, DNS resolution, and address validation. The only near-neighbors (ton_get_jettons for balances vs ton_get_jetton_info for metadata) are clearly distinguished by their descriptions.
All tools follow a uniform ton_<verb>_<noun> pattern with consistent verbs (get/resolve/validate). Minor singular/plural variation (account vs jettons/nfts) does not break the pattern.
Eight tools is well-scoped for a read-only TON data/wallet-query surface, with each tool earning its place and no redundancy.
Read-only coverage of balances, tokens, transactions, rates, metadata, NFTs, DNS, and validation is solid, but as a 'Wallet MCP' it lacks any write/lifecycle operations such as sending GRAM or jettons, constructing transfers, or wallet creation, leaving a notable gap.