Remote MCP · Endpoint
LONG Events MCP server
No. LONG Events answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://belong.events/functions/v1/mcp-server/mcp
The last check completed an MCP handshake.
- Registry name
- events.belong/long-events
- Transport
- Streamable HTTP
- Protocol negotiated
- 2024-11-05
- Handshake latency
- 243 ms
- Tools exposed
- 16 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Search events, conference weeks, cities, venues and artist schedules via remote MCP.
- Website
- https://belong.events/
- Listing
- From the official MCP registry (deprecated).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 243 ms |
| 2 days ago | Handshake completed | 196 ms |
| 4 days ago | Handshake completed | 262 ms |
| 5 days ago | Handshake completed | 197 ms |
| 7 days ago | Handshake completed | 52 ms |
| 8 days ago | Handshake completed | 197 ms |
| 9 days ago | Handshake completed | 204 ms |
| 12 days ago | Handshake completed | 203 ms |
| 13 days ago | Handshake completed | 267 ms |
| 15 days ago | Handshake completed | 212 ms |
| 16 days ago | Handshake completed | 194 ms |
| 18 days ago | Handshake completed | 198 ms |
| 19 days ago | Handshake completed | 193 ms |
| 20 days ago | Handshake completed | 204 ms |
| 20 days ago | Handshake completed | 40 ms |
| 21 days ago | Handshake completed | 202 ms |
| 22 days ago | Handshake completed | 272 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 LONG Events and makes no claim about it beyond what these checks measured.