Remote MCP · Endpoint
Cache Key Explosion Auditor MCP server
No. Cache Key Explosion Auditor answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp-factory.bowling-anthony.workers.dev/cache-key-explosion-auditor/mcp
The last check completed an MCP handshake.
- Registry name
- com.mcpscores/cache-key-explosion-auditor
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 677 ms
- Tools exposed
- 1 tool
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Audits a sample of HTTP request URLs against explicit, documented cache-key standardization rules...
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 677 ms |
| 2 days ago | Handshake completed | 127 ms |
| 4 days ago | Handshake completed | 85 ms |
| 5 days ago | Handshake completed | 103 ms |
| 7 days ago | Handshake completed | 100 ms |
| 8 days ago | Handshake completed | 305 ms |
| 9 days ago | Handshake completed | 13 ms |
| 12 days ago | Handshake completed | 11 ms |
| 13 days ago | Handshake completed | 50 ms |
| 15 days ago | Handshake completed | 15 ms |
| 17 days ago | Handshake completed | 24 ms |
| 18 days ago | Handshake completed | 19 ms |
| 19 days ago | Handshake completed | 12 ms |
| 20 days ago | Handshake completed | 37 ms |
| 20 days ago | Handshake completed | 79 ms |
| 21 days ago | Handshake completed | 79 ms |
| 23 days ago | Handshake completed | 84 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.
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 Cache Key Explosion Auditor and makes no claim about it beyond what these checks measured.