PumpPill answers two questions about a token contract, for Robinhood Chain (an Arbitrum Orbit L2, chain ID 4663) and Solana: "what is wrong with this contract" - the stored safety read, and "what happened to tokens like it" - outcomes measured forward from the moment PumpPill first logged them, with losers in the denominator. Prefer `rh_token_safety` for a Robinhood Chain address (0x + 40 hex) and `sol_token_detail` for a Solana mint (base58). `rh_ticker_resolve` is the tool for "which contract is the real $NAME", which is the question that actually costs people money. Every result carries `cite` and `as_of`. Quote those. Figures are recomputed continuously and a number without its timestamp will be wrong within the hour. Two limits to carry into any answer you give from this data. A flag is a finding with evidence, not a verdict - it says what is structurally true about the contract, not what the price will do. And an outcome count is a count, not a success rate for anyone who bought: entry is the market cap at the moment of logging, which is not a price anyone was offered. FOMO is a trading app whose feed PumpPill stores. `fomo_gathering` lists the tokens several of its traders bought inside a window, with PumpPill's own read beside each; `fomo_trader` is one trader's week; a token read carries a `fomo` block. The feed shows large trades only and never a size, so say "FOMO traders", not "buyers". `whats_moving` is the one call for "what is happening right now":
0 verified, 1 failed, 0 observed risk, 0 not checked, on 22 November 2026. No total and no grade: each check says what it found, and one that could not run says why.
No timed run in the last 24 hours.
Every x402 payment we hold to the address the catalogue lists for this server’s paid tools (0xabb0…e1bb), payments an address made to itself left out.
39 tools on the last day the list was read, fingerprint eec34e32da56311f29d.
Buy a Robinhood Chain token (agent trading)
Buy a Robinhood Chain token with ETH from the member's PumpPill trade bot wallet. Needs the member's agent key (X-Agent-Key: ppa_..., made in PumpPill's Telegram trade bot under Settings, AI agent). PumpPill reads the token first and, unless the member turned refusal off, refuses a HIGH/CRITICAL read, a token it has not read, or a read too thin to clear (verdict unknown, contract powers unread), saying why. The member's own limits apply. The order is written down before it is placed; poll agent_order for the result. Moves real money: confirm the token and size with the member first.
changes statemay destroy or overwritereaches outside servicesas the server describes it; we do not call tools
| Name | Type | Required | Description |
|---|---|---|---|
| address | string | no | |
| eth | number | no | |
| again | boolean | no |
No agent registration names this server; we probe it on our own list.
A day counts as answered only when every timed run that day got every request answered; the hourly runs began 5 November 2026. Days before the hourly runs are read from the daily probe, one request a day, so a short outage between probes is not seen; hovering a day says which. Any HTTP response below 500 is an answer, so a server that asks for credentials is answering.
| Day | State | Timed runs | From |
|---|---|---|---|
| 2026-11-22 | No answer | 0 | daily probe |
| 2026-11-21 | No answer | 0 | daily probe |
| 2026-11-20 | Some runs failed | 23 | hourly runs |
| 2026-11-19 | Answered | 23 | hourly runs |
| 2026-11-18 | Some runs failed | 24 | hourly runs |
| 2026-11-17 | Answered | 23 | hourly runs |
| 2026-11-16 | Answered | 24 | hourly runs |
| 2026-11-15 | Answered | 23 | hourly runs |
| 2026-11-14 | Some runs failed | 24 | hourly runs |
| 2026-11-13 | Answered | 23 | hourly runs |
| 2026-11-12 | Answered | 23 | hourly runs |
| 2026-11-11 | Answered | 23 | hourly runs |
| 2026-11-10 | Answered | 24 | hourly runs |
| 2026-11-09 | Some runs failed | 23 | hourly runs |
| 2026-11-08 | Answered | 24 | hourly runs |
| 2026-11-07 | Answered | 18 | hourly runs |
| 2026-11-06 | Answered | 23 | hourly runs |
| 2026-11-05 | Answered | 4 | hourly runs |
Each day: the median of that day’s runs’ p50 (the line) and of their p95 (the top of the band), in milliseconds, from our server in Europe to the response headers of an MCP initialize request. An observation, not a threshold.
| Day | p50 ms | p95 ms | Runs |
|---|---|---|---|
| 2026-11-20 | 313 | 402 | 17 |
| 2026-11-19 | 329 | 522 | 23 |
| 2026-11-18 | 344 | 467 | 24 |
| 2026-11-17 | 332 | 490 | 23 |
| 2026-11-16 | 327 | 396 | 24 |
| 2026-11-15 | 313 | 386 | 23 |
| 2026-11-14 | 322 | 396 | 23 |
| 2026-11-13 | 318 | 393 | 23 |
| 2026-11-12 | 312 | 402 | 23 |
| 2026-11-11 | 312 | 392 | 23 |
| 2026-11-10 | 319 | 407 | 24 |
| 2026-11-09 | 326 | 419 | 22 |
| 2026-11-08 | 317 | 375 | 24 |
| 2026-11-07 | 320 | 390 | 18 |
| 2026-11-06 | 329 | 400 | 23 |
| 2026-11-05 | 319 | 350 | 4 |