MCP.Market

Utah Open Data MCP server

online · 100% uptime
by pipeworx-io·io.github.pipeworx-io/data-utah·v0.1.0

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

A87/100grade A
What users say
No reviews yet
Be the first
Safety scan
A87/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Utah Open Data yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Utah Open Data tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 21ms; handshake note: Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","id":0,"error":{"code":-32602,"message":"Unknown pack20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 13 days ago15/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 87/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Utah Open Data compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
87/100
higher than 73% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
11 ms
faster than 98% of 30,031 servers

Install Utah Open Data in Claude Code, Cursor or VS Code

claude mcp add --transport http data-utah https://gateway.pipeworx.io/data-utah/mcp
Add to Cursor

What the publisher says

From the Utah Open Data repository's README, as published. We do not edit it. Read it on GitHub

mcp-data-utah

Utah Open Data — US government open data (opendata.utah.gov) via the Socrata SoQL API: state government, grants, health & demographics. Keyless.

Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.

Tools

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "data-utah": {
      "url": "https://gateway.pipeworx.io/data-utah/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/data-utah/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1476+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Data Utah data" })

The gateway picks the right tool and fills the arguments automatically.

More

  • Docs and guides
  • pipeworx.io

License

MIT

Nothing above is checked by us. What we check is on the safety report.

Utah Open Data: common questions

Is Utah Open Data MCP server safe?
Yes, by our scan: it is graded A (87/100). Read the Utah Open Data safety report
How do I install Utah Open Data?
It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Utah Open Data need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Utah Open Data maintained?
The last commit was 52 days ago (2026-09-13). The latest release is v0.1.0.
Is Utah Open Data up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Utah Open Data compare with other MCP servers?
safety score 87/100 (higher than 73% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 11 ms (faster than 98% of 30,031 servers). Full comparison.

More from pipeworx-io →