Remote MCP · Endpoint

SFomo: Bay Area events MCP server

No. SFomo: Bay Area events answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://sfomo.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.sfomo/events
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
87 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Read-only search of upcoming SF Bay Area events: AI/tech, dance, music, arts, food, fitness.
Listing
From the official MCP registry (active).
Recent checks of SFomo: Bay Area events
CheckedResultHandshake
9 hours agoHandshake completed87 ms
15 hours agoHandshake completed182 ms
2 days agoHandshake completed166 ms
4 days agoHandshake completed314 ms
7 days agoHandshake completed231 ms
9 days agoHandshake completed159 ms
11 days agoHandshake completed122 ms
14 days agoHandshake completed172 ms
16 days agoHandshake completed176 ms
18 days agoHandshake completed110 ms
20 days agoHandshake completed103 ms
21 days agoHandshake completed267 ms
23 days agoHandshake completed187 ms

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

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 SFomo: Bay Area events and makes no claim about it beyond what these checks measured.