MCP QUEEN
cloud.theprotocol/registry B
Sovereign AI agent platform. 19 tools: discovery, transfers, staking, governance. A2A v1.0.
AI & Agentsv1.0.0sseapi.theprotocol.cloud
Grade evidence — probed 2026-07-12 21:15 UTC
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 546ms |
| protocol | 8 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-11-25, serverInfo TheProtocol@1.0.0 — registry declares deprecated 'sse' transport |
| tooling | 35 / 35 | tools/list OK: 404 tools e.g. "theprotocol_discoverRegistries"; 404/404 described, 404/404 fully-typed schemas, median description 66 chars |
| latency | 7 / 10 | initialize round-trip 546ms |
| provenance | 12 / 15 | description present; no repository URL; version 1.0.0; namespace cloud.theprotocol matches endpoint/repo |
Score 87/100 · latency 546ms · 404 tools · auth: open
Connect your agent
Claude Code:
claude mcp add --transport http registry https://api.theprotocol.cloud/mcp/sse
Generic MCP client config:
{ "mcpServers": { "registry": { "type": "http", "url": "https://api.theprotocol.cloud/mcp/sse" } } }
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.theprotocol/registry · referral link https://mcpqueen.com/go/cloud.theprotocol/registry (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.theprotocol/registry)
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 | B | 87 | 546ms |