# Utah Code [Health: Active]

**Category:** ⚖️ Legal  
**Repository:** https://github.com/pipeworx-io/mcp-utah-code  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/utah-code

## Description
Utah Code — state statutes by citation, plus topic search.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "utah-code": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-utah-code"]
  }
}
```

## Documentation

## What Utah Code does

The Utah Code MCP server gives an MCP client two statute-research tools: `ut_code_section` retrieves a section by citation, and `ut_code_search` searches across Utah Code by topic or keyword. A citation can use formats such as `76-5-203` or `53-5a-102.2`.

Section results include the current statutory text, an effective date, and available amendment history. Search results provide matching citations, titles, and URLs. This makes the server suitable for legal research workflows that need to locate relevant Utah provisions before reviewing a specific section.

The package belongs in the Legal category and is an independent, unofficial integration. It is not affiliated with, endorsed by, or published by the upstream provider.

## How it works

The Utah Code MCP server reads statute content from public pages on `le.utah.gov`. The viewer page identifies the current content document, while the related document contains the statute text, effective-date line, subsection structure, and amendment note. Keyword searches use the Utah legislature website’s Code-scoped search service.

The service does not provide superseded full-text versions. The source identifies the current version for a section and may retain an amendment citation, but it does not expose the prior wording of the statute.

You can use the hosted endpoint at `https://gateway.pipeworx.io/utah-code/mcp`, or run the package locally over MCP stdio with `npx -y @pipeworx/mcp-utah-code`. The hosted gateway also exposes shared Pipeworx tools, while the standalone process lists only this package’s tools.

## Setup and configuration

No authentication key is required. Add the hosted URL to an MCP client that supports remote MCP connections, or configure the local package as a command-based server:

```json
{
  "mcpServers": {
    "utah-code": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-utah-code"]
    }
  }
}
```

The hosted service can also be called through the gateway’s HTTP tool endpoint. For example, a request to `/v1/tools/ut_code_section` can pass `{"section":"76-5-203"}` as JSON. The README states that initial calls do not require an account.

## Tools and capabilities

- `ut_code_section(section)`: Gets current full text for a cited Utah Code section, along with its effective date and amendment history.
- `ut_code_search(query, limit?)`: Performs full-text keyword or topic search across Utah Code and returns citation, title, and URL for each match.
- `ask_pipeworx`: Available through the hosted gateway for natural-language routing across the broader Pipeworx catalog; it is not part of the standalone package.

## Limitations and notes

The source website renders its section viewer with client-side JavaScript, so the implementation uses the underlying content document instead of relying on the viewer’s visible shell. The hosted route also uses an egress relay to reach the source because of the source host’s certificate-chain behavior; certificate verification is completed through the relay rather than disabled.

Search behavior has a source-specific encoding requirement for multi-word queries. The integration handles that behavior internally. Historical section text is unavailable, so users needing the wording in effect before an amendment must consult another historical source. The Utah Code MCP server returns current content and amendment references, not a complete legislative version archive.

_Full upstream README: https://allmcps.com/mcp/utah-code/readme_