@pipeworx/wisconsin-code

Connect: https://pipeworx.io/mcp — every tool in the catalog, including @pipeworx/wisconsin-code’s. Install: one-click buttons

Connect to just the @pipeworx/wisconsin-code pack

https://gateway.pipeworx.io/wisconsin-code/mcp — only @pipeworx/wisconsin-code’s own tools, nothing else in the catalog.

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 1

Keyless. 940.01 is first-degree intentional homicide.

Why this one is assembled, not sliced

Wisconsin heads its History and Note blocks with the same section number and places them BEFORE the statute, so any positional anchor lands on editorial apparatus. The markup instead tags each subsection with the citation it belongs to (data-cites="statutes/940.01(1)(a)"), so the text is assembled from those spans. When a page tells you what each fragment is, use that rather than inferring from position.

Stored copy and data_as_of (fleet #3581)

The Legislature’s site answers US data centres but refuses or stalls from Singapore: over 7 days only 7 of 176 external calls succeeded (US callers 57 of 57). A cache cannot help a first touch, so the statutes are stored, one JSON object per chapter, in the shared statute store (R2, statutes/wi/) that the Illinois, Indiana, North Carolina and Wyoming packs also use. The gateway hands the pack its R2 binding and the pack reads only the chapter a call names. A section found there is answered with no upstream request; the response says served_from: "stored-copy" and carries data_as_of (when that chapter was last read from the source). A section the copy cannot answer (chapter missing, or listed with no stored text) falls back to the live read with its short-lived cache. (fleet #3596: the copy used to be 470 files in git, 47.7 MiB in every worktree, re-uploaded to KV on every gateway deploy.)

Nothing is loaded at module scope: the data never enters the gateway bundle.

Refresh

node mcps/wisconsin-code/scripts/bake-chapters.mjs            # all chapters -> mcps/wisconsin-code/.bake/
node mcps/wisconsin-code/scripts/bake-chapters.mjs --only 940 # one chapter
node mcps/wisconsin-code/scripts/bake-chapters.mjs --resume   # skip chapters already on disk
node mcps/wisconsin-code/scripts/upload-chapters.mjs          # publish to R2 (statutes/wi/), changed chapters only

Sequential, with a delay between requests and an honest user agent. Exit 0 only if every chapter in the table of contents was fetched and parsed and the totals clear the floors (default 400 chapters, 12,000 sections with text); any section that cannot be fetched leaves its chapter’s previous file untouched and the run exits 1 with the counts. A chapter whose text is unchanged keeps its previous data_as_of. The baked files are a working copy, not committed (.bake/ is gitignored); upload-chapters.mjs writes only the chapters whose content hash differs from the one recorded in statutes/wi/_manifest.json, so a refresh that finds nothing new writes nothing. It uses wrangler r2 object put --remote under the operator login; no API token.

Data source

Wisconsin Legislature, Wisconsin Statutes. Wisconsin statutes are public record; this pack reads the published statutes and republishes no annotations.

Tools

  • wi_statute — Get the FULL TEXT of a section of the Wisconsin Statutes — Wisconsin state law — by citation. “Wis. Stat. 940.01” is first-degree intentional homicide. Returns the statutory text. Keyless. Use for “wh

Tools

  • wi_statute — Get the FULL TEXT of a section of the Wisconsin Statutes — Wisconsin state law — by citation. Wis. Stat. 940.01 is first-degree intentional homicide. Returns the statutory text. Keyless. Use for what

Regenerated from source · build October 30, 2026