# bot.yeehaw/events (remote · yeehaw.bot)

Agent-first Austin events concierge — fresh, sourced answers to what's happening in Austin.

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

## Components

- remote · `yeehaw.bot`: 62/100 (this document), [markdown](https://verifymcp.io/servers/bot-yeehaw-events/yeehaw.md), [page](https://verifymcp.io/servers/bot-yeehaw-events/yeehaw)

## Channel facts

- Endpoint: `https://yeehaw.bot/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## 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 2 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 358 tokens (~179/item across 2 items; 2 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**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http bot-yeehaw-events https://yeehaw.bot/mcp
```

### Codex

```toml
[mcp_servers.bot-yeehaw-events]
url = "https://yeehaw.bot/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add bot-yeehaw-events --url https://yeehaw.bot/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  bot-yeehaw-events:
    url: "https://yeehaw.bot/mcp"
```

### Other

```json
{
  "mcpServers": {
    "bot-yeehaw-events": {
      "type": "http",
      "url": "https://yeehaw.bot/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 62, +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 61, −1)

- [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 (2)

### `find_events` (~307 tokens)

Find upcoming Austin events from Yeehaw's sourced, deduplicated store. Structured filter over the events table; events more than 24h past are filtered. Every record carries a `source` attribution and a `confidence` score. Pass `id` to fetch one event by id; it ignores date_range and all other filters.

Input parameters:

- `category` (string): Category slug (e.g. music, sports, civic).
- `date_range` (string): Required unless `id` is set. e.g. today, tonight, this_weekend, next_7_days, or an ISO date range.
- `id` (string): Fetch one event by id; ignores date_range and other filters when set.
- `limit` (integer): Max results, default 20, clamped to 50.
- `neighborhood` (string): Austin neighborhood slug. One of: downtown, east-austin, hyde-park, mueller, rainey-street, south-congress, the-domain, zilker. Common shorthands (east, domain, soco, rainey) are accepted.
- `price_max` (number): Maximum ticket price in USD. price_max=0 returns only events with a known $0 price. Most events have no listed price (sparse upstream data) — for price_max>0 those are still returned and the response…
- `query` (string): Free-text keyword match against event titles.

### `overview` (~51 tokens)

Inspectable State: report Yeehaw's operational state in one call (no input) — event counts, last successful ingest per source vs cadence, cron health, open circuit breakers, recent error tail, and coverage gaps.

## Diagnostics

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

## Score history

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

## Links

- Remote endpoint: https://yeehaw.bot/mcp
- Repository: https://github.com/capitalthought/yeehaw-mcp
- Website: https://yeehaw.bot/
- Changelog RSS feed: https://verifymcp.io/servers/bot-yeehaw-events/yeehaw/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/bot-yeehaw-events/yeehaw/changelog.json
- HTML version of this page: https://verifymcp.io/servers/bot-yeehaw-events/yeehaw