Timestamp and verify evidence on-chain. Prove what your agent saw and when; verifying is free.
AI & Agentsv0.1.0streamable-httpbsv.cx
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 395ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo bsv.cx@0.1.0 |
| tooling | 35 / 35 | tools/list OK: 7 tools e.g. "notarize_hash"; 7/7 described, 7/7 fully-typed schemas, median description 189 chars |
| latency | 10 / 10 | initialize round-trip 395ms |
| provenance | 12 / 15 | description present; no repository URL; version 0.1.0; namespace cx.bsv matches endpoint/repo |
Score 97/100 · latency 395ms · 7 tools · protocol access: open ⓘ
Security, data integrity, citation quality, and advertised claims are measured separately from protocol uptime. Missing evidence is marked unverified, never converted into a pass.
| Dimension | Metric | Status | Evidence | Source |
|---|---|---|---|---|
| security | authentication_boundary | observed | Live protocol probe observed auth_state=open. This describes discovery/access behavior; it is not by itself a vulnerability finding. Observed value: open | live_probe |
Machine-readable receipt: /api/trust/cx.bsv/bsv-cx.json
Claude Code:
claude mcp add --transport http bsv-cx https://bsv.cx/mcp
Generic MCP client config:
{ "mcpServers": { "bsv-cx": { "type": "http", "url": "https://bsv.cx/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/cx.bsv/bsv-cx · referral link https://mcpqueen.com/go/cx.bsv/bsv-cx (counts as “routed via the queen”).
Live operational-grade badge, re-probed continuously — not a security or data-quality certification. Put it in your README and link to the complete receipt:
[](https://mcpqueen.com/s/cx.bsv/bsv-cx)
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-24 13:30 | A | 97 | 395ms |