scoutwyze-fips-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SCOUTWYZE_API_KEY | No | Prepaid key for the ScoutWyze FIPS API | |
| SCOUTWYZE_FIPS_BASE_URL | No | Base URL for the ScoutWyze FIPS API (local development only) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fips_list_productsA | 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_lookupA | 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. |
| fips_expiringA | Free. Lists covered product versions whose FIPS certificates sunset within the given number of days (default 180). |
| fips_batchA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct role: enumerate the catalog (fips_list_products), check one version (fips_lookup), filter by sunset window (fips_expiring), and bulk-check many versions (fips_batch). The only mild overlap is fips_lookup vs fips_batch, but the descriptions explicitly separate single vs up-to-500 and free-tier vs prepaid-key paths.
All four tools share a fips_ prefix and snake_case with action-oriented suffixes (list_products, lookup, expiring, batch). Minor deviation in that three are verb/noun-ish while fips_expiring and fips_batch are adjective/noun forms, but overall predictable.
Four tools is a reasonable fit for a narrow FIPS-status lookup service: catalog discovery, single lookup, expiring filter, and bulk check. It is on the lean side but nothing feels redundant or missing at the workflow level.
The surface covers the core lifecycle: discover products/versions, look up status with receipts, monitor sunsets, and batch-check at scale. Gaps are minor, e.g. no dedicated tool to retrieve full certificate detail or search by certificate number, but agents can work around these via fips_lookup.