Back to Browse

Fips MCP Server

Developer ToolsModerate7.6MCP RegistryLocal
Free

Server data from the Official MCP Registry

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

About

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

Security Report

7.6
Moderate7.6Low Risk

This is a small, well-scoped MCP server that relays read-only FIPS 140-3 status queries to a single documented API, with an optional API key read from an environment variable and no shell execution, file access, or hardcoded secrets. The only notable points are that the API key is sent to a remote host configurable via SCOUTWYZE_FIPS_BASE_URL and that the server forwards user-supplied product strings to an external API, both of which are expected for this design and low risk. Permissions match the stated purpose. Supply chain analysis found 1 known vulnerability in dependencies (0 critical, 1 high severity). Package verification found 1 issue.

4 files analyzed · 6 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

Optional prepaid API key (POST /v1/signup, then buy credits). Without it, fips_lookup gives a few free lookups per day, then returns an x402 payment challenge.Required

Environment variable: SCOUTWYZE_API_KEY

Overrides the API base URL (https://scoutwyze-fips.fly.dev). For local development only.Optional

Environment variable: SCOUTWYZE_FIPS_BASE_URL

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-scoutwyze-max-fips-mcp": {
      "env": {
        "SCOUTWYZE_API_KEY": "your-scoutwyze-api-key-here",
        "SCOUTWYZE_FIPS_BASE_URL": "your-scoutwyze-fips-base-url-here"
      },
      "args": [
        "-y",
        "@scoutwyze/fips-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

ScoutWyze FIPS MCP server

Is this product version FIPS 140-3 validated, in NIST's queue, or expiring? An MCP server for the ScoutWyze FIPS status API. Answers come from NIST CMVP lists (active certificates, Modules In Process, Implementation Under Test), with links to the NIST pages used.

Covers Windows 11 / Server, macOS / iOS, FortiOS, PAN-OS, Panorama, Cisco FTD, RHEL, Ubuntu, Samsung Android, Aruba, SonicWall, F5, Juniper, VMware ESXi and Okta. Unmapped products are logged as requests.

Install

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

Optional env: SCOUTWYZE_API_KEY (prepaid key), SCOUTWYZE_FIPS_BASE_URL (local development only).

Tools

ToolWhat it doesCost
fips_list_productsCovered products and versionsFree
fips_lookupStatus of one product version, with certificates, sunset dates, post-quantum algorithms and receiptsA few free per day, then credits or x402
fips_expiringCovered versions whose certificates sunset within N daysFree
fips_batchUp to 500 versions in one callPrepaid credits

Statuses: ACTIVE, EXPIRING (sunset within 180 days), HISTORICAL, IN_QUEUE, NOT_VALIDATED, UNVERIFIED. If NIST data is stale, the answer is UNVERIFIED, never ACTIVE.

Payments

This server never holds a private key or pays anything. A 402 response is returned as tool content; a wallet-capable calling agent can pay the x402 challenge (USDC on Base) and retry with X-PAYMENT.

Not legal or compliance advice. Confirm with your assessor.

Reviews

No reviews yet

Be the first to review this server!