Skip to content

FIPS 140 certificate tracker MCP server

com.808bits/fips-cmvp808bits.comstreamable-httpv0.1.0Scanned

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

6 tools: 3 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 3 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the FIPS 140 certificate tracker MCP server can do

The FIPS 140 certificate tracker MCP server is published by 808bits.com, a domain the MCP Registry verified. It has 6 tools. It can create or change data (3 tools: fips_cert, fips_vendor and fips_cve), but cannot delete data. 3 tools only read.

1 tool brings in text other people can write (fips_in_process).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 10, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 3Claude Code: ask
  • fips_certLook up one FIPS 140 cryptographic module validation by certificate number.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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_cveWhich FIPS-validated modules are associated with a given CVE, or which CVEs are associated with a vendor's modules.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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_vendorEverything one company holds, grouped across the spelling variants NIST filed it under.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
Only reads 3Show 3 read-only tools
  • fips_in_processSearch NIST's Modules in Process queue: submissions awaiting FIPS 140-3 validation, with the review phase each one is sitting in.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "search": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "search" and "review": it reads comments, which other people can write.
    Description, as the server wrote it
    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_sunsetList active FIPS validations by sunset date, the day each moves to NIST's historical list and stops being valid for new procurement.No findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:33 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://fips.808bits.com/mcp: tools/list returned 6 tools to an anonymous client, including fips_cert (write), fips_vendor (write), fips_cve (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__fips-cmvp__fips_search",
      "mcp__fips-cmvp__fips_in_process",
      "mcp__fips-cmvp__fips_sunset"
    ],
    "ask": [
      "mcp__fips-cmvp__fips_cert",
      "mcp__fips-cmvp__fips_vendor",
      "mcp__fips-cmvp__fips_cve"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as fips-cmvp. Review it before you use it.

Capability tags behind 1 rule
  • mcp__fips-cmvp__fips_in_process untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.808bits/fips-cmvp/verify?hash=536251bd0e7e829bb215a8b3c5ad99558ef25eb4cbcb1e0c501d1264b79fda5c" | jq -e '.changed == false'

Pinned hash 536251bd0e7e, from Nov 10, 2026, 09:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.808bits/fips-cmvp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.808bits/fips-cmvp
[![Anlyon Radar](https://radar.anlyon.com/badge/com.808bits/fips-cmvp.svg)](https://radar.anlyon.com/servers/com.808bits/fips-cmvp)

Source: MCP Registry · repository. Synced Oct 21, 2026, 17:47 UTC.

FIPS 140 certificate tracker MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the FIPS 140 certificate tracker MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the FIPS 140 certificate tracker MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the FIPS 140 certificate tracker MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the FIPS 140 certificate tracker MCP server have?

6 tools: 3 write, 3 read. fips_cert, fips_vendor, fips_cve, fips_search, fips_in_process and fips_sunset.

Does the FIPS 140 certificate tracker MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the FIPS 140 certificate tracker MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the FIPS 140 certificate tracker MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.