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

preape

https://preape.ai

Registry code: 02e6331b3e74a4cc

api record

Use PreApe before buying a RadarDEX token on Arc. Call preape_check first. If CAUTION or you need holders, call preape_analyze ($0.03 USDC on Base via x402). Verdicts: GO, CAUTION, AVOID. Missing data is null.

endpoint
https://preape.ai/mcp
protocol
streamable-http ·2025-03-26
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 preape live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is preape free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does preape have?
2 tools: preape_analyze, preape_check.
Is preape 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 99.2%· all time 99.2%

latency
273ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 396 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
crypto & onchain trading & defi
used for
  • check a token's risk before buying
  • get a full pre-trade token analysis
takes → gives
text → data
tools
2 reads
_ 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 2 tools
1 auth-required 1 never probed 1 of 2 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.

  • preape_check reads auth-required 9h ago

    Quick pre-trade risk check for a token on Arc / RadarDEX before buying. Returns GO, CAUTION, AVOID plus one-liner and red flags. Covers observed RadarDEX creator history and LP lock. Does not scan full holders. Use this first.

    mcp-tool

    {
  "type": "object",
  "required": [
    "token"
  ],
  "properties": {
    "token": {
      "type": "string",
      "description": "ERC-20 token address on Arc (0x…)"
    }
  }
}
    arguments 12 lines
  • preape_analyze reads unknown never probed

    Full pre-trade analysis for an Arc / RadarDEX token before buying. Returns GO / CAUTION / AVOID with creator observed launch history, LP lock, liquidity snapshot, and top-holder concentration. Volume and wash fields are null in v1. RadarDEX-only coverage.

    mcp-tool

    {
  "type": "object",
  "required": [
    "token"
  ],
  "properties": {
    "token": {
      "type": "string",
      "description": "ERC-20 token address on Arc (0x…)"
    },
    "includeHolders": {
      "type": "boolean",
      "description": "Include Arcscan holder concentration. Default true."
    },
    "include_holders": {
      "type": "boolean",
      "description": "Alias of includeHolders."
    }
  }
}
    arguments 20 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 02e6331b3e74a4cc.

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

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.

_ also on preape.ai 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.