Toolhood/Product/How it works

From your AIto the chain and back.

Toolhood is a remote MCP server. Your AI client calls it like any other tool, and we turn those calls into live reads, simulations and signing links on Robinhood Chain.

01The path

  1. Your AI asks

    You type a question in Claude, ChatGPT, Cursor or any MCP client. The client sees Toolhood's tools and picks the ones it needs.

  2. Toolhood reads the chain

    Reads go to Robinhood Chain RPC nodes and the Blockscout explorer. Prices come from DexScreener, launches from Pons, perps from Lighter's public API. Every answer is a one-line summary plus structured JSON your AI can quote.

  3. Writes are prepared, never sent

    Ask for a transfer, a swap, a revoke or a token deploy and Toolhood builds the transaction, simulates it against the latest block and hands back a signing link. Nothing is broadcast by us.

  4. You sign in your own wallet

    The link opens our signing page. It decodes the calldata itself, simulates again, shows the balance changes and risk flags, and only then asks your wallet to sign. Your keys never leave your wallet.

  5. The result comes back

    The signing page gives you a ready line to paste back, like done, tx 0x…. Your AI reads the receipt from the chain and carries on.

02What runs where

AI clientRuns on your machine or in your browser and holds the conversation. It never gets your keys either.
Toolhood MCP serverStateless, at the edge. Checks arguments, applies rate limits, calls the data sources and returns results. It keeps usage counters for those limits, nothing else about you.
Data sourcesRobinhood Chain RPC (publicnode, dRPC, the official node), Blockscout v2, DexScreener, Pons, Lighter, and LI.FI for swap quotes.
Explanationsexplain_transaction and Ask use an open model on Workers AI, given only the decoded data. If the model is down you still get a plain rule-based summary.
Simulationeth_call and eth_estimateGas at the latest block. Nothing is sent.
Signing pageOpens in your browser. Everything it needs sits in the link fragment, which browsers never send to a server.
Your walletMetaMask, Rabby, Coinbase Wallet, OKX, Trust or any browser wallet. The only place a signature can happen.

03One call, end to endWhat a client sends, and the shape of what comes back.

Your AI sends
POST https://toolhood.xyz/mcp

{"jsonrpc": "2.0", "id": 7,
 "method": "tools/call",
 "params": {
   "name": "get_balance",
   "arguments": {"address": "0x…"}
 }}
Toolhood answers (shape)
{"jsonrpc": "2.0", "id": 7,
 "result": {
   "content": [{"type": "text",
     "text": "<one-line summary>\n\n<compact JSON>"}],
   "structuredContent": {
     "address": "0x…", "eth": "…",
     "tokens": [ … ] }
 }}

Run it for real, with live numbers, in the playground.

04LimitsNo sign-in for the free tier. Keys and the holder tier raise the limits.

TierTool callsAskHow
Free60 / min20 / dayNo key, no sign-in. Counted per IP address.
Access key120 / min50 / daySend Authorization: Bearer th_live_… (create keys on /keys with a wallet signature).
Holder600 / min200 / dayA key whose wallet holds at least 1,000,000 $TOOLHOOD, read on-chain. after launch

Limits come from the engine itself. Details in the docs.