Precision tools that let AI agents measure the Pons market — without ever touching a wallet.
LATHE is a working Model Context Protocol server for Robinhood Chain. It answers the questions creators and traders actually ask — how much fee is unclaimed, is this token close to graduating, what launched in the last 24 hours, where are the hunter wallets moving — straight from the chain and the Pons API. No transactions. No signing. No private keys, ever.
→ tools/call pons_fee_check "token": "0xaf98…041d" // $AGESIC ← result "creatorTaxBps": 200, "curveStage": { "tradingFee": "0", "creatorTax": "0", "totalUsd": 0 }, "escrowStage": { "balance": "0.93221299", "balanceUsd": 1919.01 }, "totalUnclaimed": "0.93221299 ETH" ✓ both stages read — curve 0 ≠ no fees
Every tool is a measurement, not an action. Pick a tool to see exactly what goes in, what comes back, and the trap it was built to avoid — then run it live, right here in the panel.
Runs entirely in your browser against the same public sources the MCP server reads — read-only, no keys, no signing, nothing is written on-chain. For full agent use (any MCP host, any workflow) you still install the local server below; this runner is the same read logic, on the same sources.
The test harness is a real MCP client talking over stdio to the real Robinhood Chain RPC, the live Pons API, and Coinbase — 24 checks, all passing, run 2026-11-11.
checks passed in the final live run — Node v24.22.1 · @modelcontextprotocol/sdk 1.32.2
The first run failed 2 checks — both were test-harness bugs (proxy env not inherited by the spawned server; an over-strict assertion). The server code was right; the harness was fixed and the run repeated green.
An agent asks a question in plain MCP. LATHE reads two sources and refuses to guess when either one is ambiguous.
Claude, or any MCP host, calls e.g. pons_fee_check with a token address.
LATHE validates it — a malformed address is rejected before any network call.
Metadata from the Pons API (curve, creator, tax, phase, progress), raw balances from the
Robinhood Chain RPC. If the API is silent, LATHE decodes the factory's
getLaunchedToken struct on-chain instead.
Fees are read at the curve and the escrow contract before a total is reported. USD comes from the Coinbase public rate. The answer carries its sources, so the agent can show its work.
Curve selectors quoteFeeBalance + creatorTaxBalance, then escrow balanceOf(creator) — or balanceOfToken for token-quoted pairs. Escrow 0 never means “no fees”.
pons_new_launches estimates fees from Pons pool volume only. DexScreener volume on a non-Pons pool pays the creator nothing — LATHE never uses it.
eth_getLogs on this RPC often returns empty. LATHE never concludes “no trades” from empty logs — hunter activity is read from Pons trade data instead.
Graduation progress comes from the API's quote-raised figure — never from raw reserves, which hide the ~1.68 ETH phantom on ETH pairs.
This is the same estimate pons_new_launches runs: Pons volume × (0.7% creator share of the 1% trading fee + the creator tax the deployer set). Drag it and watch how much volume a “few hundred dollars” really takes.
Estimate only (±~5%) — “still claimable” balances from pons_fee_check are the exact on-chain numbers. Volume on non-Pons pools earns the creator $0 and is excluded.
A lathe shapes work without becoming part of it. LATHE holds the same line: it can look at anything on the chain and change nothing.
There is no wallet to configure and nothing to sign with. The server process has no key material, so there is nothing for a prompt injection or a rogue tool call to steal.
Every tool is a read: RPC view calls, the Pons API, and a public price feed. LATHE cannot buy, sell, approve, sweep, or claim — by construction, not by policy.
Fee claims remain an explicit, separate action by the creator wallet's owner. LATHE's job ends at telling you the exact amount and which stage it sits in.
Nothing to sign up for and nothing to leak. If your network needs an egress proxy, the proxy variables simply have to be visible to the server process — documented in the install notes below.
Plain Node over stdio — the way MCP hosts already expect to talk.
Download the complete MCP server source (README, src/, tests, package.json — no node_modules), unzip it, then run the commands on the right from inside the unzipped lathe folder.
Download the server source (.zip)
One dependency: the official MCP SDK. npm test runs the full live suite (24 checks, ~25 seconds) against the real chain.
Add the server to your host's config (Claude Desktop shown) with the absolute path to src/index.js.
“Check the unclaimed fees on this token”, “what launched in the last hour”, “are the hunters active?” — the agent picks the tool.
HTTPS_PROXY / HTTP_PROXY and
NODE_USE_ENV_PROXY=1 to the config's env block, or every tool fails with “fetch failed”.# unzip the download, then inside the lathe folder cd mcp-server npm install # @modelcontextprotocol/sdk ^1.32.2 npm test # live test — 24 checks, ~25s npm start # stdio MCP server
{
"mcpServers": {
"lathe": {
"command": "node",
"args": ["/absolute/path/to/lathe/mcp-server/src/index.js"]
}
}
}
pons_hunter_watch scans the top 10 new tokens by 24h volume. A hunter showing 0 trades may still have traded lower-volume tokens.pons_new_launches run ±~5% against on-chain truth, and quote prices move. Exact claimable balances come from pons_fee_check.