Idaho Code MCP server

@pipeworx/idaho-code

Idaho Statutes (Idaho Code) — current statutory text by citation, amendment history, and topic/keyword search over official chapter and section catchlines, sourced live from legislature.idaho.gov.

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

"18-4001", murder), with the official catchline, chapter/title context, and the amendment "History:" line Idaho prints on nearly every section.

• id_statute({citation}) — full text of one section by citation (e.g.

section catchlines (plus their chapter's own catchline), e.g. "landlord", "concealed weapon permit". Not full-text search of statutory prose — Idaho publishes no keyless full-text search API (see "Data sources").

• id_search({query, limit?}) — topic/keyword search over the ~20,400 live

Auth

Keyless. No signup, no activation gate.

Data sources

title list (74 titles).

• https://legislature.idaho.gov/statutesrules/idstat/ — the Idaho Statutes

list for one title, with each chapter's official catchline.

• https://legislature.idaho.gov/statutesrules/idstat/Title{T}/ — chapter

section list for one chapter, with each section's official catchline.

• https://legislature.idaho.gov/statutesrules/idstat/Title{T}/T{T}CH{C}/ —

— one section's full text.

• https://legislature.idaho.gov/statutesrules/idstat/Title{T}/T{T}CH{C}/SECT{T}-{N}/

All four are plain WordPress-served HTML, keyless, no rate limit observed.

The citation does not literally name its chapter — but a formula recovers it

Idaho cites a section as title-number ("18-4001"), with no chapter digit written out. The chapter IS recoverable, because Idaho's own numbering is a strict chapter100 + sectionWithinChapter block — verified live across chapters 1, 5, 9, 40, 83 and 91 of Title 18, and chapter 1 of the single- chapter Titles 4 and 29: chapter 1 holds "18-100".."18-1xx", chapter 40 holds "18-4000".."18-4099", chapter 83 holds "18-8300".."18-8399". So chapter = floor(number / 100). idstatute uses that formula to build the direct URL, then VERIFIES it rather than trusting it — see "THE VERIFICATION CHAIN" in src/index.ts's file header and the three-step fallback it documents (confirm the computed chapter's own listing page before ever reporting a citation doesn't exist). A wrong chapter guess must read as a loud, investigable error, never as a quiet found: false.

Honest 404s — no Oklahoma/Texas-style disguised 200

Verified live from BOTH a laptop curl and a throwaway wrangler dev --remote Worker deployed to the production Cloudflare account (2026-10-07): every URL shape returns the SAME status and byte length from both vantage points. A nonexistent chapter or section returns a real HTTP 404 (a genuine error404 WordPress template, consistently 72,512 bytes) — not a 200 with page furniture and no statute, the trap that sank an earlier Oklahoma pack build (oscn.net answered a Cloudflare Worker differently from a laptop and returned found:false on every live call despite passing every local smoke). Idaho's site does not do that, confirmed both ways:

curl (laptop)        wrangler dev --remote (CF edge, prod account)
Title18/T18CH40/SECT18-4001/ (real)        200 / 91,548B         200 / 91,548B
Title18/T18CH40/ (real chapter listing)    200 / 92,122B         200 / 92,122B
Title18/T18CH999/ (bad chapter)            404 / 72,512B         404 / 72,512B
Title18/T18CH40/SECT18-9999/ (gap number)  404 / 72,512B         404 / 72,512B

Shortened. The full README is on GitHub.