Data Collection

yeehaw.bot

Retrieves and reports on Austin events from a deduplicated data store, including operational monitoring of data ingestion and system health.

1 endpoint2 known toolsFirst detected June 18, 2026Last detected August 31, 2026

ENDPOINT 1

https://yeehaw.bot/mcp

No auth detected

MCP server metadata

Name: yeehaw
Version: 1.0.0

Capabilities

tools

Known tools 2

find_events

Find upcoming Austin events from Yeehaw's sourced, deduplicated store.

Inferred read-only

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.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.yeehaw]
url = "https://yeehaw.bot/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "yeehaw": {
      "type": "http",
      "url": "https://yeehaw.bot/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: yeehaw
Remote MCP URL: https://yeehaw.bot/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "yeehaw": {
      "type": "http",
      "url": "https://yeehaw.bot/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "yeehaw",
  "transport": "streamable-http",
  "url": "https://yeehaw.bot/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for yeehaw.bot was fetched 2026-08-24T05:07:08.056Z and is being refreshed.

Trust status Neutral

yeehaw.bot is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.