Remote MCP · Endpoint

Buffet MCP server

No. Buffet answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes ago

Server URL

https://mcp.joinbuffet.com/mcp

The last check completed an MCP handshake.

Registry name
com.joinbuffet/buffet
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
321 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Buffet's weekly lineup of real-life events and hangouts in Los Angeles. Read-only, no sign-in.
Listing
From the official MCP registry (active).
Recent checks of Buffet
CheckedResultHandshake
44 minutes agoHandshake completed321 ms
3 days agoHandshake completed314 ms
12 days agoHandshake completed139 ms
13 days agoHandshake completed102 ms
14 days agoHandshake completed81 ms
15 days agoHandshake completed897 ms
16 days agoHandshake completed67 ms
17 days agoHandshake completed223 ms
18 days agoHandshake completed97 ms
19 days agoHandshake completed73 ms
22 days agoHandshake completed62 ms
25 days agoHandshake completed106 ms
27 days agoHandshake completed145 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 Buffet and makes no claim about it beyond what these checks measured.