X feedback discovery, noise-reduced query planning, signal filtering, and AI handoffs.
Dev & Codev2.5.1streamable-httpmcp.kgninja.dev repository
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 243ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo hyperxosist-mcp-server@2.5.0 |
| tooling | 35 / 35 | tools/list OK: 3 tools e.g. "hyperxosist_search_plan"; 3/3 described, 3/3 fully-typed schemas, median description 207 chars |
| latency | 10 / 10 | initialize round-trip 243ms |
| provenance | 15 / 15 | description present; repository linked; version 2.5.1; namespace io.github.KG-NINJA matches endpoint/repo |
Score 100/100 · latency 243ms · 3 tools · auth: open
Claude Code:
claude mcp add --transport http hyperxosist-agent https://mcp.kgninja.dev/mcp
Generic MCP client config:
{ "mcpServers": { "hyperxosist-agent": { "type": "http", "url": "https://mcp.kgninja.dev/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.KG-NINJA/hyperxosist-agent · referral link https://mcpqueen.com/go/io.github.KG-NINJA/hyperxosist-agent (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/io.github.KG-NINJA/hyperxosist-agent)
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.
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-13 17:01 | A | 100 | 243ms |