OSS libs in your stack, really used: source, tests, callers. C#, Java, TS, Python, Rust, PHP+.
Dev & Codev1.2.6streamable-httpmcp.example4.ai repository
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 502ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-03-26, serverInfo xmp4@1.2.7 |
| tooling | 35 / 35 | tools/list OK: 16 tools e.g. "xmp4_callees"; 16/16 described, 16/16 fully-typed schemas, median description 84 chars |
| latency | 7 / 10 | initialize round-trip 502ms |
| provenance | 15 / 15 | description present; repository linked; version 1.2.6; namespace ai.example4 matches endpoint/repo |
Score 97/100 · latency 502ms · 16 tools · auth: open
Claude Code:
claude mcp add --transport http xmp4 https://mcp.example4.ai/mcp
Generic MCP client config:
{ "mcpServers": { "xmp4": { "type": "http", "url": "https://mcp.example4.ai/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/ai.example4/xmp4 · referral link https://mcpqueen.com/go/ai.example4/xmp4 (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/ai.example4/xmp4)
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-12 14:20 | A | 97 | 502ms |