ScoutWyze FIPS MCP
This MCP server queries the ScoutWyze FIPS status API to determine if specific product versions are FIPS 140-3 validated, in NIST's queue, or expiring. It provides statuses like ACTIVE, EXPIRING, HISTORICAL, IN_QUEUE, NOT_VALIDATED, and UNVERIFIED, along with certificate links and sunset dates for various operating systems and network devices.
Package and access
Local package with source-attributed installation metadata. Koskamo does not execute packages during review.
What you can do with it
- Check FIPS 140-3 validation status for a specific product version
- Identify certificates expiring within a specified number of days
- Batch check FIPS status for up to 500 product versions
- List all covered products and versions supported by the API
Source and maintenance
- Last repository push
- Maintenance checked
Packages and installation
Source-provided package data. Koskamo has not executed or live-probed this package.
@scoutwyze/fips-mcp 0.1.0
{
"version": "0.1.0",
"transport": "stdio",
"identifier": "@scoutwyze/fips-mcp",
"registryType": "npm",
"registryBaseUrl": "https://registry.npmjs.org",
"environmentVariables": [
{
"name": "SCOUTWYZE_API_KEY",
"description": "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."
},
{
"name": "SCOUTWYZE_FIPS_BASE_URL",
"description": "Overrides the API base URL (https://scoutwyze-fips.fly.dev). For local development only."
}
]
}Tools
Reported by the attributed source; not independently observed by Koskamo.
Maintenance history
Public check and source-refresh events. Editorial and ownership records remain private.
- · repository · passed · metadata changed · updated
- · backfill · recorded · Pre-expansion baseline; unobserved rich metadata remains unknown
Connect from your client
Each snippet configures the same source-provided package; replace placeholders before use.
Cursor
{
"mcpServers": {
"scoutwyze-fips-mcp": {
"command": "npx",
"args": [
"-y",
"@scoutwyze/fips-mcp@0.1.0"
],
"env": {
"SCOUTWYZE_API_KEY": "<YOUR_SCOUTWYZE_API_KEY>",
"SCOUTWYZE_FIPS_BASE_URL": "<YOUR_SCOUTWYZE_FIPS_BASE_URL>"
}
}
}
}Cline
{
"mcpServers": {
"scoutwyze-fips-mcp": {
"command": "npx",
"args": [
"-y",
"@scoutwyze/fips-mcp@0.1.0"
],
"env": {
"SCOUTWYZE_API_KEY": "<YOUR_SCOUTWYZE_API_KEY>",
"SCOUTWYZE_FIPS_BASE_URL": "<YOUR_SCOUTWYZE_FIPS_BASE_URL>"
}
}
}
}VS Code
{
"servers": {
"scoutwyze-fips-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@scoutwyze/fips-mcp@0.1.0"
],
"env": {
"SCOUTWYZE_API_KEY": "<YOUR_SCOUTWYZE_API_KEY>",
"SCOUTWYZE_FIPS_BASE_URL": "<YOUR_SCOUTWYZE_FIPS_BASE_URL>"
}
}
}
}Claude Desktop
{
"mcpServers": {
"scoutwyze-fips-mcp": {
"command": "npx",
"args": [
"-y",
"@scoutwyze/fips-mcp@0.1.0"
],
"env": {
"SCOUTWYZE_API_KEY": "<YOUR_SCOUTWYZE_API_KEY>",
"SCOUTWYZE_FIPS_BASE_URL": "<YOUR_SCOUTWYZE_FIPS_BASE_URL>"
}
}
}
}Let your agent find its tools
Find servers like ScoutWyze FIPS MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.