19hz
Server Details
19hz.info MCP.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-19hz
- GitHub Stars
- 0
- Server Listing
- mcp-19hz
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 46 tools
Most tools do have distinct purposes and the descriptions go to unusual lengths to say which to prefer, but several clusters genuinely overlap: ask_pipeworx / ask_pipeworx_beta (explicitly 'identical right now') / ask_pipeworx_grounded / deep_research / discover_tools / suggest_questions all answer 'find me data', and polymarket_edges / polymarket_arbitrage / polymarket_edge_tracker / bet_research / polymarket_kalshi_spread / polymarket_fill_risk are six prediction-market tools an agent must carefully separate. The bigger problem is that only `events` and `regions` relate to the server's stated identity (19hz electronic music), so an agent cannot tell what this server is for at all.
Names are readable and mostly snake_case, but the convention is mixed: verb_noun (validate_claim, generate_llms_txt, classify_row, resolve_entity), bare nouns (events, regions, remember, recall, forget, subscribe, entity_profile, deep_research), vendor prefixes (polymarket_*, kalshi_*, updown_*, ask_pipeworx*), and odd shapes like ai_visibility_check and updown_divergence_rate. No single predictable pattern an agent could generalize from.
46 tools is far too many for a server whose stated purpose is listing 19hz electronic/dance events, which is served by exactly 2 of them (`regions`, `events`). The remaining 44 are a general-purpose data gateway (SEC, FRED, FDA, Polymarket, memory, subscriptions) that dwarfs the nominal domain and makes the surface feel like two servers spliced together.
For the 19hz domain the surface is list-only: no get_event for a single event's details, no venue or artist listing, no line-up or ticket/timeslot operations, so any workflow past 'show me events in a region on a date' dead-ends. The unrelated gateway tools are individually broad, but they do not compensate for the thin coverage of the domain the server is named after.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Resident Advisor (ra.co) MCP.
Related MCP Servers
- -
- -
- -
- MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.