MCP QUEEN
eu.dockhold/dockhold A
Deploy a GitHub repo to a live HTTPS URL from your AI tool; read logs, set variables, resize apps.
Dev & Codev0.1.0streamable-httpapi.dockhold.eu
Grade evidence — probed 2026-07-13 11:15 UTC
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 859ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo dockhold@0.1.0 |
| tooling | 35 / 35 | tools/list OK: 12 tools e.g. "list_apps"; 12/12 described, 12/12 fully-typed schemas, median description 353 chars |
| latency | 7 / 10 | initialize round-trip 859ms |
| provenance | 12 / 15 | description present; no repository URL; version 0.1.0; namespace eu.dockhold matches endpoint/repo |
Score 94/100 · latency 859ms · 12 tools · auth: open
Connect your agent
Claude Code:
claude mcp add --transport http dockhold https://api.dockhold.eu/mcp
Generic MCP client config:
{ "mcpServers": { "dockhold": { "type": "http", "url": "https://api.dockhold.eu/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/eu.dockhold/dockhold · referral link https://mcpqueen.com/go/eu.dockhold/dockhold (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/eu.dockhold/dockhold)
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-13 11:15 | A | 94 | 859ms |