Remote MCP · Endpoint

com.stungevents/events MCP server

Yes, as of 1 hour ago: the response was not JSON-RPC.

DownLast checked 1 hour ago

Server URL

https://mcp.stungevents.com/

The last check failed: the response was not JSON-RPC.

Registry name
com.stungevents/events
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
6 tools
Uptime, last 30 days
66.7% from 18 checks
Described by its publisher as
Search live events in 60+ countries, plan a night out, and demand artists to tour your city.
Listing
From the official MCP registry (active).
Recent checks of com.stungevents/events
CheckedResultHandshake
1 hour agoFailed - the response was not JSON-RPC—
1 day agoFailed - the response was not JSON-RPC—
2 days agoFailed - the response was not JSON-RPC—
3 days agoFailed - the response was not JSON-RPC—
4 days agoFailed - the response was not JSON-RPC—
5 days agoFailed - the response was not JSON-RPC—
6 days agoHandshake completed62 ms
9 days agoHandshake completed61 ms
12 days agoHandshake completed72 ms
14 days agoHandshake completed365 ms
16 days agoHandshake completed70 ms
18 days agoHandshake completed64 ms
20 days agoHandshake completed62 ms
22 days agoHandshake completed62 ms
24 days agoHandshake completed50 ms
26 days agoHandshake completed113 ms
27 days agoHandshake completed364 ms
29 days agoHandshake completed308 ms

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

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 com.stungevents/events and makes no claim about it beyond what these checks measured.