Remote MCP · Endpoint

AnchorPad MCP server

No. AnchorPad answered an MCP handshake 16 minutes ago.

UpLast checked 16 minutes 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
676 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 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
16 minutes agoHandshake completed676 ms
8 days agoHandshake completed278 ms
9 days agoHandshake completed258 ms
11 days agoHandshake completed250 ms
12 days agoHandshake completed216 ms
13 days agoHandshake completed475 ms
14 days agoHandshake completed377 ms
14 days agoHandshake completed144 ms
16 days agoHandshake completed155 ms
19 days agoHandshake completed271 ms
21 days agoHandshake completed254 ms
24 days agoHandshake completed562 ms
26 days agoHandshake completed152 ms
28 days agoHandshake completed268 ms

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

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.