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
91 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Audits a sample of HTTP request URLs against explicit, documented cache-key standardization rules...
Website
https://mcp-factory.bowling-anthony.workers.dev/cache-key-explosion-auditor
Listing
From the official MCP registry (active).
Recent checks of Cache Key Explosion Auditor
CheckedResultHandshake
1 hour agoHandshake completed91 ms
1 day agoHandshake completed156 ms
2 days agoHandshake completed125 ms
3 days agoHandshake completed110 ms
4 days agoHandshake completed111 ms
5 days agoHandshake completed92 ms
6 days agoHandshake completed377 ms
9 days agoHandshake completed102 ms
11 days agoHandshake completed113 ms
14 days agoHandshake completed283 ms
16 days agoHandshake completed188 ms
18 days agoHandshake completed120 ms
20 days agoHandshake completed677 ms
22 days agoHandshake completed127 ms
24 days agoHandshake completed85 ms
26 days agoHandshake completed103 ms
27 days agoHandshake completed100 ms
29 days agoHandshake completed305 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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.