Remote MCP · Endpoint
cloud.redu/mcp MCP server
No. cloud.redu/mcp answered an MCP handshake 5 hours ago.
UpLast checked 5 hours ago
Server URL
https://mcp.redu.cloud/mcp
The last check completed an MCP handshake.
- Registry name
- cloud.redu/mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 400 ms
- Tools exposed
- 86 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Agent-native cloud, EU-hosted. Provision VMs, networks & databases on redu.cloud via MCP.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 5 hours ago | Handshake completed | 400 ms |
| 2 days ago | Handshake completed | 397 ms |
| 4 days ago | Handshake completed | 437 ms |
| 5 days ago | Handshake completed | 403 ms |
| 7 days ago | Handshake completed | 422 ms |
| 8 days ago | Handshake completed | 401 ms |
| 9 days ago | Handshake completed | 397 ms |
| 12 days ago | Handshake completed | 395 ms |
| 13 days ago | Handshake completed | 396 ms |
| 15 days ago | Handshake completed | 396 ms |
| 16 days ago | Handshake completed | 394 ms |
| 17 days ago | Handshake completed | 402 ms |
| 18 days ago | Handshake completed | 409 ms |
| 19 days ago | Handshake completed | 403 ms |
| 20 days ago | Handshake completed | 408 ms |
| 21 days ago | Handshake completed | 389 ms |
| 22 days ago | Handshake completed | 401 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.
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 cloud.redu/mcp and makes no claim about it beyond what these checks measured.