# live.catchaset/catchaset (remote · catchaset.live)

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

- Trust score: 60/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `catchaset.live`: 60/100 (this document), [markdown](https://verifymcp.io/servers/live-catchaset-catchaset/catchaset.md), [page](https://verifymcp.io/servers/live-catchaset-catchaset/catchaset)

## Channel facts

- Endpoint: `https://catchaset.live/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 567 tokens (~189/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```toml
[mcp_servers.live-catchaset-catchaset]
url = "https://catchaset.live/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "live-catchaset-catchaset": {
      "type": "remote",
      "url": "https://catchaset.live/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add live-catchaset-catchaset --url https://catchaset.live/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  live-catchaset-catchaset:
    url: "https://catchaset.live/mcp"
```

### Other

```json
{
  "mcpServers": {
    "live-catchaset-catchaset": {
      "type": "http",
      "url": "https://catchaset.live/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 59, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 60, −2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 60, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 60)

First indexed and scored.

## MCP tools (3)

### `find_events` (~223 tokens)

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.

Input parameters:

- `city` (string): City to search. Only Austin and Chicago are supported; any other value returns an unsupported_city note and defaults to Austin.
- `cursor` (string): Opaque pagination cursor from a previous response's next_cursor.
- `date_from` (string): Optional inclusive lower bound, ISO date YYYY-MM-DD.
- `date_to` (string): Optional inclusive upper bound, ISO date YYYY-MM-DD.
- `genre` (string): Optional genre substring filter.
- `limit` (integer): Max events to return (1-100).
- `query` (string): Optional free-text filter matched (case-insensitive substring) against headliner, artists, venue, and genre.

### `find_live_shows` (~224 tokens)

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.

Input parameters:

- `artists` (array, required): Names of acts the user likes. Required — this is the taste to match.
- `city` (string): City to search. Only Austin and Chicago are supported; other values default to Austin with an unsupported_city note.
- `cursor` (string): Opaque pagination cursor from a previous response's next_cursor.
- `date_from` (string): Optional inclusive lower bound, ISO date YYYY-MM-DD.
- `date_to` (string): Optional inclusive upper bound, ISO date YYYY-MM-DD.
- `limit` (integer): Max shows to return (1-100).

### `overview` (~52 tokens)

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/live-catchaset-catchaset/catchaset#diagnostics

## Score history

- 2026-08-03: 60
- 2026-08-02: 59
- 2026-08-01: 59
- 2026-07-31: 59
- 2026-07-30: 60
- 2026-07-29: 62
- 2026-07-28: 61
- 2026-07-27: 60
- 2026-07-26: 60

## Links

- Remote endpoint: https://catchaset.live/mcp
- Changelog RSS feed: https://verifymcp.io/servers/live-catchaset-catchaset/catchaset/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/live-catchaset-catchaset/catchaset/changelog.json
- HTML version of this page: https://verifymcp.io/servers/live-catchaset-catchaset/catchaset