Skip to content

bot.yeehaw/events

by yeehaw.bot · remote · no sign-in to list tools · v1.0.1 · published by bot.yeehaw

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

Changes · 1
CompareRegistry entry

2 tools: 1 change things and 1 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 events https://yeehaw.bot/mcp

Tools

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

2 tools

Changes things 1Claude Code: ask
  • overviewInspectable 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…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
    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.
Only reads 1Claude Code: allow
  • find_eventsFind upcoming Austin events from Yeehaw's sourced, deduplicated store.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 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.

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.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http events https://yeehaw.bot/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__events__find_events"
    ],
    "ask": [
      "mcp__events__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 events. Review it before you use it.