MCP QUEEN
io.github.srotzin/hiveclear A
Multi-agent settlement and clearing with validator consensus
Dev & Codev1.0.0streamable-httphiveclear.onrender.com repository
Grade evidence — probed 2026-07-14 21:00 UTC
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 248ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2024-11-05, serverInfo hiveclear@1.0.0 |
| tooling | 35 / 35 | tools/list OK: 4 tools e.g. "hiveclear_submit_settlement"; 4/4 described, 4/4 fully-typed schemas, median description 132 chars |
| latency | 10 / 10 | initialize round-trip 248ms |
| provenance | 15 / 15 | description present; repository linked; version 1.0.0; namespace io.github.srotzin matches endpoint/repo |
Score 100/100 · latency 248ms · 4 tools · auth: open
Connect your agent
Claude Code:
claude mcp add --transport http hiveclear https://hiveclear.onrender.com/mcp
Generic MCP client config:
{ "mcpServers": { "hiveclear": { "type": "http", "url": "https://hiveclear.onrender.com/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/io.github.srotzin/hiveclear · referral link https://mcpqueen.com/go/io.github.srotzin/hiveclear (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/io.github.srotzin/hiveclear)
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-14 21:00 | A | 100 | 248ms |