Utah Code MCP server

@pipeworx/utah-code

Utah Code — state statutes by citation, full text plus effective date and amendment history, and topic/keyword search across the whole Code.

Part of Pipeworx — an MCP gateway connecting AI agents to 1764+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

(e.g. "76-5-203", "53-5a-102.2"), with its effective date and amendment history (e.g. "Amended by Chapter 356, 2026 General Session"). Does NOT return superseded/historical full text — le.utah.gov's own code viewer only ever lists one "Current Version" per section; only the amendment citation survives for a prior change, not the prior text.

• utcodesection(section) — full text of a Utah Code section by citation

every Utah Code section, returning citation + title + url for each hit.

• utcodesearch(query, limit?) — full-text keyword/topic search across

Auth

Keyless.

Data sources

Title76/Chapter5/76-5-S203.html) — the public section VIEWER page. It is a template whose statute text is injected by client-side JS, so a bare fetch returns only the chrome — but the page's inline script block always carries a line of the form var versionDefault="C76-5-S203_2026050620260506";, which names the current version's content document. No bot wall: a bare default UA gets the same 200 a browser does, this pack just sends an honest one anyway.

• https://le.utah.gov/xcode/TitleNN/ChapterMM/NN-MM-Sxxx.html (e.g.

.html appended (e.g. C76-5-S203_2026050620260506.html) — the actual statute text. Plain, un-rendered HTML (no JS): a breadcrumb trail, an "Effective MM/DD/YYYY" line, the statute body as nested HTML-table rows with the subsection letters ("(1)", "(a)", "(i)") printed as literal cell text, and a trailing "Amended by Chapter N, YYYY General Session" history note. The SAME document is also published as PDF / RTF / XML (same basename, different extension) — the XML is cleaner markup but drops the subsection letters as literal text (they live only in a number attribute instead), which is why this pack reads the plain-HTML fragment rather than the XML.

• The content document named by versionDefault, in the SAME directory with

le.utah.gov's own "Keyword Search" nav link for the Code (/solrsearch.jsp?ktype=Code), called directly rather than through that JS-rendered results shell. fq=category:Code scopes it to statute text; without that filter it searches bills, committee docs, and more. Known quirk, not documented anywhere on the site: the proxy decodes its own query params and forwards them to an internal Solr server (LESOLR:8080) WITHOUT re-encoding, so a literal space in q becomes a literal space in the upstream HTTP request line and Solr 400s on it. Multi-word queries need the space DOUBLE-encoded as %2520 (which decodes once, server-side, to the still-valid string %20) rather than the normal %20/+ — single-word queries work either way. The gate did not need to forge an identity: an honest UA and a GET is all it takes.

• https://le.utah.gov/servlet/solrproxy9 — the keyless Solr proxy backing

Both the viewer-page quirk and the Solr double-encoding quirk were found by probing live with curl before writing any code — the August state-law survey had filed Utah as "client-rendered or bot-walled" on the strength of the viewer page alone.

Reachability — this pack goes through the egress relay

Shortened. The full README is on GitHub.