Remote MCP · Endpoint
com.kettlelogic/mcp-kettlelogic MCP server
No. com.kettlelogic/mcp-kettlelogic answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://kettlelogic.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.kettlelogic/mcp-kettlelogic
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 292 ms
- Tools exposed
- 5 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- MCP server exposing Kettle Logic insight articles & industry guidance as tools + resources.
- Website
- https://kettlelogic.com/mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 292 ms |
| 18 hours ago | Handshake completed | 197 ms |
| 2 days ago | Handshake completed | 178 ms |
| 3 days ago | Handshake completed | 182 ms |
| 4 days ago | Handshake completed | 189 ms |
| 5 days ago | Handshake completed | 186 ms |
| 6 days ago | Handshake completed | 173 ms |
| 7 days ago | Handshake completed | 179 ms |
| 10 days ago | Handshake completed | 246 ms |
| 13 days ago | Handshake completed | 188 ms |
| 15 days ago | Handshake completed | 181 ms |
| 17 days ago | Handshake completed | 254 ms |
| 19 days ago | Handshake completed | 163 ms |
| 21 days ago | Handshake completed | 175 ms |
| 23 days ago | Handshake completed | 169 ms |
| 25 days ago | Handshake completed | 167 ms |
| 27 days ago | Handshake completed | 198 ms |
| 28 days ago | Handshake completed | 392 ms |
| 29 days ago | Handshake completed | 169 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 28 responding of 30.
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 com.kettlelogic/mcp-kettlelogic and makes no claim about it beyond what these checks measured.