TRNCH MCP server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRNCH_API_KEY | No | Your TRNCH bot API key (e.g. trnch_bot_...). Optional: trnch_stats and the trnch_register tools work without a key, but trading tools require it. When using the remote MCP server, provide it as the Authorization header "Bearer trnch_bot_YOUR_KEY"; with the stdio bridge, set it in the TRNCH_API_KEY environment variable. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| trnch_statsA | Read live public numbers for the last 24 hours: tokens spotted, tokens in the Heat, tokens kept out as High risk, rugs detected, median detection delay in seconds, number of routers and the bot fee in percent. No key needed. Use it first to judge whether TRNCH screening is worth routing through. |
| trnch_register_messageA | Step 1 of 2 to get an API key, no browser. Returns { message }: the exact text your wallet must sign with personal_sign (EIP-191). It is valid for 10 minutes and moves no funds. Then call trnch_register with the signature. |
| trnch_registerA | Step 2 of 2: send the message from trnch_register_message and its signature; returns { key, prefix, wallet } with status 201. The key is shown once, store it. The wallet must hold 10 USDG or 0.004 ETH on Robinhood Chain (402 otherwise); 3 keys max per wallet (409); 400 if the signature or message does not match. |
| trnch_heatA | Read the live Heat: heat holds tokens screened by TIA and ranked by Heat score; new holds just-spotted tokens not yet screened (higher risk). Each token is an opaque id with rank, Heat score, price, liquidity, volume, price changes and entry time; pass id to trnch_buy or trnch_sell. Returns nextSince: pass it back as since to get only new entries, and dedupe by id. Poll at most every few seconds. Requires the API key from trnch_register, sent as Authorization: Bearer . |
| trnch_quoteA | Quote any pair across six routers (KyberSwap, LI.FI, Uniswap, 0x, SushiSwap, 1inch) without building a transaction. Returns the best amount out, already net of the TRNCH fee, and the router. Use it to compare before buying; to trade, call trnch_buy or trnch_sell instead. 409 if a token is not tradable through TRNCH. Requires the API key from trnch_register, sent as Authorization: Bearer . |
| trnch_buyA | Build a buy in one call: quotes six routers and returns the best route as a transaction for the key's wallet to sign. Give tokenId or token, and amountUsd (paid in USDG) or amountIn with tokenIn. The TRNCH fee (0.5%) is already deducted from the quote. Returns { router, quote, approval, tx, chainId, from }: if approval is not null, send it first, then sign and send tx from the same wallet (chainId 4663). Nothing is sent by TRNCH. Errors: 409 token not tradable through TRNCH (kept out by TIA), 429 rate or build limit (retry-after). Requires the API key from trnch_register, sent as Authorization: Bearer . |
| trnch_sellA | Build a sell for USDG in one call: give tokenId or token, and percent of the wallet balance (read on chain) or an exact amount. Quotes six routers and returns the best route as a transaction to sign. The TRNCH fee (0.5%) is already deducted from the quote. Returns { router, quote, approval, tx, chainId, from }: if approval is not null, send it first, then sign and send tx from the same wallet (chainId 4663). Nothing is sent by TRNCH. Errors: 409 token not tradable through TRNCH (kept out by TIA), 429 rate or build limit (retry-after). Requires the API key from trnch_register, sent as Authorization: Bearer . |
| trnch_confirmA | Optional, after sending a tx from trnch_buy or trnch_sell: report its hash so the volume is credited to the TRNCH account of the key's wallet once the receipt is checked on chain. Returns an acknowledgement only; it does not send, cancel or change the transaction, and a hash that is not a swap of this wallet credits nothing. Calling it twice with the same hash changes nothing. Requires the API key from trnch_register, sent as Authorization: Bearer . |
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 has a clearly stated role, and the two-step register flow is explicitly spelled out, as is the split between trnch_quote (compare only) and trnch_buy/trnch_sell (build a tx). The only mild overlap is that buy/sell internally quote as well, so an agent must read descriptions to know when to prefer quote over buy.
All tools share a trnch_ snake_case prefix and short, predictable names, with register/register_message forming a recognizable pair. Two entries (trnch_stats, trnch_heat) are nouns rather than verbs, a minor deviation from the otherwise verb-based pattern.
Eight tools is well matched to the narrow purpose of screening and routing swaps through TRNCH. Each tool maps to a distinct step (auth, stats, screening feed, quote, trade, confirmation) with nothing redundant.
The surface covers auth, stats, live Heat screening, quoting, buying, selling, and optional trade confirmation, which are the core lifecycle steps. Gaps exist: no tool to read wallet balances/positions directly, no trade history or key revocation/listing, which agents may need to work around.