Remote MCP · Endpoint

memecub MCP server

No. memecub answered an MCP handshake 19 minutes ago.

UpLast checked 19 minutes ago

Server URL

https://memecub.com/mcp

The last check completed an MCP handshake.

Registry name
com.memecub/memecub
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
658 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Find memes and Chinese 表情包, auto-place them into articles, or draw custom memes with AI.
Listing
From the official MCP registry (active).
Recent checks of memecub
CheckedResultHandshake
19 minutes agoHandshake completed658 ms
9 days agoHandshake completed690 ms
9 days agoHandshake completed581 ms
11 days agoHandshake completed591 ms
12 days agoHandshake completed620 ms
13 days agoHandshake completed598 ms
14 days agoHandshake completed594 ms
15 days agoHandshake completed586 ms
16 days agoHandshake completed645 ms
19 days agoHandshake completed602 ms
21 days agoHandshake completed768 ms
24 days agoHandshake completed637 ms
26 days agoHandshake completed637 ms
28 days agoHandshake completed700 ms

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

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