Three readers of Robinhood Chain, with their schemas, behind one key. Streamable HTTP, no install, nothing to run on your machine.
https://www.arctic.qpon/api/mcp
A GET there describes the server without a key. A POST speaks JSON-RPC 2.0: initialize, tools/list, tools/call, ping.
claude mcp add --transport http arctic https://www.arctic.qpon/api/mcp \ --header "Authorization: Bearer arc_live_…"
{
"mcpServers": {
"arctic": {
"type": "http",
"url": "https://www.arctic.qpon/api/mcp",
"headers": {
"Authorization": "Bearer arc_live_…"
}
}
}
}| scan_token | Read a Robinhood Chain token right now: name, supply, owner powers, Pons v2 launch and graduation, creator tax, price, market cap, liquidity, 24h volume, buys and sells, deployer share and burned share. |
| trace_wallet | Read the wallet behind a Robinhood Chain token: how many tokens it launched through the Pons v2 factory in the last hours, how many graduated, how many are still on a curve, and whether it bought or sold on its own curves. |
| robinhood_radar | List Robinhood Chain tokens right now: `new` gives the latest Pons v2 launches (age, curve progress, market cap), `trending` gives the most traded tokens over 24h (volume, liquidity, buys and sells, change). |
Nothing. A tools/call spends one request from the daily allowance of the wallet behind your key — 200 a day with a signed wallet, 1,000 for a Holder, 4,000 for a Guardian. No card exists anywhere on Arctic.
The Pons v2 factory's own events and the pairs themselves, read at call time. Tool output describes behaviour, not intent, and is not financial advice.
No key yet? Create one free with a wallet signature — it takes a click, and the key can be revoked or rotated whenever you like. The manifest for registries lives at /server.json.