hoton-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOTON_MAX_ORDER | No | Optional safety cap — orders above it are refused. | |
| HOTON_BACKEND_URL | No | The hoton backend the server talks to. | https://hoton.up.railway.app |
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 |
|---|---|
| hoton_use_walletA | Store the agent's TON wallet identity (from @ton/mcp) for this session so buy tools can target it. Call this once before buying. |
| hoton_use_referrerA | Set a referral link/short-name/wallet (e.g. 'hoton.tg/jeribond') so subsequent purchases credit that referrer 35% of the fee. Only set this if the user named a referrer. The house link (hoton.tg/hoton) or none means no commission. |
| hoton_find_recipientA | Look up a Telegram @username before buying, to confirm the right person (returns display name + photo). For premium, pass months. Optional — buy tools also resolve usernames themselves. |
| hoton_buy_starsA | Build an order to send Stars to one Telegram user. Returns messages[] to sign with @ton/mcp. Extract a referrer from the user's prompt if they named one. |
| hoton_buy_stars_bulkA | Build ONE order sending the same star amount to 1–10 Telegram users. Returns messages[] (one per recipient) to sign with @ton/mcp in a single transaction. |
| hoton_buy_premiumA | Build an order to gift Telegram Premium (3, 6 or 12 months) to one user. Returns messages[] to sign with @ton/mcp. |
| hoton_buy_premium_bulkA | Build ONE order gifting the same Premium duration to 1–10 users. Returns messages[] (one per recipient) to sign with @ton/mcp. |
| hoton_topup_gramA | Build an order to top up one Telegram account with GRAM (the native chain coin). Returns messages[] to sign with @ton/mcp. GRAM only. |
| hoton_topup_gram_bulkA | Build ONE order topping up 1–10 Telegram accounts with the same GRAM (native chain coin) amount each. Returns messages[] to sign with @ton/mcp. GRAM only. |
| hoton_confirmA | Call after @ton/mcp send_raw_transaction signs the order. I poll the TON chain for the settled transaction, return whether it's delivered + a tonviewer link, and record it in Hoton's history + referral. Pass |
| hoton_statusA | Returns whether Hoton/Fragment is healthy right now. Call before buying if unsure; if unhealthy, tell the user to try later instead of buying. |
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 11 tools
Each tool targets a distinct resource and action. The buy/topup tools are clearly separated by product type (stars, premium, gram) and by single vs bulk, and the auxiliary tools (wallet, referrer, find_recipient, status, confirm) each have a unique role.
Tool names follow a consistent verb_noun pattern with a 'hoton_' prefix, and bulk variants add '_bulk' for predictability. Minor deviations exist: 'hoton_status' and 'hoton_confirm' are not strictly verb_noun, but they are brief and unambiguous.
The 11 tools are well-scoped for the server's purpose. Each product type has a single and bulk variant, and the support tools are necessary for configuration and confirmation. No redundant tools.
The tool set covers the full purchase lifecycle: storing the wallet, setting a referrer, looking up recipients, building orders for Stars/Premium/GRAM (single and bulk), checking service health, and confirming settled transactions. No obvious gaps for the intended operations.