scoutwyze-fips-mcp
Related Servers
Alternatives to scoutwyze-fips-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables querying NIST CMVP data for FIPS 140 certificate status, validation history, vendor holdings, CVE associations, Modules in Process phases, and upcoming sunset dates through read-only MCP tools.MIT
- AlicenseAqualityAmaintenanceChecks public IPs, domains, CVE IDs and software versions for confirmed vulnerabilities and exposure, using NVD version ranges, CISA KEV, EPSS, distro backports and published exploits. All API keys are optional.19420 PyPI1MIT
- AlicenseNot gradedqualityAmaintenanceSearch and audit CVEs by keyword, severity, CWE, CISA KEV status, and CPE via the NIST National Vulnerability Database.705 npm1Apache 2.0
- AlicenseNot gradedqualityAmaintenanceProvides keyless, read-only access to CISA KEV, SSVC, and full ICS advisory corpus, letting users check CVE statuses, compute BOD 26-04 remediation timelines, and search advisories by vendor, product, CVE, CVSS, or sector.351 npm1Apache 2.0
- AlicenseBqualityDmaintenanceDefense-grade cryptographic compliance and analysis tools for MCP, including FIPS 140-3 validation, CNSA 2.0 analysis, post-quantum readiness assessment, and classical cipher utilities.182MIT
- AlicenseNot gradedqualityDmaintenanceEnables searching the NIST NVD for CVEs, retrieving full CVE details, checking software for known vulnerabilities, and searching the CPE database.1MIT
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.