Living docs and MCP context for GitHub repos — conventions, gaps, and source-cited pages on merge.
Dev & Codev0.1.0streamable-httpmoxiedocs.com repository
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 1919ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo moxie-docs@0.3.0 |
| tooling | 35 / 35 | tools/list OK: 10 tools e.g. "moxie.get_conventions"; 10/10 described, 10/10 fully-typed schemas, median description 453 chars |
| latency | 4 / 10 | initialize round-trip 1919ms |
| provenance | 15 / 15 | description present; repository linked; version 0.1.0; namespace io.github.Jackalope-Dev matches endpoint/repo |
Score 94/100 · latency 1919ms · 10 tools · auth: open
Claude Code:
claude mcp add --transport http moxie-docs https://moxiedocs.com/api/mcp
Generic MCP client config:
{ "mcpServers": { "moxie-docs": { "type": "http", "url": "https://moxiedocs.com/api/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.Jackalope-Dev/moxie-docs · referral link https://mcpqueen.com/go/io.github.Jackalope-Dev/moxie-docs (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/io.github.Jackalope-Dev/moxie-docs)
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 | 94 | 1919ms |