Is the Pipeworx Io Data Utah MCP server down?

mcp-registry/io.github.pipeworx-io/data-utah · v0.1.0

Also listed as glama/pipeworx-io/data-utah

down
Last checked 2026-10-18 13:42 UTC · handshake 80ms

As of 2026-10-18 13:42 UTC, the Pipeworx Io Data Utah MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 0% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 71 minutes.

uptime (30d checks)
0%
checks observed
5
outages (90d)
1
tools
34

Utah state open data via Socrata SoQL — government, grants, health, demographics.

Point your MCP client at this streamable-http endpoint: https://gateway.pipeworx.io/data-utah/mcp

Agent-readiness: B (86/100)

B (86/100): 1 error(s), 0 warning(s) across 34 tool(s); ~10,177 tokens of tool definitions.
Scores higher than 52% of 15,682 MCP servers Glimind has audited.
Its tool list costs an agent ~10,177 tokens per session — more than 80% of servers.
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints100
Token cost100
Client compatibility70
Protocol100
Reliability0
Stability100

What to fix (2)

The endpoint did not complete an MCP handshake.

Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. 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 →

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":["mcp-registry/io.github.pipeworx-io/data-utah"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.pipeworx-io/data-utah"}) over MCP.

Passed

Largest tool definitions

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:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.pipeworx-io%2Fdata-utah.svg)](https://glimind.com/server/mcp-registry%2Fio.github.pipeworx-io%2Fdata-utah?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fio.github.pipeworx-io%2Fdata-utah?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.pipeworx-io%2Fdata-utah.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.pipeworx-io%2Fdata-utah.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.pipeworx-io%2Fdata-utah?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:2bf7643e91371188…, first seen 2026-10-17, included at leaf 8005 of 65,174. Version history · verify what your client received.

Working alternatives

Tools (34)

Compare: most reliable ml servers · most reliable retrieval servers · most reliable other servers · most reliable data servers · most reliable search servers

Know before your agent calls it

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.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

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"
    }
  }
}

FAQ

Is the Pipeworx Io Data Utah MCP server down right now?

As of 2026-10-18 13:42 UTC, the Pipeworx Io Data Utah MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 0% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 71 minutes.

How many tools does Pipeworx Io Data Utah MCP server provide?

Pipeworx Io Data Utah MCP server advertises 34 tools, including ai_visibility_check, ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, bet_research.

How do I install Pipeworx Io Data Utah MCP server?

Point your MCP client at this streamable-http endpoint: https://gateway.pipeworx.io/data-utah/mcp

Is the Pipeworx Io Data Utah MCP server safe to connect to an AI agent?

Glimind scanned all 34 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 Pipeworx Io Data Utah MCP server?

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.

Feedback
Help us improve