FIPS 140 certificate tracker MCP: what works in Claude, ChatGPT, Cursor, and Grok Bot
Every NIST FIPS 140 certificate, plus the modules-in-process queue NIST publishes only as a page.
Registry name: com.808bits/fips-cmvp (v0.1.0) | GitHub stars
Status grid
| App | Status | Date tested |
|---|---|---|
| Claude | Untested | Not yet tested |
| ChatGPT | Untested | Not yet tested |
| Cursor | Untested | Not yet tested |
| Grok Bot | Untested | Not yet tested |
| MCP Inspector (reference client) | Untested | Not yet tested |
| MCP TypeScript SDK (reference client) | Untested | Not yet tested |
Hands-on test results
No hands-on tests yet. We do not publish results until we have actually tested.
Automated handshake
No public remote endpoint to check (local or package-only server).
Gotchas
None recorded yet. Gotchas come only from hands-on tests.
Compare with other tested connectors | Connector Weather
Request a hands-on test of FIPS 140 certificate tracker
Get the badge
Maintain FIPS 140 certificate tracker or write about it? Show its live ConnectorReport status in your README or docs.
Markdown (README, docs)
[](https://connectorreport.com/c/com-808bits-fips-cmvp?utm_source=badge&utm_medium=embed&utm_campaign=com-808bits-fips-cmvp)
HTML
<a href="https://connectorreport.com/c/com-808bits-fips-cmvp?utm_source=badge&utm_medium=embed&utm_campaign=com-808bits-fips-cmvp"><img src="https://connectorreport.com/badge/com-808bits-fips-cmvp.svg" alt="FIPS 140 certificate tracker MCP status on ConnectorReport"/></a>
The badge updates on its own after every retest. How badges work