FIPS 140 certificate tracker MCP server
Commit Sep 3, 2026Lets an AI client query NIST FIPS 140 cryptographic module validations, vendor histories, and the modules-in-process queue.
Also known as 808bits/fips-mcp, fips-mcp
- Stars
- 0
- Tools
- 6
- Downloads, 30 days
- —
- Latest version
- 0.1.0
- Last commit
- Sep 3, 2026
- License
- MIT
What is FIPS 140 certificate tracker MCP?
FIPS 140 certificate tracker lets an AI client query NIST FIPS 140 cryptographic module validations, vendor histories, and the modules-in-process queue. It exposes 6 tools, such as fips_cert, fips_search, fips_vendor.
Summary generated from the project's README
About FIPS 140 certificate tracker MCP server
Querying NIST FIPS 140 cryptographic module validations and vendor histories from inside an AI client is what this server enables. It provides access to the NIST CMVP data, including validated modules, historical records, and the modules-in-process queue. Developers and security researchers can use it to track certificate statuses, sunset dates, and vendor-specific validation levels without needing authentication or API keys.
The server operates as a read-only remote service via an SSE stream. It uses specific tools like fips_cert to retrieve validation history for a single certificate number and fips_search to check if a product holds a current validation. It also includes fips_in_process, which tracks the submission phase for replacements, a feature not available in other standard interfaces. Users can also investigate security associations using fips_cve to see which validated modules are linked to specific vulnerabilities.
Because the data is derived from snapshots of NIST lists rather than live scraping, every response includes a generation date to ensure users understand the freshness of the information. The server handles complex vendor naming by grouping spelling variants used by NIST, ensuring that searches for companies like Cisco or Thales return complete results across different registration styles.
What you can do with it
- 1Track cryptographic module expirationCheck which certificates are approaching their sunset dates to prepare for hardware or software transitions.
- 2Monitor replacement module progressDetermine if a vendor has submitted a replacement module for a lapsed validation by checking its current phase in the queue.
- 3Verify vendor validation statusSearch for all current cryptographic validations held by a specific company across various name spellings.
- 4Audit CVE associationsIdentify which validated modules are associated with a specific CVE through CPE matching.
Written from the project's README. Every use case is checked against a quote from it.
How to install FIPS 140 certificate tracker MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall FIPS 140 certificate tracker MCP in Claude Code
$ claude mcp add --transport http fips-mcp https://fips.808bits.com/mcpInstall FIPS 140 certificate tracker MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"fips-mcp": {
"url": "https://fips.808bits.com/mcp"
}
}
}Install FIPS 140 certificate tracker MCP in VS Code
.vscode/mcp.json
{
"servers": {
"fips-mcp": {
"type": "http",
"url": "https://fips.808bits.com/mcp"
}
}
}Install FIPS 140 certificate tracker MCP in VS Code CLI
$ code --add-mcp '{"name":"fips-mcp","type":"http","url":"https://fips.808bits.com/mcp"}'Install FIPS 140 certificate tracker MCP in Codex
$ codex mcp add fips-mcp --url https://fips.808bits.com/mcpInstall FIPS 140 certificate tracker MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.fips-mcp] url = "https://fips.808bits.com/mcp"
Install FIPS 140 certificate tracker MCP in Gemini CLI
$ gemini mcp add -s user --transport http fips-mcp https://fips.808bits.com/mcpInstall FIPS 140 certificate tracker MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"fips-mcp": {
"url": "https://fips.808bits.com/mcp",
"type": "http"
}
}
}FIPS 140 certificate tracker MCP tools 6
Detected from the READMEfips_certfips_searchfips_vendorfips_cvefips_in_processfips_sunset
| fips_cert | — | |
| fips_search | — | |
| fips_vendor | — | |
| fips_cve | — | |
| fips_in_process | — | |
| fips_sunset | — |
Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachable808bits/fips-mcp is public and reachablegithub.com/808bits/fips-mcp ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-09-03github.com/808bits/fips-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model6 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeinitialize answered with protocol 2025-06-18 in 243 msPass
README
View on GitHubfips-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/mcp
claude mcp add --transport http fips https://fips.808bits.com/mcp
The 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
| Tool | Answers |
|---|---|
fips_cert |
Status, level, sunset date and validation history for one certificate number. |
fips_search |
Does this vendor or product hold a current validation, and at what level. |
fips_vendor |
Everything one company holds, across the spelling variants NIST filed it under. |
fips_cve |
Which validated modules are associated with a CVE, and which CVEs touch a vendor's. |
fips_in_process |
Has the vendor's replacement actually been submitted, and what phase is it in. |
fips_sunset |
What expires before a given date, and which vendors are about to have nothing valid. |
fips_in_process 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. vendor_key groups the variants of one
registration and vendor_display 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
Everything is derived from NIST's published CMVP lists: the validated modules,
the historical and revoked lists, and the Modules in Process queue. The server
does not scrape NIST on demand. A separate pipeline snapshots the lists, diffs
them against the previous snapshot and loads the result, so answers reflect the
last refresh rather than this minute. Every response carries the generation
date, and GET / reports it too.
This repository holds the server. The dataset it serves is built elsewhere and is not checked in, so a clone will typecheck and deploy but will not have rows to answer with.
Licence
MIT. The certificate data itself is published by NIST and is not covered by it.
FIPS 140 certificate tracker MCP questions
How do I add FIPS 140 certificate tracker MCP to Claude Code?
Run claude mcp add --transport http fips-mcp https://fips.808bits.com/mcp in your terminal. Add --scope user to make it available in every project.
How do I add FIPS 140 certificate tracker MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does FIPS 140 certificate tracker MCP provide?
It exposes 6 tools, including fips_cert, fips_search, fips_vendor, fips_cve, fips_in_process.
Does this server provide information on modules currently in the NIST queue?
Yes, it includes the queue of submissions still awaiting validation, which is not typically available via an API.
How accurate are the CVE associations in the tool?
CVE associations are name-based using vendor and product CPE, meaning a listed CVE might be in code not covered by the certificate, or a real flaw might not appear.
Is the data real-time?
No, the server uses a snapshot pipeline rather than scraping NIST on demand, so answers reflect the last refresh date.
How are different vendor name spellings handled?
The server uses vendor_key to group spelling variants used by NIST and vendor_display for the most common spelling.