Remote MCP · Endpoint

Community Board MCP server

No. Community Board answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.shavitnetzer.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.sha-net/community-board
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
274 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search and discover local community listings, classifieds, services and events.
Listing
From the official MCP registry (active).
Recent checks of Community Board
CheckedResultHandshake
1 hour agoHandshake completed274 ms
2 days agoHandshake completed270 ms
4 days agoHandshake completed268 ms
6 days agoHandshake completed266 ms
8 days agoHandshake completed264 ms
10 days agoHandshake completed265 ms
12 days agoHandshake completed315 ms
14 days agoHandshake completed272 ms
15 days agoHandshake completed270 ms
16 days agoHandshake completed300 ms
18 days agoHandshake completed269 ms
20 days agoHandshake completed275 ms
22 days agoHandshake completed274 ms
24 days agoHandshake completed263 ms

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

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