FIPS 140 certificate tracker MCP server
online · 100% uptimecom.808bits/fips-cmvp·v0.1.0Every NIST FIPS 140 certificate, plus the modules-in-process queue NIST publishes only as a page.
0 stars
Reviews
Write oneNobody has reviewed FIPS 140 certificate tracker yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
FIPS 140 certificate tracker tools (6)
write = sends, deletes, buys or postsfips_certFreeLook 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_cveFreeWhich 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_in_processFreeSearch 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_searchFreeSearch 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_sunsetFreeList 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.
fips_vendorFreeEverything 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.
Public scan report
scanner v0.1.10 · 2026-10-16 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 602ms20/20
- Tool poisoning6 tool descriptions checked15/15
- Auth qualityopen endpoint, read-only tools10/15
- Maintenancelast push 43 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year; website matches verified namespace10/10
How FIPS 140 certificate tracker compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 89/100
- higher than 80% of 48,243 servers
- Tools
- 6
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 203 ms
- faster than 66% of 30,027 servers
What its tools let an agent do: 6 read
Install FIPS 140 certificate tracker in Claude Code, Cursor or VS Code
claude mcp add --transport http fips-cmvp https://fips.808bits.com/mcp
What the publisher says
From the FIPS 140 certificate tracker repository's README, as published. We do not edit it. Read it on GitHub
fips-mcp
An MCP server over the NIST CMVP data behind 808bits.com/fips: every FIPS 140 cryptographic module validation, plus the queue of submissions still awaiting one.
Read-only, no authentication.
https://fips.808bits.com/mcpclaude mcp add --transport http fips https://fips.808bits.com/mcpThe endpoint speaks POST, as the transport requires. Opening either the hostname or the endpoint in a browser redirects to the tracker. A client's GET /mcp still gets 405, which is what a stateless server owes a request to open an SSE stream, and GET / and GET /health return a JSON descriptor with the data generation dates for anything checking liveness.
Tools
fipsinprocess is the one with no equivalent elsewhere. NIST publishes the Modules in Process list as a web page, not as an API, and "it is on MIP" is the milestone people reach for when a validation has lapsed and the replacement has not landed.
Reading the data without getting it wrong
A submission in the queue is a milestone, not a date. 181 modules are in process and the phase dates run back more than a year, so plenty have sat in one phase for longer than that. "It is on MIP" says review started.
An absence from the queue can mean the successor already landed. Ribbon's SBC 5400 sunsets on 2026-09-06 and has held a 140-3 certificate since 2025. Check fips_search for the module name before reporting a gap.
Vendor names are free text at NIST. Cisco holds certificates under three spellings, Thales under two. vendorkey groups the variants of one registration and vendordisplay is the spelling NIST used most often. Neither merges corporate families: the nShield line ran nCipher Corporation to Thales to Entrust, so folding those together would credit certificates to a company that sold the product years ago.
112 certificates have no module name or vendor, because NIST published none. Those come back as null with a note rather than as empty strings.
CVE associations are name-based, not boundary-based. They come from matching the vendor and product CPE, so a listed CVE may sit in code the certificate never covered, and a real flaw inside the boundary may not appear at all. 183 associations across 16 certificates.
An empty CVE result is not a clean bill of health, and this is the more misleading direction. Only 16 of 5,504 certificates carry any association, the match does not follow dependencies, and it needs a stable CPE string, so hardware modules come back empty largely regardless of their advisory history. fips_cve for CVE-2014-0160 returns nothing. Every empty result says so, and reports how many certificates carry any association at all, so the number is in front of the caller rather than in this file.
Sunset dates are not uniform. Most active 140-2 certificates move to the historical list on 2026-09-21, but six carry earlier dates of their own.
Where the data comes from
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
FIPS 140 certificate tracker: common questions
- Is FIPS 140 certificate tracker MCP server safe?
- Yes, by our scan: it is graded A (89/100). Read the FIPS 140 certificate tracker safety report
- How do I install FIPS 140 certificate tracker?
- It runs remotely at fips.808bits.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does FIPS 140 certificate tracker need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is FIPS 140 certificate tracker maintained?
- The last commit was 63 days ago (2026-09-03). The latest release is v0.1.0.
- Is FIPS 140 certificate tracker up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does FIPS 140 certificate tracker compare with other MCP servers?
- safety score 89/100 (higher than 80% of 48,243 servers); tools 6 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.