Trnch MCP (Robinhood Chain rug checker)

Trnch is the non-custodial trading terminal for Robinhood Chain (chainId 4663). Ask any token address and TIA, the Trnch risk engine, tells you if it is a rug, a honeypot, a scam contract, a copycat or a dumped token. See the best new tokens of the last 24 hours, and trade at the best route across KyberSwap, 1inch, Uniswap, LI.FI and Sushi: every swap is returned as a transaction your own wallet signs; Trnch never holds funds. Every TIA decision is public at trnch.fun/tia.

View on trnch.fun

Hosted MCP Server

npx add-mcp 'https://trnch.fun/api/mcp'

Installs into Claude Code, Codex, Cursor and more

Documentation

Robinhood Chain MCP server

Connect Claude, Cursor or any MCP client to Robinhood Chain: screened new tokens, rug and honeypot check, best-route swaps, signed by the agent's own wallet.

Open the Heat

New tokens tracked, 24h

499

Kept out as High risk, 24h

250

Rugs detected, 7 days

1,148

New tokens tracked, 7 days

4,506

Trnch runs a remote MCP server for Robinhood Chain. An AI agent connects to one URL and gets the view Trnch traders use: new tokens screened by TIA, a rug and honeypot check for any token, and swaps at the best route across six routers. The agent keeps its own wallet and signs every transaction itself.

Add the server

The server speaks streamable HTTP at https://trnch.fun/api/mcp. In Claude Desktop, Cursor, Windsurf or any client that supports remote servers, add it by URL:

{
  "mcpServers": {
    "trnch": { "url": "https://trnch.fun/api/mcp" }
  }
}

Once the agent holds an API key, pass it as a bearer header on the same entry:

"trnch": {
  "url": "https://trnch.fun/api/mcp",
  "headers": { "Authorization": "Bearer trnch_bot_YOUR_KEY" }
}

Stdio-only clients can use the bridge in the open-source repo isonips/trnch-mcp on GitHub.

What agents can do

  • trnch_check, no key: the rug check. For any Robinhood Chain token, whether TIA keeps it out of the Heat and its public risk category. A signal, never a guarantee.
  • trnch_stats, no key: the last 24 hours in numbers, tokens spotted, kept out, rugs detected, routers and fee.
  • trnch_register_message and trnch_register: an API key from one wallet signature, no email, no browser.
  • trnch_heat: new tokens screened by TIA, ranked by momentum, with price, liquidity and volume.
  • trnch_quote: compare a pair across six routers without building a transaction.
  • trnch_buy and trnch_sell: one call returns the best route as a transaction for the agent's wallet to sign.
  • trnch_confirm: report the transaction hash so the volume is credited to the wallet.

Tokens TIA keeps out are refused: an agent cannot buy a known rug or honeypot through Trnch by mistake. Trnch never holds funds or keys.

Step-by-step tutorial

Open the Bot API

FAQ

Which MCP clients work with the Trnch server?

Any client that supports remote servers over streamable HTTP: Claude Desktop, Cursor, Windsurf and others. Stdio-only clients go through the isonips/trnch-mcp bridge.

Does the agent need a key to check a token?

No. trnch_check and trnch_stats work without a key. A key is needed to read the Heat and to trade.

Does Trnch sign or hold anything for the agent?

No. Trnch returns data and unsigned transactions. The agent's own wallet signs and sends them, and keeps the funds.

What does it cost?

Reading is free. Swaps carry a 0.5% fee, already deducted from the quoted amounts.