Deterministic sealed verdicts on public claims and startup ideas (0-LLM claim-safety guardian).
Dev & Codev1.0.0streamable-httpbies.io
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 243ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo bies@1.0.0 |
| tooling | 35 / 35 | tools/list OK: 3 tools e.g. "claim_safety_verdict"; 3/3 described, 3/3 fully-typed schemas, median description 420 chars |
| latency | 10 / 10 | initialize round-trip 243ms |
| provenance | 5 / 15 | description present; no repository URL; version 1.0.0; namespace io.github.dth0108 does NOT match remote host (expected *.dth0108.github.io) |
Score 90/100 · latency 243ms · 3 tools · auth: open
Claude Code:
claude mcp add --transport http bies-guardian https://bies.io/mcp
Generic MCP client config:
{ "mcpServers": { "bies-guardian": { "type": "http", "url": "https://bies.io/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.dth0108/bies-guardian · referral link https://mcpqueen.com/go/io.github.dth0108/bies-guardian (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/io.github.dth0108/bies-guardian)
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-14 00:30 | A | 90 | 243ms |