# New Hampshire Code [Health: Active]

**Category:** ⚖️ Legal  
**Repository:** https://github.com/pipeworx-io/mcp-new-hampshire-code  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/new-hampshire-code

## Description
New Hampshire RSA (Revised Statutes Annotated) — state statutes by

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "new-hampshire-code": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-new-hampshire-code"]
  }
}
```

## Documentation

## What New Hampshire Code MCP server does

The New Hampshire Code MCP server exposes New Hampshire Revised Statutes Annotated content through two MCP tools. It connects to the state's official RSA pages on `gc.nh.gov` and returns current legal information rather than a locally stored copy of statutory text.

The `nh_statute` tool retrieves one RSA section by citation, such as `630:1`. Its result includes the section's current text, official catchline, title and chapter context, and the amendment or enactment information published in the section's `Source.` line. The `nh_search` tool searches official section and chapter catchlines across the state's 64 titles. Queries can cover topics such as landlord issues or concealed weapon permits.

This listing belongs to the Legal category and is intended for agents that need to locate or inspect current New Hampshire statutes.

## How it works

The server uses a baked index for the RSA table of contents. That index records citations, official catchlines, and title and chapter relationships, but not statutory text. The index is built by walking the state's root table of contents, title pages, and chapter pages.

When an agent requests a statute, the server maps the citation to the corresponding live section page and fetches that page at request time. It extracts the body from the site's `codesect` element and the amendment history from its `sourcenote` element. Citations containing hyphenated chapters or sections are supported, such as `632-A:1` and `630:1-a`.

The New Hampshire Code MCP server can route requests through an egress relay because the state site rejects Cloudflare-originated requests. Local development and laptop checks can fetch the source directly, while the gateway can supply relay details for deployed requests.

## Setup and configuration

Authentication is keyless. The provided material does not specify an API key, required environment variable, or client-specific configuration. The server reads its locally generated index and fetches live section pages when `nh_statute` is called.

The index should be regenerated when New Hampshire recodifies the RSA or incorporates new session laws. The documented refresh command is:

```bash
node scripts/bake-index.mjs > src/nh-index-data.ts
```

The refresh walks the public table-of-contents pages once. It does not embed the text of statutes, so refreshing the index and fetching current sections remain separate operations.

## Tools and capabilities

- `nh_statute(citation)`: Returns current text for one RSA section, its catchline, title and chapter context, and the source-line amendment history.
- `nh_search(query, limit?)`: Searches official section and chapter catchlines by topic or keyword, with an optional result limit.
- Amendment history: Returns the session-law history published with an in-force section.
- Repealed-section handling: Distinguishes documented repealed, redesignated, transferred, renumbered, or omitted sections from an unexpected empty response.

## Limitations and notes

Search is not full-text search. `nh_search` examines official catchlines only, not the prose inside statutes. A term that appears only in statutory text may therefore produce no result.

Results from `nh_statute` represent the current online RSA. The source history identifies when a section was created or amended, but the server does not provide the wording that existed before an amendment. New Hampshire's publication does not expose a historical-version archive or date selector through the documented pages.

The baked index can become stale if a section is changed after the last refresh. A citation present in that index may also return a live 404 after a later renumbering or repeal. The official source remains the state site, and the tool reports such index-versus-live mismatches separately rather than treating them as ordinary missing searches.

The integration is independent and unofficial. It is not affiliated with, endorsed by, or published by the New Hampshire government site.

_Full upstream README: https://allmcps.com/mcp/new-hampshire-code/readme_