# North Dakota Code (npm · @pipeworx/mcp-north-dakota-code)

North Dakota Century Code — state statutes by citation and by topic. Fleet #2743.

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

## Components

- remote · `gateway.pipeworx.io`: 71/100, [markdown](https://verifymcp.io/servers/pipeworx-io-north-dakota-code/north-dakota-code-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-north-dakota-code/north-dakota-code-mcp)
- npm · `@pipeworx/mcp-north-dakota-code`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-north-dakota-code/pipeworx-mcp-north-dakota-code.md), [page](https://verifymcp.io/servers/pipeworx-io-north-dakota-code/pipeworx-mcp-north-dakota-code)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-north-dakota-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-north-dakota-code).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 495 tokens (~247/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 North Dakota Code MCP server?

North Dakota Code runs locally as an npm package, launched with npx -y @pipeworx/mcp-north-dakota-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-north-dakota-code -- npx -y @pipeworx/mcp-north-dakota-code
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add pipeworx-io-north-dakota-code -- npx -y @pipeworx/mcp-north-dakota-code
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-north-dakota-code --command npx --arg -y --arg @pipeworx/mcp-north-dakota-code
```

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-north-dakota-code": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-north-dakota-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-05 (score 83, +1)

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

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

- [security improvement] Malware scan: unverified → pass

### 2026-11-03 (score 67, −12)

- [security regression] Malware scan: pass → unverified
- [functional regression] Security disclosure: unverified → fail
- [functional improvement] Stability: unverified → 0.17
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-01 (score 79, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-30 (score 79, 0)

- [functional regression] Security disclosure: unverified → fail

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

First indexed and scored.

## MCP tools (2)

### `nd_statute` (~264 tokens)

Get the FULL TEXT of a section of the North Dakota Century Code — North Dakota state law — by citation. "12.1-16-01" is murder; "47-16-13.1" is a landlord's duty to maintain a rental unit. Accepts natural forms: "12.1-16-01", "NDCC 12.1-16-01", "§ 12.1-16-01". Returns the current statutory text, the official catchline, and chapter/title context. North Dakota publishes the CURRENT text only — no per-year historical archive and no general amendment-history field (a repealed or redesignated section's one-line session-law citation is included in the text as-is); this tool says so rather than guessing. Keyless. Use for "what does NDCC 12.1-16-01 say" or to check a North Dakota statute a case or lease relies on.

Input parameters:

- `citation` (string, required): Section citation, title-chapter-section, e.g. "12.1-16-01" (murder) or "47-16-13.1" (landlord maintenance duty). Some sections carry a decimal suffix, e.g. "47-16-07.3".

### `nd_search` (~172 tokens)

Search the North Dakota Century Code BY TOPIC or keyword rather than citation — "landlord security deposit", "concealed weapon permit", "homicide". Matches against the Legislature's own official section and chapter CATCHLINES across the whole Code (not full statutory prose — North Dakota does not publish a full-text search of Code section text, verified live), e.g. "landlord" surfaces sections like "Landlord obligations - Maintenance of premises" even though no CHAPTER is named "Landlord and Tenant". Returns matching citations and catchlines; call nd_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-north-dakota-code/pipeworx-mcp-north-dakota-code#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 82
- 2026-11-03: 67
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### What is the North Dakota Code MCP server?

North Dakota Code is an MCP server listed in the public MCP registry as io.github.pipeworx-io/north-dakota-code. North Dakota Century Code, state statutes by citation and by topic. Fleet #2743. This page covers its npm package (@pipeworx/mcp-north-dakota-code).

### Is the North Dakota Code MCP server safe to use?

North Dakota Code scores 83 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 North Dakota Code MCP server expose?

North Dakota Code exposes 2 tools: nd_statute, nd_search. Their descriptions and schemas cost roughly 436 tokens of context every time the server is loaded.

### Is the North Dakota Code MCP server still maintained?

North Dakota 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 North Dakota Code MCP server under?

North Dakota 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 North Dakota Code MCP server?

VerifyMCP ran 16 checks on North Dakota 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-north-dakota-code
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-north-dakota-code
- Repository: https://github.com/pipeworx-io/mcp-north-dakota-code
- Website: https://pipeworx.io/packs/north-dakota-code
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-north-dakota-code/pipeworx-mcp-north-dakota-code.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-north-dakota-code/pipeworx-mcp-north-dakota-code/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-north-dakota-code/pipeworx-mcp-north-dakota-code.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-north-dakota-code/pipeworx-mcp-north-dakota-code