Every NIST FIPS 140 certificate, plus the modules-in-process queue NIST publishes only as a page.
Scored across 6 tools
Each tool maps to a distinct query type: exact certificate lookup, name/vendor search, vendor rollup, sunset listing, in-process queue, and CVE association. Where fips_search and fips_vendor both touch vendors, their descriptions clearly differentiate general search from full spelling-normalized holdings.
All tool names share the fips_ prefix and use a consistent lowercase snake_case resource-noun convention (cert, cve, search, vendor, sunset, in_process). The one multiword name fips_in_process still follows the same pattern, so there is no mixing of conventions.
Six tools is a well-scoped size for a specialized FIPS 140 certificate tracker. Each tool addresses a distinct user need without redundant helpers or an overwhelming surface.
The tool set covers the core lifecycle and lookup needs for FIPS 140 tracking: certificate details, active validation search, vendor rollups, sunset dates, pending submissions, and CVE pointers. No obvious dead ends or missing essential operations for the stated read-only tracking purpose.
Look up one FIPS 140 cryptographic module validation by certificate number. Returns status (active, historical or revoked), overall level, sunset date, validation history, approved algorithms and tested configurations.
Inputs: number (required).
Which FIPS-validated modules are associated with a given CVE, or which CVEs are associated with a vendor's modules. Answers 'we have a validated module, is it caught up in this advisory'. The association is name-based against the product CPE, so read it as a pointer to check rather than a finding. An empty result means nothing matched by name, not that the module is unaffected: only 4 of the 712 active certificates carry any association at all, and historical ones are never scanned.
Inputs: cve, limit, vendor, min_cvss.
Search NIST's Modules in Process queue: submissions awaiting FIPS 140-3 validation, with the review phase each one is sitting in. Use this when a vendor claims a validation is 'coming' and you need to know whether it has actually been submitted, and how far along it is.
Inputs: limit, phase, query.
Search FIPS 140 validations by module name or vendor. Use this to answer whether a given product or vendor holds a current validation, and at what level. Results are ordered by status, then how well they match, then newest first, so the current validations lead.
Inputs: query (required), level, limit, status, +1 more.
List active FIPS validations by sunset date, the day each moves to NIST's historical list and stops being valid for new procurement. Answers 'what expires before date X' and 'which vendors are about to have nothing valid'. A certificate listed here may already have a 140-3 successor: check fips_search for the same module name before reporting a gap.
Inputs: limit, before, vendor, standard.
Everything one company holds, grouped across the spelling variants NIST filed it under. Cisco alone appears as three different strings. Returns a breakdown by status and standard plus the certificates themselves. Note this groups spellings of one registration, not corporate families: the nShield line sits under nCipher, Thales and Entrust separately, because the product changed owner. Groups large enough to have their own page on the tracker carry a tracker_url alongside the per-certificate ones.
Inputs: vendor (required), limit.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Live access to gematik Telematikinfrastruktur (TI) specs and certification requirements.
Machine-readable FCC pre-diligence corpus for multifamily broadband infrastructure scenarios.
QRNG-seeded random bytes, seeds, and ML-KEM-768 keys with signed provenance receipts.
Guidance for answering vendor security questionnaires. Every result carries the page it came from.
Add one secure layer between your agents and this server.
