AnchorPad MCP server
fun.anchorpad/anchorpadanchorpad.funstreamable-httpv1.0.0Scanned
Launch Solana coins from your AI. You approve each launch in your wallet and earn creator fees.
6 tools: 5 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
5 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the AnchorPad MCP server can do
The AnchorPad MCP server is published by anchorpad.fun, a domain the MCP Registry verified. It has 6 tools. It can create or change data (5 tools: anchorpad_prepare_launch, anchorpad_prepare_claim, anchorpad_prepare_trade, anchorpad_request_status and 1 more), but cannot delete data. 1 tool only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 15, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Changes things 5Claude Code: ask
anchorpad_my_coinsA wallet's coins on AnchorPad, their links and unclaimed creator earnings.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it A wallet's coins on AnchorPad, their links and unclaimed creator earnings.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
anchorpad_prepare_claimPrepare a claim of the creator earnings on every coin of the wallet that approves (with an agent key: the agent's wallet).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
anchorpad_prepare_launchPrepare a new Solana coin on AnchorPad, paired with an asset from anchorpad_pairs.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
anchorpad_prepare_tradePrepare a buy or sell of an AnchorPad coin on its bonding curve.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
anchorpad_request_statusWhether a prepared request was approved: open (waiting for the user), done (with the coin or transaction signatures) or expired (links last 24 hours).1 finding
Why it is in this group
- The name "anchorpad_request_status" says "request": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "anchorpad_request_status" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "anchorpad_request_status" says "request": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
Only reads 1Show 1 read-only tool
anchorpad_pairsList the assets an AnchorPad coin can be paired with: SOL, stablecoins, crypto (BTC, ETH, ZEC, TAO, NEAR, ...), Solana tokens, memes and tokenized stocks.No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:54 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 5
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://anchorpad.fun/mcp: tools/list returned 6 tools to an anonymous client, including anchorpad_prepare_launch (write), anchorpad_prepare_claim (write), anchorpad_prepare_trade (write), anchorpad_request_status (write), anchorpad_my_coins (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "anchorpad_request_status" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "anchorpad_request_status" says "request": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http anchorpad https://anchorpad.fun/mcpclaude mcp add --transport http anchorpad https://anchorpad.fun/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__anchorpad__anchorpad_pairs"
],
"ask": [
"mcp__anchorpad__anchorpad_prepare_launch",
"mcp__anchorpad__anchorpad_prepare_claim",
"mcp__anchorpad__anchorpad_prepare_trade",
"mcp__anchorpad__anchorpad_request_status",
"mcp__anchorpad__anchorpad_my_coins"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as anchorpad. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/fun.anchorpad/anchorpad/verify?hash=440120ebf40678b73ba5d7877d3220514dd1a7ffbc092ddcf1e7207c2465278f" | jq -e '.changed == false'Pinned hash 440120ebf406, from Nov 15, 2026, 10:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/fun.anchorpad/anchorpad/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/fun.anchorpad/anchorpad)Source: MCP Registry. Synced Oct 21, 2026, 18:12 UTC.
AnchorPad MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the AnchorPad MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 5 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the AnchorPad MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the AnchorPad MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the AnchorPad MCP server have?
- 6 tools: 5 write, 1 read. anchorpad_prepare_launch, anchorpad_prepare_claim, anchorpad_prepare_trade, anchorpad_request_status, anchorpad_my_coins and anchorpad_pairs.
Does the AnchorPad MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the AnchorPad MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the AnchorPad MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.