MCP QUEEN
dev.turva/turva-mcp A
Read-only MCP server for turva.dev, an agent-readiness audit and advisory service.
AI & Agentsv1.0.0streamable-httpmcp.turva.dev
Grade evidence — probed 2026-07-13 11:00 UTC
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 904ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo turva-mcp@1.2.1 |
| tooling | 35 / 35 | tools/list OK: 4 tools e.g. "get_services"; 4/4 described, 4/4 fully-typed schemas, median description 410 chars |
| latency | 7 / 10 | initialize round-trip 904ms |
| provenance | 12 / 15 | description present; no repository URL; version 1.0.0; namespace dev.turva matches endpoint/repo |
Score 94/100 · latency 904ms · 4 tools · auth: open
Connect your agent
Claude Code:
claude mcp add --transport http turva-mcp https://mcp.turva.dev/mcp
Generic MCP client config:
{ "mcpServers": { "turva-mcp": { "type": "http", "url": "https://mcp.turva.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/dev.turva/turva-mcp · referral link https://mcpqueen.com/go/dev.turva/turva-mcp (counts as “routed via the queen”).
Own this server? Embed your grade badge
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/dev.turva/turva-mcp)
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.
Queen Watch
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
Probe history
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-13 11:00 | A | 94 | 904ms |