Hawaii Code MCP server

@pipeworx/hawaii-code

Hawaii Revised Statutes (HRS) — state statutes by citation, by official catchline (topic search), with inline amendment/enactment history and a year-by-year historical archive back to 1999. Keyless.

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

Tools

("707-701" is murder in the first degree; "521-44" is a landlord's security-deposit duty under the Residential Landlord-Tenant Code). Includes the official catchline, chapter context, and amendment/enactment history parsed from the Legislature's own trailing "[L 1972, c 9, ...]" session-law bracket. Pass year (1999-2025) to get that year's archived text of the same section instead of the current one.

• hi_statute(citation, year?) — full text of an HRS section by citation

own official section and chapter catchlines (not full statutory prose — see below), returning matching citations.

• hi_search(query, limit?) — topic/keyword search over the Legislature's

Auth

Keyless.

The survey trap did not apply — it was never really walled

The August survey recorded "Hawaii (403)" and stopped there. Looking past it: the Legislature's statute site (www.capitol.hawaii.gov/hrscurrent/) sits behind Cloudflare and its WAF returns a hard 403 "Sorry, you have been blocked" to this fleet's laptop/office IP on every request — reproduced with a dozen UA/Accept/Accept-Language combinations, including a full real-Chrome header set, 0 passes. That matched the described trap.

The edge probe said otherwise. A throwaway wrangler dev --remote Worker on the prod Cloudflare account, fetching the exact same URLs, got clean 200s every time — cache HIT and MISS, a dozen distinct real pages, zero blocks. This is the inverse of the oscn.net/oklahoma-code case (Worker blocked, browser fine): here the Cloudflare Worker is the client that gets through, and the laptop is the one that doesn't. Since the live gateway is a Cloudflare Worker, it needs no egress relay, no special header, and no BYOK — a plain fetch() from the gateway reaches the site directly. The pack's own src/index.ts header has the full probe trail; this file's job is just to record the conclusion for the next person who sees "403" in a survey and reaches for the relay reflexively.

No combined index, no search API — one TOC fetch per chapter, baked once

hrscurrent/ is a plain IIS directory tree, one file per section:

/hrscurrent/Vol{NN}_Ch{range}/HRS{chapterNum}/HRS_{chapterNum}-{section}.htm

Every chapter directory also carries exactly one extra file — HRS{chapterNum}-.htm — which is the chapter's own official table of contents: a "CHAPTER NNN" heading, the chapter's name, and every section number with its official catchline. One fetch per chapter (1,108 of them) is enough to bake the whole citation + catchline index; hisearch reads that baked table entirely in memory. hi_statute uses the baked table to resolve a chapter, then encodes the expected filename for the requested section and fetches it live — falling back to a live directory listing if the encoded guess doesn't resolve (a section added, renumbered, or carrying a decimal/letter-suffix shape the encoder didn't predict since the last bake). The baked table never carries statutory body text.

Three TOC-parsing traps, found by actually diffing bake output, not by inspection

Shortened. The full README is on GitHub.