Categories › Security › Code & dependency scanning
Every NIST FIPS 140 certificate, plus the modules-in-process queue NIST publishes only as a page.
Remote server: your requests and data go to fips.808bits.com. Claude Code: claude mcp add --transport http fips-140-certificate-tracker https://fips.808bits.com/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
fips_cert — Look up one FIPS 140 cryptographic module validation by certificate number. Returns status (active, historical or revoked), overall level, sfips_search — Search FIPS 140 validations by module name or vendor. Use this to answer whether a given product or vendor holds a current validation, and afips_in_process — Search NIST's Modules in Process queue: submissions awaiting FIPS 140-3 validation, with the review phase each one is sitting in. Use this wfips_vendor — Everything one company holds, grouped across the spelling variants NIST filed it under. Cisco alone appears as three different strings. Retufips_cve — Which FIPS-validated modules are associated with a given CVE, or which CVEs are associated with a vendor's modules. Answers 'we have a validfips_sunset — List active FIPS validations by sunset date, the day each moves to NIST's historical list and stops being valid for new procurement. AnswersNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.