Specification v0.1Read-only tools · implementedWrite windows · specified-only

Agents — eyes on the floor

The board is public data by design. pit-mcp is a read-only toolkit that gives any MCP-compatible agent — Claude Code, Cursor, Codex, Gemini CLI — the same live view of Robinhood Chain you get on this site: pool prices, trending seats, token search, public balances. Every read is stamped with its source and as-of.

What it is for

Humans watch the board. Agents read the stream. A trading bot, a monitoring script or a coding assistant can ask for the whole floor's state and get receipts, not vibes. The toolkit runs locally on your machine — it holds nothing, signs nothing, and proxies nothing.

Object model

Four objects from the floor's own language: a Seat (a pool on the board, with price / 24h move / FDV / age), a Call (one priced read, always carrying as-of), the Board (the full floor state), and Zero state (the honest placeholder when a contract does not exist yet).

Tool catalogue — six tools, all read-only

get_pool_pricein: pool — name substring or contract address
out: price · 24h move · FDV · seat age + as-of

get_trending_poolsin: limit (1–10, default 5)
out: ranked by absolute 24h move + as-of

search_tokenin: query — name or symbol substring
out: matching pools on Robinhood Chain + as-of

get_wallet_balancein: address — public 0x address
out: native ETH balance + as-of

get_erc20_balancein: token, wallet — two public addresses
out: one contract's balance for that wallet + as-of

get_token_infoin: address — token contract
out: symbol · decimals · total supply + as-of

Error contract: never invent — feed down → “the board is quiet right now”; unknown pool → “not on the board”; no demo data anywhere.

Shape of use

One line registers the toolkit with your agent host; after that the tools appear in your agent's tool list and it calls them when a question needs live data. Trading stays at your venue, in your wallet — the toolkit never constructs, signs or broadcasts anything.

Auth & boundaries

No auth — all six tools read public data. No accounts, no keys, no model proxying. If access gating ever ships (a Phase-2 question below), it will be specified in a new spec version before any code exists.

FAQ

Does it sign transactions? No — not in v0.1, and a future write window is specified-only (a preview–approval shape is drafted in SPEC §2; no code implements it).
Does it hold keys or funds? No — balances are read from public addresses only.
Does it proxy an AI model? No — data tools only.
Where does the data come from? GeckoTerminal public API and Robinhood Chain's public RPC (chain 4663) — the same sources this site shows.

Open questions

1. Should a canonical Robinhood Chain token list exist, or stay on-chain discovery only? · 2. A server-side feed endpoint on this site (demand-driven) · 3. Access gating, if $PIT ships — separate evaluation, not assumed.

SPEC v0.1 · REFERENCE IMPLEMENTATION COMPLETE · STATUS MARKERS ARE CONTRACTUAL