mcpbeat

Events MCP Server

bot.yeehaw/events
answering

Events is answering right now. Last checked 2 min ago. It exposes 2 tools. Last commit 8 Jun 2026.

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

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
92 of 92 checks
2
Tools
read from the server
107 ms
Response time
average over 24h
0
Stars
last commit 8 Jun 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

run in your terminal
claude mcp add events --transport http https://yeehaw.bot/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "events": {
      "url": "https://yeehaw.bot/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.events]
url = "https://yeehaw.bot/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "events": {
      "url": "https://yeehaw.bot/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "events": {
      "url": "https://yeehaw.bot/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

events
find_events
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.
overview
overview
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.

Endpoints

URLTransportStateLatencyChecked
https://yeehaw.bot/mcp streamable-http answering 126 ms 2 min ago

Events — questions

Answers built from our own checks of this server.

What can Events do?
It exposes 2 tools, read directly from the server on our last check. Among them: find_events, overview. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Events working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 107 ms. The bar chart above shows every period we have measured.
How do I connect Events?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Events need an API key?
No. Events completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Events?
It answers our handshake in 107 ms on average, which is faster than 82% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Events open source?
Yes — it is published under the MIT licence and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.