MCP QUEEN
cloud.redu/mcp A
Agent-native cloud, EU-hosted. Provision VMs, networks & databases on redu.cloud via MCP.
AI & Agentsv0.1.1streamable-httpmcp.redu.cloud
Grade evidence — probed 2026-07-12 21:15 UTC
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 578ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo redu-cloud-mcp@2.0.0 |
| tooling | 35 / 35 | tools/list OK: 64 tools e.g. "whoami"; 64/64 described, 64/64 fully-typed schemas, median description 228 chars |
| latency | 7 / 10 | initialize round-trip 578ms |
| provenance | 12 / 15 | description present; no repository URL; version 0.1.1; namespace cloud.redu matches endpoint/repo |
Score 94/100 · latency 578ms · 64 tools · auth: open
Connect your agent
Claude Code:
claude mcp add --transport http mcp https://mcp.redu.cloud/mcp
Generic MCP client config:
{ "mcpServers": { "mcp": { "type": "http", "url": "https://mcp.redu.cloud/mcp" } } }
MCP Queen is a graded index, not a middleman — your agent connects directly to the server above. Check the grade and evidence first; that's the point.
Share this server: permalink https://mcpqueen.com/s/cloud.redu/mcp · referral link https://mcpqueen.com/go/cloud.redu/mcp (counts as “routed via the queen”).
Own this server? Embed your grade badge
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/cloud.redu/mcp)
Think the grade is wrong? Fix the finding the evidence shows, then the next probe cycle picks it up automatically (full cycle ≈ 3 days) — or open a dispute via the MCP endpoint.
Queen Watch
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
Probe history
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-12 21:15 | A | 94 | 578ms |