Remote MCP · Endpoint

live.catchaset/catchaset MCP server

No. live.catchaset/catchaset answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://catchaset.live/mcp

The last check completed an MCP handshake.

Registry name
live.catchaset/catchaset
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
189 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
Live-music shows in Austin & Chicago matched to your taste (pass artists you like).
Listing
From the official MCP registry (active).
Recent checks of live.catchaset/catchaset
CheckedResultHandshake
1 hour agoHandshake completed189 ms
19 hours agoHandshake completed48 ms
2 days agoHandshake completed55 ms
3 days agoHandshake completed61 ms
4 days agoHandshake completed88 ms
5 days agoHandshake completed46 ms
6 days agoHandshake completed50 ms
8 days agoHandshake completed475 ms
10 days agoHandshake completed53 ms
13 days agoHandshake completed56 ms
15 days agoHandshake completed93 ms
18 days agoHandshake completed79 ms
19 days agoHandshake completed79 ms
22 days agoHandshake completed74 ms
24 days agoHandshake completed167 ms
25 days agoHandshake completed41 ms
27 days agoHandshake completed39 ms
29 days agoHandshake completed86 ms
29 days agoHandshake completed59 ms

The last 19 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 live.catchaset/catchaset and makes no claim about it beyond what these checks measured.