FIPS 140 certificate tracker — Claude Code MCP server for NIST FIPS data
FIPS 140 certificate tracker — an MCP server exposing NIST CMVP data: FIPS 140 certificates, the Modules in Process queue, CVE links. Useful when an agent needs to check the status of a cryptographic module.
MIT updated 2026-09-03
claude mcp add --transport http fips-cmvp https://fips.808bits.com/mcpWhat FIPS 140 certificate tracker does
The server runs over snapshots of NIST CMVP lists collected by a separate pipeline. It does not scrape NIST on demand, so responses reflect the latest refresh rather than the current minute. Each answer includes the data generation date, and GET / reports it too.
Six tools are available: fips_cert returns status and history for one certificate, fips_search finds a current validation by vendor or product, fips_vendor groups all certificates for a company across name spelling variants, fips_cve matches CVEs to modules, fips_in_process shows the Modules in Process queue, and fips_sunset lists what expires before a given date. NIST publishes the MIP queue only as a web page, so fips_in_process has no equivalent elsewhere.
The data has rough edges: 112 certificates lack module and vendor names entirely, returned as null. CVE associations are built from CPE strings and may not align with the certificate's actual code boundary, so an empty CVE result does not mean the module is clean. Cloning the repository will not give you a working server with data; the dataset is built separately and not checked in.
What it helps with
- Get status and level of a FIPS 140 certificate by number
- Find a current validation for a vendor or product
- Check whether a replacement module has been submitted to the MIP queue
- See which certificates are linked to a specific CVE
- Find out which vendors have certificates expiring before a date
Example prompts for the agent
- Check the status of FIPS 140 certificate 4567 using
fips_cert. - Find current FIPS 140 certificates for Cisco and show their levels.
- What does Thales have in the Modules in Process queue? Call
fips_in_process.
How to install FIPS 140 certificate tracker
Platform CLI: remote server
claude mcp add --transport http fips-cmvp https://fips.808bits.com/mcpPlatform CLI: remote server
codex mcp add fips-140-certificate-tracker --url https://fips.808bits.com/mcpConfig file
{
"mcpServers": {
"fips-140-certificate-tracker": {
"url": "https://fips.808bits.com/mcp"
}
}
}Config file
{
"servers": {
"fips-140-certificate-tracker": {
"type": "http",
"url": "https://fips.808bits.com/mcp"
}
}
}Platform CLI: remote server
gemini mcp add -t http fips-140-certificate-tracker https://fips.808bits.com/mcpStep by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about FIPS 140 certificate tracker
How do I install FIPS 140 certificate tracker in Claude Code?
Run claude mcp add --transport http fips-140-certificate-tracker https://fips.808bits.com/mcp. The server will appear in your MCP list and the agent can call its tools.
What does FIPS 140 certificate tracker do?
It exposes NIST CMVP data through six tools: certificate status, vendor search, all certificates for a company, CVE links, the Modules in Process queue, and expiring certificates.
Why does fips_in_process show milestones instead of a completion date?
NIST publishes the Modules in Process queue as a web page, without an API or completion forecast. Being on the queue means review has started, but a phase can last over a year.