Utah Open Data

io.github.pipeworx-ioPublished by GitHub account pipeworx-iov0.1.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

Remote MCP endpoint for Utah state open data on Socrata, letting an assistant search datasets and run SoQL queries over government, grants, health and…

What you can do
  • Search the Utah Open Data catalog by keyword and get each dataset's resource_id, name, description, category and update date
  • Run Socrata SoQL queries against a dataset by resource_id, with where, select, group and order clauses plus limit and offset, returning rows as JSON
  • Read a dataset's schema and metadata: columns, types, row count, category and last-updated date
  • Ask questions in plain English through the gateway's ask_pipeworx meta-tool, which routes to the right tool
  • Use shared gateway meta-tools such as discover_tools, search_within and remember/recall that are listed alongside the pack's own tools
When to use it
Useful when an assistant needs Utah-specific public data — state government, grants, health or demographics — and you want keyless access without building your own Socrata client. Also handy for exploratory questions where the assistant should find the right dataset first and then query it.
Requirements
A remote streamable HTTP endpoint; no package install. No authentication, API keys, environment variables or headers are declared. Network access to the gateway host is required. The endpoint lists roughly 30 shared gateway meta-tools in addition to this pack's three tools.
Before you install
The endpoint exposes more than the three documented tools: shared Pipeworx meta-tools are always mounted and cannot be turned off, which costs context and may route questions across the whole gateway catalog. Queries and questions are sent to a third-party gateway, not directly to the state data portal. Read-only tools are described, but verify scope in the initialize response.

Installation

In SourceWeft

  1. Open Utah Open Data in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.pipeworx-io%2Fdata-utah/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

README

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

ToolDescription
datasetsSearch the Utah Open Data catalog of open datasets by keyword. Returns each dataset's resource_id, name, description, category and update date — pass the resource_id to query/metadata.
queryRun a Socrata SoQL query against a Utah Open Data dataset by resource_id (e.g. "7n5d-er3z"). Filter with where/select/group/order (SoQL clauses, without the leading $) plus limit/offset. Returns matching rows as JSON.
metadataGet a Utah Open Data dataset's schema + metadata (columns, types, row count, category, last-updated) by resource_id, e.g. "7n5d-er3z".

Quick Start

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

json
{  "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 — ask_pipeworx, discover_tools, 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:

json
{  "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

License

MIT

Source: README.md at commit 6342529

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts