FIPS 140 certificate tracker MCP server

• fips_certFree

  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_cveFree

  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 16 of the 1,183 active certificates carry any association at all, and historical ones are never scanned.

• fips_in_processFree

  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_searchFree

  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_sunsetFree

  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.

• fips_vendorFree

  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.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 644ms20/20
• Tool poisoning6 tool descriptions checked15/15
• Auth qualityopen endpoint, read-only tools10/15
• Maintenancelast push 17 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year; website matches verified namespace10/10

FIPS 140 certificate tracker: common questions

Is FIPS 140 certificate tracker MCP server safe?

Yes, by our scan: it is graded A (93/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, Claude Desktop or Cursor 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 17 days ago (2026-09-03). The latest release is v0.1.0.

Is FIPS 140 certificate tracker up?

100% of our last 6 checks got an answer. We check remote servers about four times a day.