Remote MCP · Endpoint

Moonlauncher MCP server

No. Moonlauncher answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://moonlauncher.app/mcp

The last check completed an MCP handshake.

Registry name
app.moonlauncher/moonlauncher
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
427 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Prepare pump.fun token launches from your AI agent. You review and sign each one in your own wallet.
Listing
From the official MCP registry (active).
Recent checks of Moonlauncher
CheckedResultHandshake
1 hour agoHandshake completed427 ms
7 hours agoHandshake completed440 ms
2 days agoHandshake completed467 ms
4 days agoHandshake completed744 ms
6 days agoHandshake completed377 ms
9 days agoHandshake completed791 ms
11 days agoHandshake completed72 ms
13 days agoHandshake completed873 ms
15 days agoHandshake completed495 ms
17 days agoHandshake completed428 ms
19 days agoHandshake completed50 ms
21 days agoHandshake completed49 ms
23 days agoHandshake completed589 ms
24 days agoHandshake completed424 ms

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

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 Moonlauncher and makes no claim about it beyond what these checks measured.