_ registry / mcp streamable-http · checked 48m 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. The creator wallet earns 0.4% of every trade, paid in the pair asset.

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
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
202ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ 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 open 48m 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_my_coins unknown 48m 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
  • anchorpad_prepare_launch 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 every trade in the pair asset. 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": "Higher fee for bots in the first minute (15% falling to 1%). Default true"
    }
  }
}
    arguments 49 lines
  • anchorpad_prepare_claim 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 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 unknown 48m 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
_ 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.

_ 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)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ 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.