mcp server
catchaset
Live-music shows in Austin & Chicago matched to your taste (pass artists you like).
Description as published by the maintainer. Source
- version 1.0.0
- active
active — Registry entry last updated 2026-07-01.
What this server can do
3 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
find_events(city, genre, limit, query, cursor, date_to, date_from)- 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.
find_live_shows(city, limit, cursor, artists, date_to, date_from)- 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. Required: artists.
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.
Last successful function declaration observed on . Source: https://catchaset.live/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://catchaset.live/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-01 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-01 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 3 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | catchaset.live | |
| mcp endpoint status | ok | The server listed 3 functions when asked. | as of probe | catchaset.live |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json