mcpbeat Sign in

Events MCP Server

answering

Events is answering right now. Last checked 9 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 52 days of history · worst day 87%
52 days agonow
90.1%
Uptime 24h
82 of 91 checks
2
Tools
read from the server
138 ms
Response time
average over 24h
0
Stars
last commit 8 Jun 2026

Events does not always answer

Over the last week it answered 97.5% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 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 151 ms 9 min ago

Alternatives to Events

same job, measured the same way
Whyismy Org
by parkragsterman

Sourced answers to everyday "why is my…" questions — health, pets, home, plumbing, tech, cars.

4 tools answering
Who Do I Call For? — Emergency Home-Service Router
by woodydaniel

Routes home emergencies to the right trade: who to call in what order, first steps, sourced costs.

3 tools answering
KMP
by underpass-ai

Local-first agent memory that preserves what happened, when and why

local only
Dorsal
by godorsal

Field evidence for coding agents: what AI builders shipped, broke, and fixed. Dated, source-linked.

answering
Verified Numbers
by jfortier93

Current source-cited 2026 US tax constants and calculators for AI agents; every answer cites IRS.

answering
OSINT MCP
by rjn32s

26 free OSINT tools as MCP tools for AI agents. Auto-installs everything on first run.

73 installs/wk local only
agentdocs
by titov-d

Fresh, source-verified docs for building MCP servers and Claude agents, for AI coding agents.

36 installs/wk local only
Mnemograph
by tm42

Event-sourced knowledge graph memory for AI coding agents with semantic search

148 installs/wk local only

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 82 of 91 checks got a reply (90.1%), average response time 138 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 138 ms on average, which is faster than 87% 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, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.