_ registry / mcp streamable-http · checked 32m ago

paxie-launch-data

https://api.paxie.fun

Registry code: 972617e9ece626ae

api record
endpoint
https://api.paxie.fun/mcp
protocol
streamable-http ·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 paxie-launch-data live?
Yes — it answered the hub's last check (checked 32m ago). It answered 100% of checks over the last 30 days.
Is paxie-launch-data free to use?
Yes — the hub reached it with no key and no payment.
What tools does paxie-launch-data have?
9 tools: sample, rh_bursts_live, rh_bursts_history, rh_pools_new, rh_pool_flow, sol_bursts_live, sol_bursts_history, launch_snapshot, ….
Is paxie-launch-data 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
100%

90 days 100%· all time 100%

latency
335ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 9 tools
1 open 8 never probed 1 of 9 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.

  • status open 32m ago

    Free: data freshness, payment networks and the price list.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • sample unknown never probed

    Free 15-minute-delayed preview: 3 bursts per chain plus 3 Robinhood pools. No payment.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • rh_bursts_live unknown never probed

    Robinhood Chain buyer bursts from the last 1-240 minutes: net ETH inflow, buy/sell swaps, scripted vs spread buying, pool age, and 30-minute outcomes once scored. Every Uniswap v4 and v3 pool on the chain is watched. Costs $0.01 USDC per call (x402).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "tier": {
      "enum": [
        "main",
        "lite",
        "refire",
        "old",
        "all"
      ],
      "type": "string",
      "description": "Burst tier (default main for live, all for history)"
    },
    "minutes": {
      "type": "number",
      "maximum": 240,
      "minimum": 1,
      "description": "Look-back window in minutes, 1-240 (default 60)"
    }
  },
  "additionalProperties": false
}
    arguments 24 lines
  • rh_bursts_history unknown never probed

    Scored Robinhood Chain bursts from the last 1-24 hours, each with its 30-minute outcome: return at 30 min, peak return and the return under each exit rule, 2% round-trip costs included. Costs $0.02 USDC per call (x402).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "tier": {
      "enum": [
        "main",
        "lite",
        "refire",
        "old",
        "all"
      ],
      "type": "string",
      "description": "Burst tier (default main for live, all for history)"
    },
    "hours": {
      "type": "number",
      "maximum": 24,
      "minimum": 1,
      "description": "Look-back window in hours, 1-24 (default 24)"
    }
  },
  "additionalProperties": false
}
    arguments 24 lines
  • rh_pools_new unknown never probed

    ETH-quoted Uniswap v4 and v3 pools opened on Robinhood Chain in the last 1-24 hours: token, age, last price, ETH liquidity and 60-minute net flow. Costs $0.005 USDC per call (x402).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "hours": {
      "type": "number",
      "maximum": 24,
      "minimum": 1,
      "description": "Look-back window in hours, 1-24 (default 6)"
    },
    "limit": {
      "type": "number",
      "maximum": 1000,
      "minimum": 1,
      "description": "Max rows (default 200)"
    }
  },
  "additionalProperties": false
}
    arguments 19 lines
  • rh_pool_flow unknown never probed

    One Robinhood Chain Uniswap v4 pool: 1-minute buckets for the last 60 minutes (net ETH, buy ETH, sell ETH, buy and sell swap counts) plus its burst history. Costs $0.005 USDC per call (x402).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Uniswap v4 pool id (bytes32 hex) from rh_pools_new"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • sol_bursts_live unknown never probed

    Solana pump.fun bonding-curve buyer bursts from the last 1-240 minutes: SOL inflow, where on the curve, token age, burst anatomy (same-slot bundles, scripted sizes, top-3 share, top-10 holders) and the scored outcome: graduated or not, peak and rule returns. Costs $0.01 USDC per call (x402).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "minutes": {
      "type": "number",
      "maximum": 240,
      "minimum": 1,
      "description": "Look-back window in minutes, 1-240 (default 60)"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • sol_bursts_history unknown never probed

    Scored Solana pump.fun curve bursts from the last 1-24 hours: which graduated, how fast, peak return, and the return under each abandon-ship exit rule, costs included. Costs $0.02 USDC per call (x402).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "hours": {
      "type": "number",
      "maximum": 24,
      "minimum": 1,
      "description": "Look-back window in hours, 1-24 (default 24)"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • launch_snapshot unknown never probed

    Everything in one call: live buyer bursts on Robinhood Chain and Solana pump.fun (last 1-240 minutes), Robinhood pools opened in the last hour, and 24h tallies (bursts, scored, median 30-min return, graduations). Costs $0.03 USDC per call (x402).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "minutes": {
      "type": "number",
      "maximum": 240,
      "minimum": 1,
      "description": "Look-back window in minutes, 1-240 (default 60)"
    }
  },
  "additionalProperties": false
}
    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 972617e9ece626ae.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/972617e9ece626ae/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/972617e9ece626ae/badge.svg)](https://brick.blue/agent/972617e9ece626ae?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.