Remote MCP · Endpoint
Checkly MCP by usefulapi MCP server
No. Checkly MCP by usefulapi answered an MCP handshake 6 minutes ago.
UpLast checked 6 minutes ago
Server URL
https://checkly.usefulapi.io/mcp
The last check completed an MCP handshake.
- Registry name
- io.usefulapi/checkly
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 215 ms
- Tools exposed
- 22 tools
- Uptime, last 30 days
- 72.2% from 18 checks
- Described by its publisher as
- Query Checkly synthetic monitoring — checks, statuses, results, alerts, reporting and dashboards.
- Repository
- https://github.com/m190/usefulapi-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 6 minutes ago | Handshake completed | 215 ms |
| 2 days ago | Handshake completed | 142 ms |
| 4 days ago | Handshake completed | 287 ms |
| 6 days ago | Handshake completed | 235 ms |
| 7 days ago | Handshake completed | 241 ms |
| 9 days ago | Handshake completed | 326 ms |
| 10 days ago | Failed - the check failed for an unclassified reason | — |
| 11 days ago | Failed - the check failed for an unclassified reason | — |
| 14 days ago | Handshake completed | 185 ms |
| 15 days ago | Handshake completed | 177 ms |
| 17 days ago | Handshake completed | 333 ms |
| 18 days ago | Handshake completed | 158 ms |
| 20 days ago | Handshake completed | 193 ms |
| 21 days ago | Handshake completed | 165 ms |
| 22 days ago | Failed - the check failed for an unclassified reason | — |
| 22 days ago | Failed - the check failed for an unclassified reason | — |
| 23 days ago | Handshake completed | 207 ms |
| 25 days ago | Failed - the check failed for an unclassified reason | — |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 18.
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 Checkly MCP by usefulapi and makes no claim about it beyond what these checks measured.