Connect

8 clients · secrets stay placeholders

JSON (mcpServers)Claude CodeCodexOpenCodeCursorVS CodeGemini CLIGoose

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

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

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

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

{
  "mcpServers": {
    "fips-cmvp": {
      "type": "http",
      "url": "https://fips.808bits.com/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=fips-cmvp&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vZmlwcy44MDhiaXRzLmNvbS9tY3AifQ%3D%3D"
}

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

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

extensions:
  "fips-cmvp":
    enabled: true
    name: "fips-cmvp"
    type: streamable_http
    uri: "https://fips.808bits.com/mcp"
    timeout: 300

Quality 83 / 100good

protocol88 · weight 25

pass
protocol.modernsupports 2026-07-28 (server/discover)
pass
protocol.statelessanswers without a session
pass
protocol.transportstreamable HTTP
warn
protocol.list_ttltools/list declares ttlMs 0, so clients re-fetch it on every use

authorizationn/a · weight 15

n/a
auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
n/a
auth.secret_in_urlno templated URL

tool hygiene71 · weight 30

pass
tools.descriptionsevery tool has a description
pass
tools.description_lengthdescriptions are concise
pass
tools.schemasevery tool has an object input schema
fail
tools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
fail
tools.directory_hintsno 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_costabout 1,049 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump

stability100 · weight 15

pass
stability.changes1 tool changes in 30 days
pass
stability.rug_pullno tool changed its meaning under the same name

dependenciesn/a · weight 15

n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

6 tools, about 1,049 tokens to load them all · tool set 7390faff6948 · tools last changed 2026-09-25 · checked 2026-10-20 06:17 UTC

Tool changes

2026-09-25fips_cvechangeddescription
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 · 93% of words in common
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: list_changes · trend: quality JSON.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 73 / 100

provenance100

liveness19

freshness85

hygiene100

+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. How it is computed.

Endpoints

remote	auth	reachable	uptime 30d	p50	protocol	last ok
`https://fips.808bits.com/mcp` streamable-http	none	no (2 failures)	98%	297 ms	2026-07-28	2026-10-18

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.

Schemas: list_tools.

Similar MCP servers

Official server.json

{
  "name": "com.808bits/fips-cmvp",
  "title": "FIPS 140 certificate tracker",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://fips.808bits.com/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "0.1.0",
  "repository": {
    "url": "https://github.com/808bits/fips-mcp",
    "source": "github"
  },
  "websiteUrl": "https://808bits.com/fips/mcp/",
  "description": "Every NIST FIPS 140 certificate, plus the modules-in-process queue NIST publishes only as a page."
}