mcpField
S
ScoutWyze FIPS

ScoutWyze FIPS

Local
scoutwyze-fips.fly.devSecurity0Updated 3w ago
RepositoryVisit website

About ScoutWyze FIPS

ScoutWyze FIPS is an MCP server for checking product-version FIPS 140-3 status using NIST CMVP lists, with links to source pages. It serves teams reviewing validation, certificate sunsets, and queue status; stale data is marked unverified rather than active.

Key features

  1. 01Check FIPS status by product version
  2. 02List covered products and versions
  3. 03Find certificates nearing sunset
  4. 04Batch-check up to 500 versions
  5. 05Link to NIST source pages

Use cases

  1. 01Verify a software or device version's FIPS status
  2. 02Find versions with certificates nearing sunset
  3. 03Check multiple product versions in one batch

MCP support

It exposes tools for product listings, version lookups, sunset checks, and batch queries to MCP clients. Paid requests return an x402 challenge for the calling agent to handle; the server holds no private key.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "scoutwyze-max-fips": {
      "command": "npx",
      "args": [
        "-y",
        "@scoutwyze/fips-mcp"
      ],
      "env": {
        "SCOUTWYZE_API_KEY": "<SCOUTWYZE_API_KEY>",
        "SCOUTWYZE_FIPS_BASE_URL": "<SCOUTWYZE_FIPS_BASE_URL>"
      }
    }
  }
}
Run commandnpx -y @scoutwyze/fips-mcp
Environment variables to set
SCOUTWYZE_API_KEYSecretOptional 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.
SCOUTWYZE_FIPS_BASE_URLOverrides the API base URL (https://scoutwyze-fips.fly.dev). For local development only.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@scoutwyze/fips-mcp0.1.0

Tools

4

Saved tool list · updated 2w ago

This tool takes no parameters.

Details

From the project 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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.