mcp-registry/bot.yeehaw/events · v1.0.0
As of 2026-10-26 23:22 UTC, the Yeehaw Events MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Agent-first Austin events concierge — fresh, sourced answers to what's happening in Austin.
Point your MCP client at this streamable-http endpoint: https://yeehaw.bot/mcp
2 of 2 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fbot.yeehaw%2Fevents/fixes
{
"name": "find_events",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "Fetch one event by id; ignores date_range and other filters when set."
},
"limit": {
"type": "integer",
"default": 20,
"description": "Max results, default 20, clamped to 50."
},
"query": {
"type": "string",
"description": "Free-text keyword match against event titles."
},
"category": {
"type": "string",
"description": "Category slug (e.g. music, sports, civic)."
},
"price_max": {
"type": "number",
"description": "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 states how many were not price-filtered."
},
"date_range": {
"type": "string",
"description": "Required unless `id` is set. e.g. today, tonight, this_weekend, next_7_days, or an ISO date range."
},
"neighborhood": {
"type": "string",
"description": "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."
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/bot.yeehaw/events"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/bot.yeehaw/events"}) over MCP.
find_events ~400 tokensoverview ~82 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fbot.yeehaw%2Fevents?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fbot.yeehaw%2Fevents?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fbot.yeehaw%2Fevents.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fbot.yeehaw%2Fevents.svg :target: https://glimind.com/server/mcp-registry%2Fbot.yeehaw%2Fevents?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:3659bd59253364c9…, first seen 2026-10-17, included at leaf 2665 of 76,061. Version history · verify what your client received.
Compare: most reliable search servers · most reliable devops servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 23:22 UTC, the Yeehaw Events MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Yeehaw Events MCP server advertises 2 tools, including find_events, overview.
Point your MCP client at this streamable-http endpoint: https://yeehaw.bot/mcp
Glimind scanned all 2 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.