# ScoutWyze FIPS (npm · @scoutwyze/fips-mcp)

Is this product version FIPS 140-3 validated, in NIST's queue, or expiring? From NIST CMVP data.

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

## Components

- npm · `@scoutwyze/fips-mcp`: 76/100 (this document), [markdown](https://verifymcp.io/servers/scoutwyze-max-fips-mcp/scoutwyze-fips-mcp.md), [page](https://verifymcp.io/servers/scoutwyze-max-fips-mcp/scoutwyze-fips-mcp)

## Channel facts

- Registry: `npm`
- Package: `@scoutwyze/fips-mcp`
- Version: `0.1.0`
- 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**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.30.1, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 30 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 24 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 433 tokens (~108/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 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 4 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 ScoutWyze FIPS MCP server?

ScoutWyze FIPS runs locally as an npm package, launched with npx -y @scoutwyze/fips-mcp. 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 scoutwyze-max-fips-mcp -- npx -y @scoutwyze/fips-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "scoutwyze-max-fips-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@scoutwyze/fips-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "scoutwyze-max-fips-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@scoutwyze/fips-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add scoutwyze-max-fips-mcp -- npx -y @scoutwyze/fips-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "scoutwyze-max-fips-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@scoutwyze/fips-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add scoutwyze-max-fips-mcp --command npx --arg -y --arg @scoutwyze/fips-mcp
```

### Hermes

```yaml
mcp_servers:
  scoutwyze-max-fips-mcp:
    command: "npx"
    args: ["-y", "@scoutwyze/fips-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "scoutwyze-max-fips-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@scoutwyze/fips-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add scoutwyze-max-fips-mcp -t stdio -c npx -a -y @scoutwyze/fips-mcp
```

### Other

```json
{
  "mcpServers": {
    "scoutwyze-max-fips-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@scoutwyze/fips-mcp"
      ]
    }
  }
}
```

## 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 76, +1)

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

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

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

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

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

### 2026-10-29 (score 73, +1)

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

### 2026-10-27 (score 72, +1)

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

### 2026-10-25 (score 71, +1)

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

### 2026-10-24 (score 70, 0)

- [security regression] CVE-2023-54404 affects this package: high

### 2026-10-23 (score 70, +1)

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

## MCP tools (4)

### `fips_list_products` (~47 tokens)

ScoutWyze FIPS: list covered products

Free. Lists the products and versions ScoutWyze FIPS covers (vendor, product, aliases, versions). Call this first to pick exact product and version names for fips_lookup.

### `fips_lookup` (~251 tokens)

ScoutWyze FIPS: is this version FIPS 140-3 validated?

Returns the FIPS 140-3 status of one product version from NIST CMVP data: ACTIVE, EXPIRING (sunset within 180 days), HISTORICAL, IN_QUEUE (NIST in-process or lab Implementation Under Test list), NOT_VALIDATED or UNVERIFIED, with certificate numbers, sunset dates, post-quantum algorithms and links to the NIST pages used (receipts). The answer is fail-closed: if NIST data is stale it says UNVERIFIED rather than ACTIVE. A few free lookups per day; after that, either set SCOUTWYZE_API_KEY (prepaid credits) or the tool returns an HTTP 402 with an x402 USDC-on-Base challenge that a wallet-capable agent must pay and retry with X-PAYMENT. This server cannot pay it. Unmapped products return 404 with the known list and are always free. Not legal or compliance advice.

Input parameters:

- `product` (string, required): Product name or alias, e.g. "FortiOS", "Windows 11", "RHEL"
- `version` (string): Version, e.g. "7.6", "24H2", "9"

### `fips_expiring` (~45 tokens)

ScoutWyze FIPS: certificates sunsetting soon

Free. Lists covered product versions whose FIPS certificates sunset within the given number of days (default 180).

Input parameters:

- `within` (integer): Days ahead, default 180

### `fips_batch` (~90 tokens)

ScoutWyze FIPS: check an inventory

Checks up to 500 product versions in one call and returns per-item status plus counts. Requires a prepaid SCOUTWYZE_API_KEY (billed per item; no free tier, no x402). Without a key or credits it returns HTTP 402 with signup and credit-pack details.

Input parameters:

- `items` (array, required): e.g. [{"product":"Windows 11","version":"24H2"}]

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/scoutwyze-max-fips-mcp/scoutwyze-fips-mcp#diagnostics

## Score history

- 2026-11-05: 76
- 2026-11-04: 76
- 2026-11-03: 75
- 2026-11-02: 75
- 2026-11-01: 74
- 2026-10-31: 74
- 2026-10-30: 73
- 2026-10-29: 73
- 2026-10-28: 72
- 2026-10-27: 72
- 2026-10-26: 71
- 2026-10-25: 71
- 2026-10-24: 70
- 2026-10-23: 70
- 2026-10-22: 69
- 2026-10-21: 69
- 2026-10-20: 66
- 2026-10-19: 66
- 2026-10-18: 66
- 2026-10-17: 66
- 2026-10-16: 66
- 2026-10-15: 66
- 2026-10-14: 66
- 2026-10-13: 33
- 2026-10-12: 33

## Common questions

### What is the ScoutWyze FIPS MCP server?

ScoutWyze FIPS is an MCP server listed in the public MCP registry as io.github.scoutwyze-max/fips-mcp. Is this product version FIPS 140-3 validated, in NIST's queue, or expiring? From NIST CMVP data. This page covers its npm package (@scoutwyze/fips-mcp).

### Is the ScoutWyze FIPS MCP server safe to use?

ScoutWyze FIPS scores 76 out of 100 on VerifyMCP. We recorded 6 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. 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 ScoutWyze FIPS MCP server expose?

ScoutWyze FIPS exposes 4 tools: fips_list_products, fips_lookup, fips_expiring, fips_batch. Their descriptions and schemas cost roughly 433 tokens of context every time the server is loaded.

### Is the ScoutWyze FIPS MCP server still maintained?

ScoutWyze FIPS 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 ScoutWyze FIPS MCP server under?

ScoutWyze FIPS 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 ScoutWyze FIPS MCP server?

VerifyMCP ran 16 checks on ScoutWyze FIPS, 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/@scoutwyze/fips-mcp
- Socket report: https://socket.dev/npm/package/@scoutwyze/fips-mcp
- Repository: https://github.com/scoutwyze-max/fips-mcp
- Website: https://scoutwyze-fips.fly.dev/
- Changelog RSS feed: https://verifymcp.io/servers/scoutwyze-max-fips-mcp/scoutwyze-fips-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/scoutwyze-max-fips-mcp/scoutwyze-fips-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/scoutwyze-max-fips-mcp/scoutwyze-fips-mcp.json
- HTML version of this page: https://verifymcp.io/servers/scoutwyze-max-fips-mcp/scoutwyze-fips-mcp