Is 19hz Events down?

pulsemcp/19hz-events · v0.1.0

Also listed as glama/pipeworx-io/mcp-19hz, mcp-registry/io.github.pipeworx-io/19hz · primary listing: mcp-registry/io.github.pipeworx-io/19hz

As of 2026-10-17 21:10 UTC, 19hz Events is up with a Glimind reliability score of 72/100 (grade C). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 69 minutes.

Bay Area underground electronic music events from 19hz.info via the Pipeworx MCP gateway.

claude mcp add --transport http 19hz-events https://gateway.pipeworx.io/19hz/mcp

{
  "mcpServers": {
    "19hz-events": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/19hz/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (86/100)

What to fix (3)

Get alerted

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":["pulsemcp/19hz-events"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "pulsemcp/19hz-events"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• Every tool and parameter is described.
• Every tool declares whether it is read-only or destructive.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.

Largest tool definitions

• company_facts ~937 tokens
• polymarket_edges ~904 tokens
• subscribe ~894 tokens
• research_row ~575 tokens
• ask_pipeworx ~525 tokens

Static 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:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/pulsemcp%2F19hz-events.svg)](https://glimind.com/server/pulsemcp%2F19hz-events?ref=badge)

<a href="https://glimind.com/server/pulsemcp%2F19hz-events?ref=badge"><img src="https://glimind.com/v1/readiness/badge/pulsemcp%2F19hz-events.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/pulsemcp%2F19hz-events.svg
   :target: https://glimind.com/server/pulsemcp%2F19hz-events?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:9c419ef21c5c04f4…, first seen 2026-10-17, included at leaf 7806 of 20,624. Version history · verify what your client received.

Tools (43)

• ai_visibility_check
• archive_compare
• archive_evidence
• ask_pipeworx
• ask_pipeworx_beta
• ask_pipeworx_grounded
• bet_research
• classify_row
• company_facts
• company_register_search
• compare_entities
• deep_research
• discover_tools
• entity_profile
• events
• forget
• generate_llms_txt
• kalshi_weather_edge
• list_subscriptions
• pipeworx_feedback
• pipeworx_trending
• polymarket_arbitrage
• polymarket_edge_tracker
• polymarket_edges
• polymarket_fill_risk
• polymarket_kalshi_spread
• recall
• recent_alerts
• recent_changes
• regions
• release_calendar_markets
• remember
• research_row
• resolution_audit
• resolution_diff
• resolve_entity
• scan_competitor_ai_presence
• scan_dependency
• search_within
• subscribe
• suggest_questions
• unsubscribe
• validate_claim

Compare: most reliable ml servers · most reliable web servers · most reliable knowledge servers · most reliable other servers · most reliable data servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is 19hz Events down right now?

As of 2026-10-17 21:10 UTC, 19hz Events is up with a Glimind reliability score of 72/100 (grade C). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 69 minutes.

How many tools does 19hz Events provide?

19hz Events advertises 43 tools, including ai_visibility_check, archive_compare, archive_evidence, ask_pipeworx, ask_pipeworx_beta.

How do I install 19hz Events?

Point your MCP client at this streamable_http endpoint: https://gateway.pipeworx.io/19hz/mcp

Is 19hz Events safe to connect to an AI agent?

Glimind scanned all 43 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.

Operator of 19hz Events?

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.