# New Hampshire Code (npm · @pipeworx/mcp-new-hampshire-code)

New Hampshire RSA (Revised Statutes Annotated) — state statutes by citation and by topic. Fleet…

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-new-hampshire-code/new-hampshire-code-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-new-hampshire-code/new-hampshire-code-mcp)
- npm · `@pipeworx/mcp-new-hampshire-code`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-new-hampshire-code/pipeworx-mcp-new-hampshire-code.md), [page](https://verifymcp.io/servers/pipeworx-io-new-hampshire-code/pipeworx-mcp-new-hampshire-code)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-new-hampshire-code`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-new-hampshire-code).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 557 tokens (~278/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the New Hampshire Code MCP server?

New Hampshire Code runs locally as an npm package, launched with npx -y @pipeworx/mcp-new-hampshire-code. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-new-hampshire-code -- npx -y @pipeworx/mcp-new-hampshire-code
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add pipeworx-io-new-hampshire-code -- npx -y @pipeworx/mcp-new-hampshire-code
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-new-hampshire-code": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-new-hampshire-code"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-new-hampshire-code --command npx --arg -y --arg @pipeworx/mcp-new-hampshire-code
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-new-hampshire-code:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-new-hampshire-code"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-new-hampshire-code": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-new-hampshire-code"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-new-hampshire-code -t stdio -c npx -a -y @pipeworx/mcp-new-hampshire-code
```

### Other

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 82, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-03 (score 66, −15)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-02 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 79)

First indexed and scored.

## MCP tools (2)

### `nh_statute` (~291 tokens)

Get the FULL TEXT of a section of the New Hampshire RSA (Revised Statutes Annotated) — New Hampshire state law — by citation. "630:1" is capital murder; "540:2" lists grounds for landlord eviction. Accepts natural forms: "630:1", "RSA 630:1", "§ 630:1". Returns the current statutory text, the official catchline, chapter/title context, and the amendment HISTORY taken verbatim from the section's own "Source." line (e.g. "Source. 1971, 518:1. 1974, 34:1. ... 2019, 42:1, eff. May 30, 2019."). New Hampshire publishes the CURRENT text only — no per-year historical archive and no "view as of" picker, verified live; this tool says so rather than guessing. Keyless. Use for "what does RSA 630:1 say" or to check a New Hampshire statute a case or lease relies on.

Input parameters:

- `citation` (string, required): Section citation, chapter:section, e.g. "630:1" (capital murder) or "540:2" (landlord eviction grounds). Some sections carry a letter suffix, e.g. "630:1-a", or a letter-suffixed chapter, e.g. "632-A…

### `nh_search` (~210 tokens)

Search the New Hampshire RSA BY TOPIC or keyword rather than citation — "landlord security deposit", "concealed weapon permit", "capital murder". Matches against the General Court's own official section and chapter CATCHLINES across the whole RSA (not full statutory prose — New Hampshire does not publish a full-text search of RSA section text, verified live). "landlord"/"tenant"/"lessor"/"lessee" are expanded to their statutory counterpart (NH's own catchlines name the landlord-tenant relationship by "tenant" almost exclusively, e.g. "Actions Against Tenants", even for chapters squarely about landlord obligations like security deposits), returned in `expanded_terms` when it fires. Returns matching citations and catchlines; call nh_statute with a citation for the full text. Keyless.

Input parameters:

- `limit` (number): Max results to return, default 10, max 25.
- `query` (string, required): Topic or keywords, e.g. "landlord security deposit".

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-new-hampshire-code/pipeworx-mcp-new-hampshire-code#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 66
- 2026-11-02: 81
- 2026-11-01: 80
- 2026-10-31: 80
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### What is the New Hampshire Code MCP server?

New Hampshire Code is an MCP server listed in the public MCP registry as io.github.pipeworx-io/new-hampshire-code. New Hampshire RSA (Revised Statutes Annotated), state statutes by citation and by topic. Fleet… This page covers its npm package (@pipeworx/mcp-new-hampshire-code).

### Is the New Hampshire Code MCP server safe to use?

New Hampshire Code scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the New Hampshire Code MCP server expose?

New Hampshire Code exposes 2 tools: nh_statute, nh_search. Their descriptions and schemas cost roughly 501 tokens of context every time the server is loaded.

### Is the New Hampshire Code MCP server still maintained?

New Hampshire Code is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the New Hampshire Code MCP server under?

New Hampshire Code declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the New Hampshire Code MCP server?

VerifyMCP ran 16 checks on New Hampshire Code, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-new-hampshire-code
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-new-hampshire-code
- Repository: https://github.com/pipeworx-io/mcp-new-hampshire-code
- Website: https://pipeworx.io/packs/new-hampshire-code
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-new-hampshire-code/pipeworx-mcp-new-hampshire-code.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-new-hampshire-code/pipeworx-mcp-new-hampshire-code/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-new-hampshire-code/pipeworx-mcp-new-hampshire-code.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-new-hampshire-code/pipeworx-mcp-new-hampshire-code