# Nist Standards (npm · @pipeworx/mcp-nist-standards)

NIST Standards MCP pack

- 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-nist-standards/nist-standards-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-nist-standards/nist-standards-mcp)
- npm · `@pipeworx/mcp-nist-standards`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-nist-standards/pipeworx-mcp-nist-standards.md), [page](https://verifymcp.io/servers/pipeworx-io-nist-standards/pipeworx-mcp-nist-standards)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-nist-standards`
- 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-nist-standards).
  - 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**: 65/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 797 tokens (~265/item across 3 items; 3 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 Nist Standards MCP server?

Nist Standards runs locally as an npm package, launched with npx -y @pipeworx/mcp-nist-standards. 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-nist-standards -- npx -y @pipeworx/mcp-nist-standards
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add pipeworx-io-nist-standards -- npx -y @pipeworx/mcp-nist-standards
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-nist-standards --command npx --arg -y --arg @pipeworx/mcp-nist-standards
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-nist-standards:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-nist-standards"]
```

### Netclaw

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

### Vellum

```bash
assistant mcp add pipeworx-io-nist-standards -t stdio -c npx -a -y @pipeworx/mcp-nist-standards
```

### Other

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

## 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-01 (score 81, +1)

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

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

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 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 (3)

### `nist_control` (~311 tokens)

Look up the full text of one NIST 800-53 security control or NIST 800-171 CUI security requirement by id — the control statement (requirement prose), discussion/guidance, and related controls. Use for "what does NIST control AC-2 require", "NIST 800-53 AC-2 access control", "FedRAMP control SC-7 boundary protection", "NIST authenticator management IA-5", "NIST CUI control 800-171 3.1.1". Forgiving id: accepts "AC-2", "ac-2", "AC-02", control enhancements "AC-2(1)" or "AC-2.1", and CUI ids "3.1.1" / "3.01.01". Source: SP 800-53 Rev 5 and SP 800-171 Rev 3 (official NIST OSCAL, public domain). Examples: {"id":"AC-2"}, {"id":"SC-7"}, {"id":"IA-5"}, {"id":"AC-2(1)"}, {"id":"3.1.1"}.

Input parameters:

- `id` (string, required): Control id, e.g. "AC-2", "ac-2", "AC-02", "SC-7", "IA-5", enhancement "AC-2(1)"/"AC-2.1", or CUI requirement "3.1.1".

### `nist_control_search` (~252 tokens)

Keyword search across NIST 800-53 security/privacy controls and NIST 800-171 CUI requirements by title and requirement text. Use when the id is unknown — "NIST security control for least privilege", "NIST control about session lock", "NIST 800-53 encryption at rest", "NIST cybersecurity control multi-factor authentication", "access control / identification and authentication / system and communications protection". All query tokens must match (case-insensitive AND). Optional family filter (code like "AC", "IA", "SC" or a family name like "access control"). Returns matching {id, family, title, snippet}. Source: SP 800-53 Rev 5 + SP 800-171 Rev 3. Examples: {"query":"least privilege"}, {"query":"multi-factor authentication","family":"IA"}, {"query":"boundary protection"}.

Input parameters:

- `family` (string): Optional family filter: code ("AC","IA","SC",…) or name ("access control").
- `limit` (number): Max results (default 10).
- `query` (string, required): Keywords, e.g. "least privilege" or "encryption at rest". All tokens must match.

### `nist_control_family` (~176 tokens)

List every NIST control in a family — the FedRAMP/800-53 control-family baseline. Use for "list all NIST access control controls", "NIST 800-53 AC family", "what controls are in identification and authentication", "NIST system and communications protection family". Input a family code ("AC", "IA", "SC", "AU", "SI", …) or a family name ("access control"). Returns the family title plus every control id + title (including enhancements). Source: SP 800-53 Rev 5 (+ SP 800-171 Rev 3). Examples: {"family":"AC"}, {"family":"identification and authentication"}, {"family":"SC"}.

Input parameters:

- `family` (string, required): Family code ("AC","IA","SC",…) or name ("access control").

## Diagnostics

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

## Score history

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

## Common questions

### What is the Nist Standards MCP server?

Nist Standards is an MCP server listed in the public MCP registry as io.github.pipeworx-io/nist-standards. NIST Standards MCP pack. This page covers its npm package (@pipeworx/mcp-nist-standards).

### Is the Nist Standards MCP server safe to use?

Nist Standards 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 Nist Standards MCP server expose?

Nist Standards exposes 3 tools: nist_control, nist_control_search, nist_control_family. Their descriptions and schemas cost roughly 739 tokens of context every time the server is loaded.

### Is the Nist Standards MCP server still maintained?

Nist Standards 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 Nist Standards MCP server under?

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

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-nist-standards
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-nist-standards
- Repository: https://github.com/pipeworx-io/mcp-nist-standards
- Website: https://pipeworx.io/packs/nist-standards
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-nist-standards/pipeworx-mcp-nist-standards.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-nist-standards/pipeworx-mcp-nist-standards.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-nist-standards/pipeworx-mcp-nist-standards