Remote MCP · Endpoint

MemePump Token Safety MCP server

No. MemePump Token Safety answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://memepump.org/api/mcp

The last check completed an MCP handshake.

Registry name
org.memepump/memepump
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
222 ms
Tools exposed
3 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
Read-only Solana token safety checks: risk score, honeypot, liquidity lock, authorities, holders.
Listing
From the official MCP registry (active).
Recent checks of MemePump Token Safety
CheckedResultHandshake
1 hour agoHandshake completed222 ms
4 days agoHandshake completed239 ms
7 days agoHandshake completed213 ms

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

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