Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AnchorPad

REMOTE · ANCHORPAD.FUN · SCANNED OCT 7

Launch Solana coins from your AI. You approve each launch in your wallet and earn creator fees.

Available components

+3 this week 76 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability75
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 946 tokens (~157/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the AnchorPad MCP server?

AnchorPad is a hosted endpoint at https://anchorpad.fun/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · anchorpad.fun

# add to Claude Code
claude mcp add --transport http fun-anchorpad-anchorpad 'https://anchorpad.fun/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "fun-anchorpad-anchorpad": {
      "url": "https://anchorpad.fun/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "fun-anchorpad-anchorpad": {
      "type": "http",
      "url": "https://anchorpad.fun/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.fun-anchorpad-anchorpad]
url = "https://anchorpad.fun/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fun-anchorpad-anchorpad": {
      "type": "remote",
      "url": "https://anchorpad.fun/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add fun-anchorpad-anchorpad --url 'https://anchorpad.fun/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  fun-anchorpad-anchorpad:
    url: "https://anchorpad.fun/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "fun-anchorpad-anchorpad": {
      "Transport": "http",
      "Url": "https://anchorpad.fun/mcp"
    }
  }
}
# add to Vellum
assistant mcp add fun-anchorpad-anchorpad -t streamable-http -u 'https://anchorpad.fun/mcp'
// mcp.json
{
  "mcpServers": {
    "fun-anchorpad-anchorpad": {
      "type": "http",
      "url": "https://anchorpad.fun/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 7 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 37. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “anchorpad_prepare_launch” rewrote its description, which is the text the model reads security
    • “anchorpad_prepare_launch” reworded the description of “sniper_shield” cosmetic
  • 1 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Sept 26 +7
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 26 Sept 26 65

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 8 Oct 2026 · Probed https://anchorpad.fun/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=anchorpad.fun CN=WE1,O=Google Trust Services,C=US 24 Sept 2026 23 Dec 2026 ECDSA 256 ECDSA-SHA256 8cd8ab8d9dae3f313dfe64c09aabef6
SANs: anchorpad.fun
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of anchorpad.fun. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
fun. present 47728 13 Verified
anchorpad.fun. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://anchorpad.fun/mcp Verified 200
http (plaintext) http://anchorpad.fun/mcp HTTPS enforced 301 https://anchorpad.fun/mcp
MCP tools · 6 exposed · ~759 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
anchorpad_my_coins ~54

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

NameTypeReqDescription
walletstring–The user's Solana wallet address. Not needed with an agent key (the agent's wallet is used)

No output schema declared.

No examples provided.

anchorpad_pairs ~76

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

anchorpad_prepare_claim ~73

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

anchorpad_prepare_launch ~353

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.

NameTypeReqDescription
descriptionstring–Optional, up to 500 characters
first_buystring–Optional amount of the pair asset to buy in the launch transaction, e.g. "0.1". Default 0
imagestring–Optional https URL (or data:image/... URL) of the coin image, up to 1 MB
namestringyesCoin name, 1-32 bytes
pairstring–Pair symbol from anchorpad_pairs, e.g. SOL, USDC, ZEC. Default SOL
sniper_shieldboolean–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
symbolstringyesTicker, 1-10 letters or digits
telegramstring–Optional https://t.me/... link
twitterstring–Optional https://x.com/... link
websitestring–Optional https link

No output schema declared.

No examples provided.

anchorpad_prepare_trade ~131

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.

NameTypeReqDescription
amountstringyesAmount as a plain number, e.g. "0.1"
mintstringyesThe coin's mint address
sidestringyesbuy or sell

No output schema declared.

No examples provided.

anchorpad_request_status ~72

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.

NameTypeReqDescription
idstring–Request id returned by a prepare tool

No output schema declared.

No examples provided.

Common questions

What is the AnchorPad MCP server?

AnchorPad is an MCP server listed in the public MCP registry as fun.anchorpad/anchorpad. Launch Solana coins from your AI. You approve each launch in your wallet and earn creator fees. This page covers its hosted endpoint (https://anchorpad.fun/mcp).

Is the AnchorPad MCP server safe to use?

AnchorPad scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the AnchorPad MCP server expose?

AnchorPad exposes 6 tools: anchorpad_pairs, anchorpad_prepare_launch, anchorpad_prepare_claim, anchorpad_prepare_trade, anchorpad_request_status, anchorpad_my_coins. Their descriptions and schemas cost roughly 759 tokens of context every time the server is loaded.

Does the AnchorPad MCP server require authentication?

No. We connected to AnchorPad without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AnchorPad MCP server still maintained?

AnchorPad is still listed as active in the MCP registry. We last reached this channel on 5 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.