# FIPS 140 certificate tracker (remote · fips.808bits.com)

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

- Trust score: 72/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `fips.808bits.com`: 72/100 (this document), [markdown](https://verifymcp.io/servers/com-808bits-fips-cmvp/fips.md), [page](https://verifymcp.io/servers/com-808bits-fips-cmvp/fips)

## Channel facts

- Endpoint: `https://fips.808bits.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-28.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 966 tokens (~161/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 79/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 37% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the FIPS 140 certificate tracker MCP server?

FIPS 140 certificate tracker is a hosted endpoint at https://fips.808bits.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-808bits-fips-cmvp": {
      "type": "remote",
      "url": "https://fips.808bits.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-808bits-fips-cmvp --url 'https://fips.808bits.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-808bits-fips-cmvp:
    url: "https://fips.808bits.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-808bits-fips-cmvp": {
      "Transport": "http",
      "Url": "https://fips.808bits.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-808bits-fips-cmvp -t streamable-http -u 'https://fips.808bits.com/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 72, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-26 (score 71, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “fips_cve” rewrote its description, which is the text the model reads

### 2026-09-25 (score 70, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-21 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (6)

### `fips_cert` (~55 tokens)

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.

Input parameters:

- `number` (integer, required)

### `fips_search` (~124 tokens)

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.

Input parameters:

- `level` (integer)
- `limit` (integer)
- `query` (string, required): Module name or vendor. Several words all have to match, in any order and across either field, so "openssl provider" works.
- `standard` (string)
- `status` (string)

### `fips_in_process` (~108 tokens)

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.

Input parameters:

- `limit` (integer)
- `phase` (string): e.g. Review, Finalization, Coordination
- `query` (string): Substring of the module name or vendor

### `fips_vendor` (~122 tokens)

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.

Input parameters:

- `limit` (integer)
- `vendor` (string, required): Vendor name or part of one

### `fips_cve` (~166 tokens)

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.

Input parameters:

- `cve` (string): CVE id, e.g. CVE-2023-4807
- `limit` (integer)
- `min_cvss` (number)
- `vendor` (string): Vendor name or part of one

### `fips_sunset` (~131 tokens)

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.

Input parameters:

- `before` (string): ISO date, exclusive: before=2026-09-21 excludes the 21st itself
- `limit` (integer)
- `standard` (string)
- `vendor` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-808bits-fips-cmvp/fips#diagnostics

## Score history

- 2026-09-28: 72
- 2026-09-27: 71
- 2026-09-26: 71
- 2026-09-25: 70
- 2026-09-24: 70
- 2026-09-23: 69
- 2026-09-22: 69
- 2026-09-21: 69
- 2026-09-20: 68
- 2026-09-19: 68
- 2026-09-18: 67
- 2026-09-17: 67
- 2026-09-16: 66
- 2026-09-15: 66
- 2026-09-14: 65
- 2026-09-13: 65
- 2026-09-12: 64
- 2026-09-11: 64
- 2026-09-10: 63
- 2026-09-09: 63
- 2026-09-08: 62
- 2026-09-07: 62
- 2026-09-06: 61
- 2026-09-05: 61
- 2026-09-04: 60

## Common questions

### What is the FIPS 140 certificate tracker MCP server?

FIPS 140 certificate tracker is an MCP server listed in the public MCP registry as com.808bits/fips-cmvp. Every NIST FIPS 140 certificate, plus the modules-in-process queue NIST publishes only as a page. This page covers its hosted endpoint (https://fips.808bits.com/mcp).

### Is the FIPS 140 certificate tracker MCP server safe to use?

FIPS 140 certificate tracker scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the FIPS 140 certificate tracker MCP server expose?

FIPS 140 certificate tracker exposes 6 tools: fips_cert, fips_search, fips_in_process, fips_vendor, fips_cve, fips_sunset. Their descriptions and schemas cost roughly 706 tokens of context every time the server is loaded.

### Does the FIPS 140 certificate tracker MCP server require authentication?

No. We connected to FIPS 140 certificate tracker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the FIPS 140 certificate tracker MCP server still maintained?

FIPS 140 certificate tracker is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://fips.808bits.com/mcp
- Repository: https://github.com/808bits/fips-mcp
- Website: https://808bits.com/fips/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/com-808bits-fips-cmvp/fips.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-808bits-fips-cmvp/fips.json
- HTML version of this page: https://verifymcp.io/servers/com-808bits-fips-cmvp/fips