FIPS 140 certificate tracker
com.808bits/fips-cmvpVersion 0.1.0Every NIST FIPS 140 certificate, plus the modules-in-process queue NIST publishes only as a page.
Status
Responds277 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 13:45 UTC
- Latency
- 277 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 21:12 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://fips.808bits.com/mcpResponds277 msNo sign-in
Claude Code
claude mcp add --transport http fips-cmvp https://fips.808bits.com/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: fips-cmvp
Remote MCP server URL: https://fips.808bits.com/mcpCursor
{
"mcpServers": {
"fips-cmvp": {
"url": "https://fips.808bits.com/mcp"
}
}
}VS Code
code --add-mcp '{"name":"fips-cmvp","type":"http","url":"https://fips.808bits.com/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
6 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
fips_certLook 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. | Not declared | Not declared | Not declared | Not declared |
fips_cveWhich 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. | Not declared | Not declared | Not declared | Not declared |
fips_in_processSearch 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. | Not declared | Not declared | Not declared | Not declared |
fips_searchSearch 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. | Not declared | Not declared | Not declared | Not declared |
fips_sunsetList 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. | Not declared | Not declared | Not declared | Not declared |
fips_vendorEverything 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. | Not declared | Not declared | Not declared | Not declared |
Details
- Registry status
- Active
- Published
- Sep 3, 2026
- Updated
- Sep 3, 2026
- Categories (suggested)
- SecuritySuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared