Committee-reviewed market sizing, forecasts, and competitive landscape from Meridian Consensus.
Dev & Codev1.0.2streamable-httpwww.meridianconsensus.com
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 1505ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo meridian-consensus@1.0.0 |
| tooling | 35 / 35 | tools/list OK: 8 tools e.g. "search_markets"; 8/8 described, 8/8 fully-typed schemas, median description 336 chars |
| latency | 4 / 10 | initialize round-trip 1505ms |
| provenance | 5 / 15 | description present; no repository URL; version 1.0.2; namespace io.github.adicted07-lang does NOT match remote host (expected *.adicted07-lang.github.io) |
Score 84/100 · latency 1505ms · 8 tools · auth: open
Claude Code:
claude mcp add --transport http meridian-consensus https://www.meridianconsensus.com/api/mcp
Generic MCP client config:
{ "mcpServers": { "meridian-consensus": { "type": "http", "url": "https://www.meridianconsensus.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.adicted07-lang/meridian-consensus · referral link https://mcpqueen.com/go/io.github.adicted07-lang/meridian-consensus (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/io.github.adicted07-lang/meridian-consensus)
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 20:48 | B | 84 | 1505ms |