mcpbeat

Catchaset MCP Server

live.catchaset/catchaset
answering

Catchaset is answering right now. Last checked 11 min ago. It exposes 3 tools.

Live-music shows in Austin & Chicago matched to your taste (pass artists you like).

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
3
Tools
read from the server
96 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add catchaset --transport http https://catchaset.live/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "catchaset": {
      "url": "https://catchaset.live/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.catchaset]
url = "https://catchaset.live/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "catchaset": {
      "url": "https://catchaset.live/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "catchaset": {
      "url": "https://catchaset.live/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

events
find_events
Find upcoming live-music events in a supported city (Austin or Chicago), filtered by free-text query, date range, and/or genre. Returns taste-neutral event records with source attribution, ticket links, and a freshness timestamp — the same public data catchaset.live shows signed-out visitors. Does NOT rank by personal taste. Results are capped per call; page with the returned next_cursor.
live
find_live_shows
Given a list of artists the user likes, find upcoming shows in a supported city (Austin or Chicago) where one of those artists is on the bill, ranked (most matches first, then soonest). Taste is a PARAMETER — no account or login needed. Each result includes why_matched (which of the user's artists plays). This is direct-artist matching; genre-based discovery of *similar* artists is available in the CatchaSet web app, not here.
overview
overview
Operational state of the CatchaSet event feed: per-city event counts, data sources, last-refresh time, staleness, and coverage. No input. Call this to check health/coverage before relying on find_events.

Endpoints

URLTransportStateLatencyChecked
https://catchaset.live/mcp streamable-http answering 98 ms 11 min ago

Catchaset — questions

Answers built from our own checks of this server.

What can Catchaset do?
It exposes 3 tools, read directly from the server on our last check. Among them: find_events, find_live_shows, overview. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Catchaset working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 96 ms. The bar chart above shows every period we have measured.
How do I connect Catchaset?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Catchaset need an API key?
No. Catchaset completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Catchaset?
It answers our handshake in 96 ms on average, which is faster than 85% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.