FIPS 140 certificate tracker MCP Server

by 808bits Your server? Claim it

answering

FIPS 140 certificate tracker is answering right now. Last checked 4 min ago. It exposes 6 tools. Last commit 4 Sep 2026.

Every NIST FIPS 140 certificate, plus the modules-in-process queue NIST publishes only as a page.

Uptime history 69 days of history · worst day 91%

69 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

220 ms

Response time

average over 24h

Stars

last commit 4 Sep 2026

What changed 5

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 9 September 2026. No other catalogue keeps this.

25 Sep a tool description was rewritten fips_cve

9 Sep 3 tool descriptions were rewritten fips_cve, fips_search, fips_vendor

9 Sep a tool changed the parameters it asks for fips_search

Nothing serious here today

Today is the operative word: we check FIPS 140 certificate tracker every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add fips-cmvp --transport http https://fips.808bits.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://fips.808bits.com/mcp

~/.codex/config.toml

[mcp_servers.fips-cmvp]
url = "https://fips.808bits.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "fips-cmvp": {
      "url": "https://fips.808bits.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "fips-cmvp": {
      "type": "http",
      "url": "https://fips.808bits.com/mcp"
    }
  }
}

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

fips

fips_cert

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_cve

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

fips_in_process

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_search

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_sunset

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_vendor

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.

Endpoints

URL	Transport	State	Latency	Checked
https://fips.808bits.com/mcp	streamable-http	answering	188 ms	4 min ago

Alternatives to FIPS 140 certificate tracker

same job, measured the same way

Eclipse Crosslist MCP

by cyan-eclipse-technologies-llc

Publish once, tracked everywhere: registry-native facets plus a mandate-bound listing ledger.

local only

ScoutWyze FIPS

by scoutwyze-max

Is this product version FIPS 140-3 validated, in NIST's queue, or expiring? From NIST CMVP data.

49 installs/wk local only

Domain and Certificate Tracker MCP

by servosity

Every client's domains and certificates in one inventory: what expires, unlocks or changes.

local only

Morfee

by furo-solutions

Turn an HTML template plus JSON into a finished PDF: a quote, invoice, work order or certificate.

answering

Goproxy MCP

by mrfentmen

Go Proxy: every published version of a Go module, straight from proxy.golang.org - keyless.

332 installs/wk local only

DSH Plugin Certification

by perrylink

Read-only MCP server exposing the dsh-plugin-certification registry for DeepSeek Harness plugins.

729 installs/wk local only

Mandate

by mandatefi

Trade on Base through the Mandate module: every batch is checked onchain against the owner's rules

114 installs/wk local only

MCPFax Web Extract

by mcpscores

Read any web page as clean text for a prompt, or list every link on it.

4 tools answering

FIPS 140 certificate tracker — questions

Answers built from our own checks of this server.

What can FIPS 140 certificate tracker do?

It exposes 6 tools, read directly from the server on our last check. Among them: fips_cert, fips_cve, fips_in_process, fips_search, fips_sunset, fips_vendor. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is FIPS 140 certificate tracker working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 220 ms. The bar chart above shows every period we have measured.

How do I connect FIPS 140 certificate tracker?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does FIPS 140 certificate tracker need an API key?

No. FIPS 140 certificate tracker completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is FIPS 140 certificate tracker?

It answers our handshake in 220 ms on average, which is faster than 61% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is FIPS 140 certificate tracker open source?

The code is open source: it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at fips.808bits.com, which runs on its operator's own terms.