Bitcoin-anchored, tamper-evident audit-permanence layer for AI agents, FRE 902(13)/(14)-shaped.
AI & Agentsv1.0.1streamable-httpbonissystems.com
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 179ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-03-26, serverInfo knox-anchor@1.0.0 |
| tooling | 35 / 35 | tools/list OK: 7 tools e.g. "get_descriptor"; 7/7 described, 7/7 fully-typed schemas, median description 269 chars |
| latency | 10 / 10 | initialize round-trip 179ms |
| provenance | 12 / 15 | description present; no repository URL; version 1.0.1; namespace com.bonissystems matches endpoint/repo |
Score 97/100 · latency 179ms · 7 tools · auth: open
Claude Code:
claude mcp add --transport http knox-anchor https://bonissystems.com/api/knox/mcp
Generic MCP client config:
{ "mcpServers": { "knox-anchor": { "type": "http", "url": "https://bonissystems.com/api/knox/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/com.bonissystems/knox-anchor · referral link https://mcpqueen.com/go/com.bonissystems/knox-anchor (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/com.bonissystems/knox-anchor)
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 23:00 | A | 97 | 179ms |