Remote MCP · Endpoint

LONG Events MCP server

No. LONG Events answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://long.events/functions/v1/mcp-server/mcp

The last check completed an MCP handshake.

Registry name
events.long/long-events
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
285 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search events, conference weeks, cities, venues and artist schedules via remote MCP.
Listing
From the official MCP registry (active).
Recent checks of LONG Events
CheckedResultHandshake
43 minutes agoHandshake completed285 ms
8 days agoHandshake completed215 ms
9 days agoHandshake completed39 ms
11 days agoHandshake completed216 ms
12 days agoHandshake completed235 ms
13 days agoHandshake completed198 ms
14 days agoHandshake completed219 ms
14 days agoHandshake completed283 ms
16 days agoHandshake completed37 ms
19 days agoHandshake completed201 ms
21 days agoHandshake completed50 ms
24 days agoHandshake completed381 ms
26 days agoHandshake completed290 ms
28 days agoHandshake completed212 ms

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

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.