Remote MCP · Endpoint
FIPS 140 certificate tracker MCP server
No. FIPS 140 certificate tracker answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://fips.808bits.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.808bits/fips-cmvp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 289 ms
- Tools exposed
- 6 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Every NIST FIPS 140 certificate, plus the modules-in-process queue NIST publishes only as a page.
- Repository
- https://github.com/808bits/fips-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 289 ms |
| 1 day ago | Handshake completed | 169 ms |
| 2 days ago | Handshake completed | 155 ms |
| 3 days ago | Handshake completed | 254 ms |
| 4 days ago | Handshake completed | 175 ms |
| 5 days ago | Handshake completed | 202 ms |
| 7 days ago | Handshake completed | 498 ms |
| 10 days ago | Handshake completed | 192 ms |
| 12 days ago | Handshake completed | 211 ms |
| 14 days ago | Handshake completed | 163 ms |
| 17 days ago | Handshake completed | 84 ms |
| 19 days ago | Handshake completed | 185 ms |
| 21 days ago | Handshake completed | 151 ms |
| 23 days ago | Handshake completed | 164 ms |
| 25 days ago | Handshake completed | 174 ms |
| 26 days ago | Handshake completed | 231 ms |
| 28 days ago | Handshake completed | 160 ms |
| 29 days ago | Handshake completed | 326 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with FIPS 140 certificate tracker and makes no claim about it beyond what these checks measured.