FIPS 140 certificate tracker
REMOTE · FIPS.808BITS.COM · SCANNED SEP 28
Every NIST FIPS 140 certificate, plus the modules-in-process queue NIST publishes only as a page.
Available components
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage79
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 37% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
remote · fips.808bits.com
claude mcp add --transport http com-808bits-fips-cmvp 'https://fips.808bits.com/mcp'
{
"mcpServers": {
"com-808bits-fips-cmvp": {
"url": "https://fips.808bits.com/mcp"
}
}
} {
"servers": {
"com-808bits-fips-cmvp": {
"type": "http",
"url": "https://fips.808bits.com/mcp"
}
}
} [mcp_servers.com-808bits-fips-cmvp] url = "https://fips.808bits.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-808bits-fips-cmvp": {
"type": "remote",
"url": "https://fips.808bits.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-808bits-fips-cmvp --url 'https://fips.808bits.com/mcp' --transport streamable-http
mcp_servers:
com-808bits-fips-cmvp:
url: "https://fips.808bits.com/mcp" {
"McpServers": {
"com-808bits-fips-cmvp": {
"Transport": "http",
"Url": "https://fips.808bits.com/mcp"
}
}
} assistant mcp add com-808bits-fips-cmvp -t streamable-http -u 'https://fips.808bits.com/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
- 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 security
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +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.
- 21 Sept 26 +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.
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 15 Sept 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 28 Sept 2026 · Probed https://fips.808bits.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=808bits.com | CN=WE1,O=Google Trust Services,C=US | 3 Sept 2026 | 2 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 24d07555676ec7370ec48fa3f77ff31e |
| SANs: 808bits.com, fips.808bits.com, *.fips.808bits.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of fips.808bits.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| 808bits.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://fips.808bits.com/mcp | Verified | 200 | |
| http (plaintext) | http://fips.808bits.com/mcp | HTTPS enforced | 301 | https://fips.808bits.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
fips_cert ~55
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.
| Name | Type | Req | Description |
|---|---|---|---|
| number | integer | yes | – |
No output schema declared.
No examples provided.
fips_cve ~166
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cve | string | – | CVE id, e.g. CVE-2023-4807 |
| limit | integer | – | – |
| min_cvss | number | – | – |
| vendor | string | – | Vendor name or part of one |
No output schema declared.
No examples provided.
fips_in_process ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| phase | string | – | e.g. Review, Finalization, Coordination |
| query | string | – | Substring of the module name or vendor |
No output schema declared.
No examples provided.
fips_search ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| level | integer | – | – |
| limit | integer | – | – |
| query | string | yes | 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 | – | – |
No output schema declared.
No examples provided.
fips_sunset ~131
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.
| Name | Type | Req | Description |
|---|---|---|---|
| before | string | – | ISO date, exclusive: before=2026-09-21 excludes the 21st itself |
| limit | integer | – | – |
| standard | string | – | – |
| vendor | string | – | – |
No output schema declared.
No examples provided.
fips_vendor ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| vendor | string | yes | Vendor name or part of one |
No output schema declared.
No examples provided.
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.