@pipeworx/new-jersey-code

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

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: 2

New Jersey Statutes (N.J.S.A.) by citation — with amendment history where the source lists one — plus full-text topic search. Keyless.

Tools

• nj_statute_section(section) — full text of one N.J.S.A. section by citation (e.g. "2C:11-3", "39:4-50", "46:8-19"), with its amendment_history line parsed out when the section has been amended.
• nj_statute_search(query, limit?) — full-text search by topic/keyword (“security deposit interest”, “landlord grounds for eviction”); returns ranked sections with citation + heading where the hit title parses as one.

Auth

Keyless.

Data sources

• https://lis.njleg.state.nj.us/nxt/gateway.dll — the New Jersey Legislature’s statute-viewer subdomain (NXT4/Folio document publishing, IIS-hosted). This is a DIFFERENT legislature subdomain than the njleg.state.nj.us Next.js site most links point at — that one is bills/session focused and does not itself host statute text.

Shape of this source, because it is not a REST API

The viewer is session-cookie based, not a clean lookup-by-id endpoint:

1. f=xhitlist is a full-text search. It sets a session cookie and renders its hit list as plain server-side HTML (<a class="hit-doc-link" href="...">title</a> rows) — no JS execution needed to read it.
2. A citation lookup queries the EXACT quoted phrase "<citation> " (trailing space, inside the search). That trailing space is load-bearing: an unquoted citation free-text-matches thousands of sections that merely contain the same digits, and even the quoted phrase WITHOUT the trailing space still matches dotted/lettered children (“39:4-50.17”, “39:4-50c”) because “50” is a literal prefix of “50.17”. The space forces the match onto a token boundary.
3. Each hit’s href is an f=hitdoc$hitdoc_bm=... link. Resolving it (GET, with the search’s session cookie, redirect: manual) 302s to the document’s permanent, COOKIE-FREE path: /nxt/gateway.dll/statutes/<a>/<b>/<c>.
4. That path is fetched directly for the actual statutory text.

This is a session-cookie flow across two ordinary GETs — not the ASP.NET __VIEWSTATE postback pattern (there is no postback form anywhere in it), and it carries no CAPTCHA or other anti-bot wall. It has been reachable from a Cloudflare Worker at the rate one caller generates; it has not been load tested.

Amendment history is free; a prior point-in-time version is not

Every amended section’s text ends with a trailing amended 1979, c.178, s.21; ...; 2017, c.150. (or, for a section’s original enactment, L.<year>, c.<n>, s.<n>.) line. nj_statute_section parses that into amendment_history rather than leaving it buried in text — an original, never-amended section simply has none (null). This source does NOT expose a point-in-time/prior-version snapshot of a section; nj_statute_section says so explicitly in its historical_version field rather than silently omitting the capability.

Topic search quality

nj_statute_search ANDs every word in the query (this is the upstream engine’s own behaviour, not something this pack adds) — a long sentence over-narrows; a few plain words (“landlord grounds for eviction”) works better than a full question.

Tools

• nj_statute_section — Get the FULL TEXT of a section of the New Jersey Statutes (N.J.S.A.) — New Jersey state law — by citation, plus its amendment history where the source lists one. “N.J.S.A. 2C:11-3” is murder; “39:4-50
• nj_statute_search — Search the New Jersey Statutes (N.J.S.A.) BY TOPIC or keyword rather than citation — “security deposit interest”, “landlord grounds for eviction”, “possession of weapons for unlawful purposes”. Return