The statistical analyst in your AI chat — validated, citable, re-runnable analysis of your data.
Data & Databasesv1.0.6streamable-httpapi.mcpanalytics.ai repository
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 709ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2024-11-05, serverInfo MCP Analytics@1.0.5 |
| tooling | 35 / 35 | tools/list OK: 13 tools e.g. "account_link"; 13/13 described, 13/13 fully-typed schemas, median description 98 chars |
| latency | 7 / 10 | initialize round-trip 709ms |
| provenance | 15 / 15 | description present; repository linked; version 1.0.6; namespace ai.mcpanalytics matches endpoint/repo |
Score 97/100 · latency 709ms · 13 tools · auth: open
Claude Code:
claude mcp add --transport http analytics https://api.mcpanalytics.ai/mcp/api-key
Generic MCP client config:
{ "mcpServers": { "analytics": { "type": "http", "url": "https://api.mcpanalytics.ai/mcp/api-key" } } }
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.mcpanalytics/analytics · referral link https://mcpqueen.com/go/ai.mcpanalytics/analytics (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/ai.mcpanalytics/analytics)
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 15:01 | A | 97 | 709ms |