Skip to content

live.catchaset/catchaset

by catchaset.live · remote · no sign-in to list tools · v1.0.0 · published by live.catchaset

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

Changes · 1
CompareRegistry entry

3 tools: 1 change things and 2 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http catchaset https://catchaset.live/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

3 tools

Changes things 1Claude Code: ask
  • overviewOperational state of the CatchaSet event feed: per-city event counts, data sources, last-refresh time, staleness, and coverage.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
Only reads 2Claude Code: allow
  • find_eventsFind upcoming live-music events in a supported city (Austin or Chicago), filtered by free-text query, date range, and/or genre.No findings

    Why it is in this group

    • The name "find_events" says "find": a word for reading.
    Description, as the server wrote it
    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_showsGiven 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 soon…No findings

    Why it is in this group

    • The name "find_live_shows" says "find": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http catchaset https://catchaset.live/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__catchaset__find_events",
      "mcp__catchaset__find_live_shows"
    ],
    "ask": [
      "mcp__catchaset__overview"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as catchaset. Review it before you use it.