MCP.Market

Events MCP server

online · 100% uptime
by yeehaw.bot·bot.yeehaw/events·v1.0.1

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

B81/100grade B
What users say
No reviews yet
Be the first
Safety scan
B81/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Events yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Events tools (2)

write = sends, deletes, buys or posts
  • find_eventsFree

    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.

  • overviewFree

    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.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 244ms20/20
  • Tool poisoning2 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 111 days ago8/15
  • Maintainer identitynamespace and repository owner differ; GitHub account older than a year; website matches verified namespace8/10
Overall 81/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Events compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
81/100
higher than 63% of 4,460 AI and agents servers
Tools
2
the typical AI and agents server has 6
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote AI and agents server answers 100%
Response time
30 ms
faster than 97% of 2,331 AI and agents servers

What its tools let an agent do: 2 read

Install Events in Claude Code, Cursor or VS Code

claude mcp add --transport http events https://yeehaw.bot/mcp
Add to Cursor

What the publisher says

From the Events repository's README, as published. We do not edit it. Read it on GitHub

Yeehaw — Austin events, as an MCP server 🤠

Yeehaw is an agent-first city concierge for Austin, TX — the fresh, sourced, citeable answer to "what's happening in Austin?". Ask any LLM that today and it guesses from stale listicles. Yeehaw ships the structured, current, attributable source of truth, exposed as a public MCP server any AI assistant can call.

  • 🌐 Site: https://yeehaw.bot · for agents: https://yeehaw.bot/for-agents
  • 🔌 MCP endpoint: https://yeehaw.bot/mcp (JSON-RPC over HTTP) — no signup, no key, free
  • 📇 Official MCP registry: bot.yeehaw/events

~2,800 live Austin events aggregated hourly from 10 sources (Ticketmaster, Do512, Luma, Visit Austin, Alamo Drafthouse, Capital Factory, UT Austin, Huston-Tillotson, City of Austin open data, and a Brave-powered discovery net), deduplicated and ranked — every event carries its source.

Connect

Drop-in config for any MCP client (Claude, Cursor, Cline, …):

// .mcp.json
{ "mcpServers": { "yeehaw": { "url": "https://yeehaw.bot/mcp" } } }

Or call it directly:

curl -s https://yeehaw.bot/mcp \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
       "params":{"name":"find_events",
         "arguments":{"date_range":"this_weekend","limit":3}}}'

Tools

See AGENTS.md for the usage contract (when to call what, value ranges, honest caveats).

Why depend on it

  • Fresh — re-ingested hourly; past events drop automatically.
  • Sourced — every event cites its origin with a clickable link; your assistant can footnote instead of hallucinate.
  • Resilient — per-source circuit breakers; a single upstream outage degrades honestly instead of corrupting the answer.
  • Honest — ticket prices are sparse upstream, so pricemin/pricemax are often null; find_events reports how many results it couldn't price rather than guessing.

About

Yeehaw is operated by Capital Thought, LLC (Austin, TX). Not an official City of Austin outlet.

This repo is the public discovery surface (docs + agent contract + registry descriptor). The service itself runs on Cloudflare Workers + Supabase.

Nothing above is checked by us. What we check is on the safety report.

Events: common questions

Is Events MCP server safe?
Mostly: it is graded B (81/100). Read the Events safety report
How do I install Events?
It runs remotely at yeehaw.bot. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Events need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Events maintained?
The last commit was 149 days ago (2026-06-08). The latest release is v1.0.1.
Is Events up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Events?
Servers from other publishers that do the same job: Basic Memory MCP server, HOL Guard MCP server and Agent-Native Chat MCP server.
How does Events compare with other AI and agents MCP servers?
safety score 81/100 (higher than 63% of 4,460 AI and agents servers); tools 2 (the typical AI and agents server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Events

Same job from other publishers: the closest match first, then the best rated.

  • Basic Memory
    Local-first knowledge management with bi-directional LLM sync via Markdown files.
    B
  • HOL Guard
    Local-first AI agent security evidence and approval workflows through HOL Guard's stdio MCP server.
    A
  • Agent-Native Chat
    Minimal chat-first app with durable threads, actions, and the app-agent loop
    A
  • Agent Recall
    Correction-first agent memory. Precision KPI tracks if agents heed warnings. 5 layers, local-only.
    A