# FIPS 140 certificate tracker

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

- name: com.808bits/fips-cmvp
- version: 0.1.0
- connection class: unknown (unknown)
- trust: 73/100
- quality: 83/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.808bits%2Ffips-cmvp
- tools: https://api.protogrid.dev/v1/servers/com.808bits%2Ffips-cmvp/tools

**Not classified yet.** The remote endpoints have not been probed successfully, or the listing has nothing to connect to.

## Connection (mcpServers)

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


## Trust

- hygiene: 100
- liveness: 19
- freshness: 85
- provenance: 100
- drivers: +repository +namespace-matches-repo +dns-namespace +website -unreachable(2 failures) ~updated-46d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 83/100 (good)

### protocol: 88 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- warn `protocol.list_ttl`: tools/list declares ttlMs 0, so clients re-fetch it on every use

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 71 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- fail `tools.annotations`: no tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: fips_search (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); fips_vendor (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); fips_cve (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
- pass `tools.token_cost`: about 1,049 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: 1 tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 6, about 1,049 tokens to load them all
- tool set hash: 7390faff69485bd7c14c920203b8e8aa
- tools last changed: 2026-09-25T14:20:15.562Z
- badge: [![protogrid quality](https://protogrid.dev/badge/com.808bits/fips-cmvp.svg)](https://protogrid.dev/servers/com.808bits/fips-cmvp)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-09-25 `fips_cve` changed (description)
  - before: 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.
  - after: 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.

Full history: https://api.protogrid.dev/v1/servers/com.808bits%2Ffips-cmvp/changes

## Remotes

- https://fips.808bits.com/mcp (streamable-http, auth none, reachable false, uptime30d 0.9826087)

## Packages

_none_

## Tools (6)

- `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.