Remote MCP · Endpoint
MCP health — MCP directory health check diagnostics MCP server
No. MCP health — MCP directory health check diagnostics answered an MCP handshake 2 days ago.
UpLast checked 2 days ago
Server URL
https://mcp-health.rowb.app/mcp
The last check completed an MCP handshake.
- Registry name
- app.rowb.mcp-health/probe
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 225 ms
- Tools exposed
- 2 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Diagnoses whether an MCP server is reachable, by live HTTP probe.
- Website
- https://mcp-health.rowb.app/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 days ago | Handshake completed | 225 ms |
| 3 days ago | Handshake completed | 549 ms |
| 3 days ago | Handshake completed | 259 ms |
| 5 days ago | Handshake completed | 265 ms |
| 6 days ago | Handshake completed | 286 ms |
| 7 days ago | Handshake completed | 302 ms |
| 8 days ago | Handshake completed | 256 ms |
| 9 days ago | Handshake completed | 294 ms |
| 11 days ago | Handshake completed | 596 ms |
| 13 days ago | Handshake completed | 253 ms |
| 16 days ago | Handshake completed | 723 ms |
| 18 days ago | Handshake completed | 297 ms |
| 21 days ago | Handshake completed | 321 ms |
| 22 days ago | Handshake completed | 247 ms |
| 25 days ago | Handshake completed | 277 ms |
| 27 days ago | Handshake completed | 252 ms |
| 29 days ago | Handshake completed | 227 ms |
| 30 days ago | Handshake completed | 232 ms |
| 31 days ago | Handshake completed | 265 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 27 responding of 27.
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 MCP health — MCP directory health check diagnostics and makes no claim about it beyond what these checks measured.