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

anchorpad

https://anchorpad.fun

Registry code: 9e6167142db86672

api record

AnchorPad (Solana) launches coins paired with SOL, USDC, crypto such as BTC, ETH, ZEC, TAO or NEAR, or tokenized stocks. At the normal 1% trading fee, the creator wallet earns 0.4% of traded volume in the pair asset; during Sniper Shield the same fee split applies to the higher fee.

You never hold keys and nothing is spent through you. The prepare tools return a sign link: always give that link to the user, who opens it, connects their own Solana wallet (it becomes the coin's creator) and approves. Afterwards anchorpad_request_status with the request id tells you the result.

endpoint
https://anchorpad.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 anchorpad live?
Partly — its last checks failed now and then (checked 2h ago). It answered 99% of checks over the last 30 days.
Is anchorpad free to use?
Yes — the hub reached it with no key and no payment.
What tools does anchorpad have?
6 tools: anchorpad_prepare_launch, anchorpad_prepare_claim, anchorpad_prepare_trade, anchorpad_request_status, anchorpad_my_coins, anchorpad_pairs.
Is anchorpad 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
degraded
uptime, 30 days
98.7%

90 days 98%· all time 98%

latency
283ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 358 checks · signed record
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
_ what it is for
used for
  • launch a solana coin
  • prepare a bonding curve trade
  • claim creator earnings
  • list a wallet's launched coins
takes → gives
text → data, text
tools
3 reads3 changes data
_ 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 6 tools
1 open 5 never probed 1 of 6 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.

  • anchorpad_pairs reads open 42d ago

    List the assets an AnchorPad coin can be paired with: SOL, stablecoins, crypto (BTC, ETH, ZEC, TAO, NEAR, ...), Solana tokens, memes and tokenized stocks. launchBuy says whether a first buy can be included in the launch; tradeHere whether AnchorPad trades it directly.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • anchorpad_prepare_launch changes data unknown never probed

    Prepare a new Solana coin on AnchorPad, paired with an asset from anchorpad_pairs. Returns a sign link for the user; nothing happens until they approve it in their wallet. The approving wallet becomes the creator and earns 0.4% of traded volume in the pair asset at the normal 1% fee; the same fee split applies during Sniper Shield. The user pays about 0.027 SOL network rent plus any first buy. Give an image as an https URL (PNG, JPEG, GIF or WebP, up to 1 MB) if you have one; otherwise the approval page asks the user for it.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name",
        "symbol"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Coin name, 1-32 bytes"
        },
        "pair": {
          "type": "string",
          "description": "Pair symbol from anchorpad_pairs, e.g. SOL, USDC, ZEC. Default SOL"
        },
        "image": {
          "type": "string",
          "description": "Optional https URL (or data:image/... URL) of the coin image, up to 1 MB"
        },
        "symbol": {
          "type": "string",
          "description": "Ticker, 1-10 letters or digits"
        },
        "twitter": {
          "type": "string",
          "description": "Optional https://x.com/... link"
        },
        "website": {
          "type": "string",
          "description": "Optional https link"
        },
        "telegram": {
          "type": "string",
          "description": "Optional https://t.me/... link"
        },
        "first_buy": {
          "type": "string",
          "description": "Optional amount of the pair asset to buy in the launch transaction, e.g. \"0.1\". Default 0"
        },
        "description": {
          "type": "string",
          "description": "Optional, up to 500 characters"
        },
        "sniper_shield": {
          "type": "boolean",
          "description": "Trading fee starts at 50% and falls to 1% over the first two minutes, on buys and sells; the bundled first buy uses the minimum fee. Default true"
        }
      }
    }
    arguments 49 lines
  • anchorpad_prepare_claim changes data unknown never probed

    Prepare a claim of the creator earnings on every coin of the wallet that approves (with an agent key: the agent's wallet). Returns a sign link for the user; nothing happens until they approve it in their wallet. Costs only the network fee. See anchorpad_my_coins first for what is unclaimed.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • anchorpad_prepare_trade changes data unknown never probed

    Prepare a buy or sell of an AnchorPad coin on its bonding curve. Returns a sign link for the user; nothing happens until they approve it in their wallet. amount is in the pair asset for a buy (e.g. 0.1 SOL) and in coins for a sell. The approval page shows the live price and a 3% slippage limit before the user signs.

    mcp-tool

    {
      "type": "object",
      "required": [
        "mint",
        "side",
        "amount"
      ],
      "properties": {
        "mint": {
          "type": "string",
          "description": "The coin's mint address"
        },
        "side": {
          "enum": [
            "buy",
            "sell"
          ],
          "type": "string",
          "description": "buy or sell"
        },
        "amount": {
          "type": "string",
          "description": "Amount as a plain number, e.g. \"0.1\""
        }
      }
    }
    arguments 26 lines
  • anchorpad_request_status reads unknown 42d ago

    Whether a prepared request was approved: open (waiting for the user), done (with the coin or transaction signatures) or expired (links last 24 hours). Without id (agent key only), lists the agent's last 10 requests.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "id": {
          "type": "string",
          "description": "Request id returned by a prepare tool"
        }
      }
    }
    arguments 9 lines
  • anchorpad_my_coins reads unknown 42d ago

    A wallet's coins on AnchorPad, their links and unclaimed creator earnings.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "wallet": {
          "type": "string",
          "description": "The user's Solana wallet address. Not needed with an agent key (the agent's wallet is used)"
        }
      }
    }
    arguments 9 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 9e6167142db86672.

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