Remote MCP · Endpoint

AnchorPad MCP server

No. AnchorPad answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://anchorpad.fun/mcp

The last check completed an MCP handshake.

Registry name
fun.anchorpad/anchorpad
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
152 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Launch Solana coins from your AI. You approve each launch in your wallet and earn creator fees.
Listing
From the official MCP registry (active).
Recent checks of AnchorPad
CheckedResultHandshake
2 hours agoHandshake completed152 ms
1 day agoHandshake completed268 ms
4 days agoHandshake completed242 ms
6 days agoHandshake completed232 ms
8 days agoHandshake completed122 ms
9 days agoHandshake completed249 ms
11 days agoHandshake completed143 ms
12 days agoHandshake completed412 ms
13 days agoHandshake completed168 ms
16 days agoHandshake completed135 ms
17 days agoHandshake completed274 ms
19 days agoHandshake completed210 ms
20 days agoHandshake completed287 ms
21 days agoHandshake completed141 ms
22 days agoHandshake completed193 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with AnchorPad and makes no claim about it beyond what these checks measured.