Remote MCP · Endpoint

Genesis Social MCP server

No. Genesis Social answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.genesis.social/mcp

The last check completed an MCP handshake.

Registry name
io.github.junoventures/genesis-social
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
178 ms
Tools exposed
26 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Genesis Social — directory of places, events, and listings.
Listing
From the official MCP registry (active).
Recent checks of Genesis Social
CheckedResultHandshake
1 hour agoHandshake completed178 ms
2 days agoHandshake completed61 ms
4 days agoHandshake completed71 ms
5 days agoHandshake completed174 ms
7 days agoHandshake completed113 ms
8 days agoHandshake completed74 ms
9 days agoHandshake completed86 ms
12 days agoHandshake completed78 ms
13 days agoHandshake completed80 ms
15 days agoHandshake completed71 ms
17 days agoHandshake completed90 ms
18 days agoHandshake completed72 ms
19 days agoHandshake completed110 ms
20 days agoHandshake completed89 ms
20 days agoHandshake completed96 ms
21 days agoHandshake completed86 ms
23 days agoHandshake completed85 ms

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

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