mcp-registry/com.808bits/fips-cmvp · v0.1.0
As of 2026-10-27 03:31 UTC, the 808bits Fips Cmvp MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 11 minutes.
Every NIST FIPS 140 certificate, plus the modules-in-process queue NIST publishes only as a page.
Point your MCP client at this streamable-http endpoint: https://fips.808bits.com/mcp
12 parameter(s) across 6 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
6 of 6 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 6 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.808bits%2Ffips-cmvp/fixes
{
"name": "fips_search",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"query"
],
"properties": {
"level": {
"type": "integer",
"maximum": 4,
"minimum": 1
},
"limit": {
"type": "integer",
"default": 20,
"maximum": 50,
"minimum": 1
},
"query": {
"type": "string",
"minLength": 2,
"description": "Module name or vendor. Several words all have to match, in any order and across either field, so \"openssl provider\" works."
},
"status": {
"enum": [
"active",
"historical",
"revoked"
],
"type": "string"
},
"standard": {
"enum": [
"140-1",
"140-2",
"140-3"
],
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.808bits/fips-cmvp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.808bits/fips-cmvp"}) over MCP.
fips_cve ~246 tokensfips_search ~237 tokensfips_vendor ~227 tokensfips_sunset ~210 tokensfips_in_process ~184 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.808bits%2Ffips-cmvp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.808bits%2Ffips-cmvp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.808bits%2Ffips-cmvp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.808bits%2Ffips-cmvp.svg :target: https://glimind.com/server/mcp-registry%2Fcom.808bits%2Ffips-cmvp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:a535a61925c94dbe…, first seen 2026-10-17, included at leaf 14057 of 77,101. Version history · verify what your client received.
Compare: most reliable other servers · most reliable data servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-27 03:31 UTC, the 808bits Fips Cmvp MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 11 minutes.
808bits Fips Cmvp MCP server advertises 6 tools, including fips_cert, fips_cve, fips_in_process, fips_search, fips_sunset.
Point your MCP client at this streamable-http endpoint: https://fips.808bits.com/mcp
Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.