Remote MCP · Endpoint

MemeSwap MCP MCP server

No. MemeSwap MCP answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.memeswap.fun/mcp

The last check completed an MCP handshake.

Registry name
fun.memeswap/trading
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
156 ms
Tools exposed
43 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Buy & research hot/new memes. Quotes + unsigned swaps; wallet signs. Not a launcher. Fee 0.85%. NFA.
Listing
From the official MCP registry (active).
Recent checks of MemeSwap MCP
CheckedResultHandshake
1 hour agoHandshake completed156 ms
2 days agoHandshake completed167 ms
5 days agoHandshake completed186 ms
7 days agoHandshake completed165 ms
9 days agoHandshake completed135 ms
11 days agoHandshake completed320 ms
13 days agoHandshake completed137 ms
15 days agoHandshake completed132 ms
17 days agoHandshake completed148 ms
18 days agoHandshake completed137 ms
19 days agoHandshake completed622 ms
20 days agoHandshake completed169 ms
23 days agoHandshake completed128 ms
24 days agoHandshake completed230 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 MemeSwap MCP and makes no claim about it beyond what these checks measured.