ScoutWyze FIPS

io.github.scoutwyze-maxPublished by GitHub account scoutwyze-maxv0.1.0Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlySecurity & Monitoring Business & Commerce

Server details

Identifier: io.github.scoutwyze-max/fips-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Oct 12, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account scoutwyze-max for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.scoutwyze-max%2Ffips-mcp.svg)](https://sourceweft.com/mcp/io.github.scoutwyze-max%2Ffips-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Looks up whether a product version is FIPS 140-3 validated, in NIST's queue, or expiring, using NIST CMVP data.

What you can do: List covered products and versions
Look up one product version's status with certificates, sunset dates and post-quantum algorithms
Find covered versions whose certificates sunset within a given number of days
Check up to 500 versions in a single batch call
When to use it: Useful when checking FIPS 140-3 validation status for a specific product version, tracking certificate sunset dates, or screening many versions at once during compliance or procurement review.
Requirements: Runs locally via npx (Node.js). Optional SCOUTWYZE_API_KEY for prepaid credits; without it, lookups are limited to a few free per day. SCOUTWYZE_FIPS_BASE_URL is for local development only. Network access to the ScoutWyze API is required.

Before you install

Lookups beyond the free daily allowance require prepaid credits or an x402 payment challenge (USDC on Base) that a wallet-capable agent may pay; the server itself holds no private key. Batch calls consume prepaid credits. Unmapped products are logged as requests. Results are not legal or compliance advice and should be confirmed with an assessor.

Installation

In SourceWeft

Open ScoutWyze FIPS in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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

json

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

{  "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

Tool	What it does	Cost
`fips_list_products`	Covered products and versions	Free
`fips_lookup`	Status of one product version, with certificates, sunset dates, post-quantum algorithms and receipts	A few free per day, then credits or x402
`fips_expiring`	Covered versions whose certificates sunset within N days	Free
`fips_batch`	Up to 500 versions in one call	Prepaid 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.

Source: README.md at commit 4ad94ce

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.1.0LatestOct 12, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts