Remote MCP · Endpoint
WebKnox MCP server
No. WebKnox answered an MCP handshake 3 hours ago.
UpLast checked 3 hours ago
Server URL
https://mcp.webknox.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.webknox/webknox
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 191 ms
- Tools exposed
- 1 tool
- Uptime, last 30 days
- 100% from 11 checks
- Described by its publisher as
- Answer cards in the chat: comparisons with photos, weather, nutrition, recipes, media and more.
- Website
- https://webknox.com/docs/mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 3 hours ago | Handshake completed | 191 ms |
| 4 days ago | Handshake completed | 389 ms |
| 14 days ago | Handshake completed | 202 ms |
| 15 days ago | Handshake completed | 177 ms |
| 15 days ago | Handshake completed | 161 ms |
| 17 days ago | Handshake completed | 177 ms |
| 18 days ago | Handshake completed | 174 ms |
| 19 days ago | Handshake completed | 185 ms |
| 20 days ago | Handshake completed | 218 ms |
| 21 days ago | Handshake completed | 152 ms |
| 23 days ago | Handshake completed | 205 ms |
The last 11 checks. Full history is kept for 30 days; the all-time counter stands at 11 responding of 11.
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 WebKnox and makes no claim about it beyond what these checks measured.