Remote MCP · Endpoint

lesgooo.fun MCP server

No. lesgooo.fun answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://lesgooo.fun/mcp

The last check completed an MCP handshake.

Registry name
fun.lesgooo/lesgooo
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
111 ms
Tools exposed
23 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Free no-signup group planner: dates, RSVPs, place votes, shared checklist and split costs.
Listing
From the official MCP registry (active).
Recent checks of lesgooo.fun
CheckedResultHandshake
1 hour agoHandshake completed111 ms
8 days agoHandshake completed117 ms
9 days agoHandshake completed95 ms
11 days agoHandshake completed104 ms
12 days agoHandshake completed104 ms
12 days agoHandshake completed115 ms
14 days agoHandshake completed154 ms
14 days agoHandshake completed112 ms
16 days agoHandshake completed129 ms
19 days agoHandshake completed146 ms
21 days agoHandshake completed139 ms
24 days agoHandshake completed119 ms
26 days agoHandshake completed126 ms
28 days agoHandshake completed117 ms

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

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