live.catchaset/catchaset
REMOTE · CATCHASET.LIVE · SCANNED AUG 3
Live-music shows in Austin & Chicago matched to your taste (pass artists you like).
Available components
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. How we score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · catchaset.live
claude mcp add --transport http live-catchaset-catchaset https://catchaset.live/mcp
[mcp_servers.live-catchaset-catchaset] url = "https://catchaset.live/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"live-catchaset-catchaset": {
"type": "remote",
"url": "https://catchaset.live/mcp",
"enabled": true
}
}
} openclaw mcp add live-catchaset-catchaset --url https://catchaset.live/mcp --transport streamable-http
mcp_servers:
live-catchaset-catchaset:
url: "https://catchaset.live/mcp" {
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +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.
- 31 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +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.
- 28 Jul 26 +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.
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 60
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://catchaset.live/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=catchaset.live | CN=WE1,O=Google Trust Services,C=US | 18 Jun 2026 | 16 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | ddcba795a900208e0eae479610464cc0 |
| SANs: catchaset.live, *.catchaset.live | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of catchaset.live. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| live. | present | 36322 | 8 | Verified |
| catchaset.live. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://catchaset.live/mcp | Verified | 200 | |
| http (plaintext) | http://catchaset.live/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
find_events ~223
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
find_live_shows ~224
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.
| Name | Type | Req | Description |
|---|---|---|---|
| artists | array | yes | 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). |
No output schema declared.
No examples provided.
overview ~52
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.