_ registry / mcp http-sse · checked 2h ago

pumppill

https://api.pumppill.org

Registry code: f6d17b0bce68e518

api record

PumpPill answers two questions about a token contract, for

Robinhood Chain (an Arbitrum Orbit L2, chain ID 4663) and Solana:

endpoint
https://api.pumppill.org/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is pumppill live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is pumppill free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does pumppill have?
30 tools: rh_ticker_resolve, rh_token_safety, agent_sell, rh_scan_now, x_chatter, agent_buy, fomo_trader, rh_deployer_record, ….
Is pumppill safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.5%

90 days 99%· all time 99%

latency
1,351ms

last good check

priced tools
1

of 30 tools

_ answered our checks, 90 days 390 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· HTTP 522
_ what it is for
used for
  • check a token contract for safety risks
  • find the real contract for a ticker
  • review a deployer wallet record
  • buy or sell a token via trade bot
takes → gives
text → data
tools
23 reads2 moves money
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 30 tools
1 paid15 open 14 never probed 16 of 30 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • premium_calls_recent reads 0.1 USDC paid 10h ago

    MEMBERS: the premium call table, the Solana tokens PumpPill logged for members, newest first, with the market cap at logging and the move since. Needs a PumpPill membership (Authorization: Bearer <claim>, from pumppill.org/premium) or one x402 payment per call (USDC on Base). Each row cleared an attention filter (a promoter with real reach, or a moving narrative): a filter on attention, not a prediction or a recommendation. Narrative and trend columns are deliberately withheld.

    mcp-tool

    {
      "type": "object",
      "title": "premium_calls_recentArguments",
      "properties": {
        "hours": {
          "type": "integer",
          "title": "Hours",
          "default": 24
        },
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 25
        }
      }
    }
    arguments 16 lines
  • rh_early_wallets reads open 6h ago

    Robinhood Chain wallets whose first buy landed in the early window of tokens that later crossed $100K, with the feed's base rate (meta.early_base_rate) beside every rate. A record is a fact about timing, not a forecast; quote a wallet's rate only with the base rate. Wallets are removed for spraying, underperforming the base rate, or silence.

    mcp-tool

    {
      "type": "object",
      "title": "rh_early_walletsArguments",
      "properties": {
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 25
        },
        "window": {
          "type": "string",
          "title": "Window",
          "default": "30d"
        }
      }
    }
    arguments 16 lines
  • sol_early_wallets reads open 6h ago

    Solana wallets recorded among a token's first buyers on tokens whose peak later reached 5x the scan cap, with the base rate (meta.base_5x, about one in twenty) beside every rate. Sprayers, at-or-below-base and silent wallets are removed with the reason. Wallet identity showed no out-of-sample edge on Solana: this answers who was early, not who to copy.

    mcp-tool

    {
      "type": "object",
      "title": "sol_early_walletsArguments",
      "properties": {
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 25
        }
      }
    }
    arguments 11 lines
  • fomo_gathering reads open 2h ago

    Tokens that several different traders on the FOMO app bought inside a window (default 3 traders in 60 minutes), on Robinhood Chain and Solana, most traders first. Each row has the latest and the first buy seen with their market caps, how many of those traders are still in, and pumppill_read, PumpPill's own risk answer for the token ('none stored' is a gap, not a clean bill). FOMO's feed shows large buys only: this counts FOMO users, not all buyers, and carries no trade sizes.

    mcp-tool

    {
      "type": "object",
      "title": "fomo_gatheringArguments",
      "properties": {
        "chain": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Chain",
          "default": null
        },
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 25
        },
        "min_traders": {
          "type": "integer",
          "title": "Min Traders",
          "default": 3
        },
        "window_minutes": {
          "type": "integer",
          "title": "Window Minutes",
          "default": 60
        }
      }
    }
    arguments 33 lines
  • rh_flagged_recent reads open 2h ago

    Tokens whose latest scan in the last 30 days found HIGH or CRITICAL structural risk, with the findings named. Each is a finding with evidence, not a verdict on price and not an accusation. Shows what the current wave of bad launches looks like; never a list to trade against.

    mcp-tool

    {
      "type": "object",
      "title": "rh_flagged_recentArguments",
      "properties": {
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 25
        }
      }
    }
    arguments 11 lines
  • whats_moving reads open 17h ago

    One call for 'what is happening right now' on Robinhood Chain and Solana: the tokens FOMO app traders are gathering on (with PumpPill's read of each), the calls PumpPill's room posted (a few minutes behind unless a member asks), and newly flagged Robinhood Chain tokens. Pass the as_of from the last answer as `since` to get only what changed. A list of what moved, not of what to buy: flags are findings and trader counts are counts.

    mcp-tool

    {
      "type": "object",
      "title": "whats_movingArguments",
      "properties": {
        "chain": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Chain",
          "default": null
        },
        "since": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Since",
          "default": null
        }
      }
    }
    arguments 30 lines
  • agent_status reads open 17h ago

    Whether the member's agent is switched on, the wallet's ETH, the member's agent limits and what is left of today's, whether red flags are refused, and the last five orders. Call it before a first trade and after any error. Needs the member's agent key (X-Agent-Key: ppa_..., made in PumpPill's Telegram trade bot under Settings, AI agent).

    mcp-tool

    {
      "type": "object",
      "title": "agent_statusArguments",
      "properties": {}
    }
    arguments 5 lines
  • best_calls reads open 17h ago

    The room's calls that reached 2x, 5x, 10x or 20x+ after the post, on Solana and Robinhood Chain, ONLY where PumpPill's own price readings after the call confirm the peak (a peak seen on one odd pool is left out). Each row: entry market cap at the post, peak, multiple, when it was called and why. The best of the room, not its record: room_calls is the full list with losers. A day behind the members.

    mcp-tool

    {
      "type": "object",
      "title": "best_callsArguments",
      "properties": {
        "days": {
          "type": "integer",
          "title": "Days",
          "default": 30
        },
        "chain": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Chain",
          "default": null
        }
      }
    }
    arguments 23 lines
  • rule_matches reads open 10h ago

    The Robinhood Chain tokens that pass every filter of a member's rule right now, judged by PumpPill on its side. `rule` is the code (pp1....) the member copies from pumppill.org/customize. Each token comes with each filter's reading. A token passing is a match to the member's own rule, not a recommendation; compare with the last check to find NEW passes. Up to 40, biggest first.

    mcp-tool

    {
      "type": "object",
      "title": "rule_matchesArguments",
      "properties": {
        "rule": {
          "type": "string",
          "title": "Rule",
          "default": ""
        }
      }
    }
    arguments 11 lines
  • my_watched_wallets reads open 25h ago

    MEMBERS: the Robinhood Chain wallets this member follows: capital (what each can move), record (counts beside the chain's base rate), activity in the window, and the events that fired. Needs a PumpPill membership (Authorization: Bearer <claim>, from pumppill.org/premium) or one x402 payment per call (USDC on Base). Capital is size, not correctness; a rate is never shipped without its denominator. No activity means not seen moving, not gone quiet; sell sizes are floors, never profit.

    mcp-tool

    {
      "type": "object",
      "title": "my_watched_walletsArguments",
      "properties": {
        "days": {
          "type": "integer",
          "title": "Days",
          "default": 7
        }
      }
    }
    arguments 11 lines
  • membership_status reads open 25h ago

    Whether the claim this client sends is an active PumpPill membership, its tier, and when it renews. An unauthenticated call answers signed_in=false, not an error. Nothing about the claim itself is returned.

    mcp-tool

    {
      "type": "object",
      "title": "membership_statusArguments",
      "properties": {}
    }
    arguments 5 lines
  • room_calls open 25h ago

    The calls PumpPill's room posted on Solana and Robinhood Chain, newest first, each with the rule that fired (whale buy, revival, early detection, agreement between systems), the market cap at the post, the move since, the 7-day peak and whether it died. Losers are in the list. Open to everyone a few minutes behind (delay_minutes says how far); a member's claim reads it live. A count of calls is not a success rate.

    mcp-tool

    {
      "type": "object",
      "title": "room_callsArguments",
      "properties": {
        "days": {
          "type": "integer",
          "title": "Days",
          "default": 7
        },
        "chain": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Chain",
          "default": null
        },
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 25
        }
      }
    }
    arguments 28 lines
  • rh_chain_stats reads open 6h ago

    How Robinhood Chain measures from PumpPill's index, recomputed hourly with the method in the payload: tokens seen, forward-measured outcomes, how many doubled, 5x, 10x or crossed $100K, how many are stock-quoted. Quote computed_at, not the time you asked. Counts, not a success rate: entry is the market cap at logging.

    mcp-tool

    {
      "type": "object",
      "title": "rh_chain_statsArguments",
      "properties": {}
    }
    arguments 5 lines
  • rh_whale_wallets reads open 2h ago

    Wallets holding 10+ ETH or $50K+ in tokens, read as on-chain balances. Tiers by dollars held (mega, whale, mini, large); positions_top names each wallet's three largest holdings. Measures who CAN move a pool, never who is right or who to follow: most listed wallets hold rather than trade (meta.trading_30d). sort='active' orders by trades.

    mcp-tool

    {
      "type": "object",
      "title": "rh_whale_walletsArguments",
      "properties": {
        "sort": {
          "type": "string",
          "title": "Sort",
          "default": "balance"
        },
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 25
        }
      }
    }
    arguments 16 lines
  • rh_stock_pairs reads open 13h ago

    Memecoins quoted in TOKENIZED STOCKS on Robinhood Chain. Pass a stock symbol (NVDA, SPY, TSLA) for the trading, unflagged tokens quoted in it with liquidity and latest scan risk; omit it for every stock with a count. This pairing exists on no other chain.

    mcp-tool

    {
      "type": "object",
      "title": "rh_stock_pairsArguments",
      "properties": {
        "stock": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Stock",
          "default": null
        }
      }
    }
    arguments 18 lines
  • outcomes_measured open 10h ago

    Forward-measured outcomes across both chains: the share of logged tokens that doubled, reached 5x, 10x, or never moved. Entry is the market cap at the MOMENT OF LOGGING, never backfilled, and losers are in the denominator: a population measurement, not a track record. Recomputed hourly; a call during the recompute may take 45s or answer error='recomputing', and a retry a minute later is instant.

    mcp-tool

    {
      "type": "object",
      "title": "outcomes_measuredArguments",
      "properties": {}
    }
    arguments 5 lines
  • rh_ticker_resolve reads unknown 38h ago

    The ONE Robinhood Chain contract worth naming for a ticker: alive, $10K+ in its pool, not flagged HIGH or CRITICAL. Other contracts using the name come back as a count, never a list. found=false means nothing clears the gate, which is itself the answer.

    mcp-tool

    {
      "type": "object",
      "title": "rh_ticker_resolveArguments",
      "required": [
        "symbol"
      ],
      "properties": {
        "symbol": {
          "type": "string",
          "title": "Symbol"
        }
      }
    }
    arguments 13 lines
  • rh_token_safety reads unknown 38h ago

    Stored safety read for one Robinhood Chain token (0x + 40 hex): sellability, launch flags with evidence, where the launch money went, and the move since PumpPill first logged it. Never triggers a scan. found=false means not yet indexed, not safe; the miss is queued for reading. deep=true means the economics, lock, operator and thesis passes ran. A flag is a finding, not a prediction. `fomo`, when present, is what FOMO app traders did with it: 24h counts, recent trades, the first buy seen and who is still in (large trades only, no sizes).

    mcp-tool

    {
      "type": "object",
      "title": "rh_token_safetyArguments",
      "required": [
        "address"
      ],
      "properties": {
        "address": {
          "type": "string",
          "title": "Address"
        }
      }
    }
    arguments 13 lines
  • agent_sell moves money unknown never probed

    Sell part or all of a Robinhood Chain token the member holds in their PumpPill trade bot wallet, as a percent of the holding (1-100). Needs the member's agent key (X-Agent-Key: ppa_..., made in PumpPill's Telegram trade bot under Settings, AI agent). A sell is never refused for the token's read. Written down before it is placed; poll agent_order for the result. Moves real money: confirm with the member first.

    mcp-tool

    {
      "type": "object",
      "title": "agent_sellArguments",
      "properties": {
        "pct": {
          "type": "integer",
          "title": "Pct",
          "default": 100
        },
        "address": {
          "type": "string",
          "title": "Address",
          "default": ""
        }
      }
    }
    arguments 16 lines
  • rh_scan_now unknown never probed

    MEMBERS: read one Robinhood Chain contract FRESH, when rh_token_safety said found=false or the stored read is stale. Needs a PumpPill membership (Authorization: Bearer <claim>, from pumppill.org/premium) or one x402 payment per call (USDC on Base). Slow (10-20s cold; do not retry). Capped per member and per day; the answer reports the budget and a refusal names the cap and its reset (00:00 UTC). A read from the last few minutes is served from the store without spending. Not idempotent: each call may spend the cap.

    mcp-tool

    {
      "type": "object",
      "title": "rh_scan_nowArguments",
      "properties": {
        "address": {
          "type": "string",
          "title": "Address",
          "default": ""
        }
      }
    }
    arguments 11 lines
  • x_chatter unknown never probed

    MEMBERS: what X has been saying about one contract: posts naming the address in their text, distinct accounts, combined reach, acceleration, and each poster's record on earlier calls. Needs a PumpPill membership (Authorization: Bearer <claim>, from pumppill.org/premium) or one x402 payment per call (USDC on Base). Reads X live before answering when the hourly budget allows (the live field says); the stored corpus is always underneath. A SAMPLE of X: zero means PumpPill saw none, and silence on an EVM contract is normal. Counts, reach and record; no sentiment or hype score. Each call may spend a live-read budget.

    mcp-tool

    {
      "type": "object",
      "title": "x_chatterArguments",
      "properties": {
        "contract": {
          "type": "string",
          "title": "Contract",
          "default": ""
        }
      }
    }
    arguments 11 lines
  • agent_buy moves money unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "title": "agent_buyArguments",
      "properties": {
        "eth": {
          "type": "number",
          "title": "Eth",
          "default": 0
        },
        "again": {
          "type": "boolean",
          "title": "Again",
          "default": false
        },
        "address": {
          "type": "string",
          "title": "Address",
          "default": ""
        }
      }
    }
    arguments 21 lines
  • fomo_trader reads unknown 38h ago

    What one trader on the FOMO app did in the last 7 days, by FOMO name: buys with the market cap at the buy, sells with the realized profit the feed reported, the tokens touched, a record once 15 buys have been scored, and the Robinhood Chain wallet when PumpPill has matched one. Large trades only, no sizes; found=false means not seen in our data (it starts 2026-09-30), not that the trader is inactive.

    mcp-tool

    {
      "type": "object",
      "title": "fomo_traderArguments",
      "required": [
        "handle"
      ],
      "properties": {
        "handle": {
          "type": "string",
          "title": "Handle"
        }
      }
    }
    arguments 13 lines
  • rh_deployer_record reads unknown never probed

    What one Robinhood Chain wallet has launched and how those went: tokens, liveness, liquidity, which crossed $100K. Factory and relayer wallets above the launch ceiling get no record, and so does a wallet with a single launch. No success rate is computed: the rows hold only what crossed.

    mcp-tool

    {
      "type": "object",
      "title": "rh_deployer_recordArguments",
      "required": [
        "address"
      ],
      "properties": {
        "address": {
          "type": "string",
          "title": "Address"
        }
      }
    }
    arguments 13 lines
  • agent_order reads unknown never probed

    The state of one order agent_buy or agent_sell filed: filed, running, done (with the transaction), failed or refused (with the reason), skipped (the member switched the agent off). Needs the member's agent key (X-Agent-Key: ppa_..., made in PumpPill's Telegram trade bot under Settings, AI agent).

    mcp-tool

    {
      "type": "object",
      "title": "agent_orderArguments",
      "properties": {
        "order_id": {
          "type": "integer",
          "title": "Order Id",
          "default": 0
        }
      }
    }
    arguments 11 lines
  • fetch reads unknown 13h ago

    Fetch one result by the id search returned (rh:<address>, sol:<mint> or learn:<slug>). A token id returns the stored read as text with its citation and as-of time; a learn id returns the lesson's full text and, when it has a video, the transcript. Never triggers a scan; a missing read says so.

    mcp-tool

    {
      "type": "object",
      "title": "fetchArguments",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "title": "Id"
        }
      }
    }
    arguments 13 lines
  • exit_check unknown 13h ago

    Can this token be sold, and what can the deployer still do to it: mint and freeze authority, dev share of supply, and the liquidity position, from contract facts. Open to everyone, cache-only. have_record=false means no read, not safe. Fields are null when unknown rather than guessed. Facts, not advice.

    mcp-tool

    {
      "type": "object",
      "title": "exit_checkArguments",
      "required": [
        "address"
      ],
      "properties": {
        "address": {
          "type": "string",
          "title": "Address"
        }
      }
    }
    arguments 13 lines
  • sol_token_detail reads unknown 21h ago

    Any Solana token by mint (base58): holders, bundled-launch read, what the deployer still holds, socials, and meta.verdict, one sentence on whether it trades, can be sold, what the dev holds and how far it has run. Start from the verdict; the rest is evidence. A clean read is not a reason to buy. depth='quick_scan' means a token PumpPill never logged: contract and holders only, no entry or peak. `fomo`, when present, is what FOMO app traders did with it: 24h counts, recent trades, the first buy seen and who is still in (large trades only, no sizes).

    mcp-tool

    {
      "type": "object",
      "title": "sol_token_detailArguments",
      "required": [
        "mint"
      ],
      "properties": {
        "mint": {
          "type": "string",
          "title": "Mint"
        }
      }
    }
    arguments 13 lines
  • search reads unknown 21h ago

    Find PumpPill's read for a query: a Robinhood Chain address (0x + 40 hex), a Solana mint (base58), or a ticker such as HOOD. Returns ids for fetch. For a ticker the result is the one Robinhood Chain contract that clears the gate (alive, $10K+ pool, not flagged HIGH or CRITICAL) with the count of others using the name, then Solana tokens PumpPill holds under that exact name, marked as name matches. No results is an honest miss, not a clean bill. A question in words (how do exits work, what is a liquidity lock) searches PumpPill's lessons at /learn instead and returns learn:<slug> ids with a matching passage.

    mcp-tool

    {
      "type": "object",
      "title": "searchArguments",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "title": "Query"
        }
      }
    }
    arguments 13 lines
  • rh_wallet_record reads unknown 21h ago

    One Robinhood Chain wallet's holdings and trades off the chain's own feed. A sell's size is derived from the router's minimum-out, so it is a floor, never profit. Many addresses on this chain are routing contracts, not people. `fomo_trader`, when present, names the FOMO app trader this wallet was matched to.

    mcp-tool

    {
      "type": "object",
      "title": "rh_wallet_recordArguments",
      "required": [
        "address"
      ],
      "properties": {
        "address": {
          "type": "string",
          "title": "Address"
        }
      }
    }
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id f6d17b0bce68e518.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/f6d17b0bce68e518/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/f6d17b0bce68e518/badge.svg)](https://brick.blue/agent/f6d17b0bce68e518?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.