FIPS 140 certificate tracker
by 808bits.com · remote · no sign-in to list tools · v0.1.0 · published by com.808bits
Every NIST FIPS 140 certificate, plus the modules-in-process queue NIST publishes only as a page.
6 tools: 3 change things and 3 only read.
Scanned Oct 21, 2026
- Deletes or cancels0Claude Code: deny
- Can't be undone0Claude Code: ask
- Changes things3Claude Code: ask: see these tools
- Only reads3Claude Code: allow: see these tools
No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http fips-cmvp https://fips.808bits.com/mcpTools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
6 tools
Changes things 3Claude Code: ask
fips_certLook up one FIPS 140 cryptographic module validation by certificate number.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
fips_cveWhich FIPS-validated modules are associated with a given CVE, or which CVEs are associated with a vendor's modules.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
fips_vendorEverything one company holds, grouped across the spelling variants NIST filed it under.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Only reads 3Claude Code: allow
fips_in_processSearch NIST's Modules in Process queue: submissions awaiting FIPS 140-3 validation, with the review phase each one is sitting in.No findings
Why it is in this group
- The description's first verb is "search": a word for reading.
Description, as the server wrote it 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.
fips_searchSearch FIPS 140 validations by module name or vendor.No findings
Why it is in this group
- The name "fips_search" says "search": a word for reading.
Description, as the server wrote it 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.
fips_sunsetList active FIPS validations by sunset date, the day each moves to NIST's historical list and stops being valid for new procurement.No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it 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.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http fips-cmvp https://fips.808bits.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__fips-cmvp__fips_search",
"mcp__fips-cmvp__fips_in_process",
"mcp__fips-cmvp__fips_sunset"
],
"ask": [
"mcp__fips-cmvp__fips_cert",
"mcp__fips-cmvp__fips_vendor",
"mcp__fips-cmvp__fips_cve"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as fips-cmvp. Review it before you use it.