Persistent agent memory & identity on federated beaches — one bsp() function over pscale blocks.
Dev & Codev0.4.0streamable-httpbsp.hermitcrab.me repository
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 218ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo bsp-mcp-server@0.4.0 |
| tooling | 34 / 35 | tools/list OK: 11 tools e.g. "bsp"; 11/11 described, 10/11 fully-typed schemas, median description 827 chars |
| latency | 10 / 10 | initialize round-trip 218ms |
| provenance | 15 / 15 | description present; repository linked; version 0.4.0; namespace io.github.pscale-commons matches endpoint/repo |
Score 99/100 · latency 218ms · 11 tools · auth: open
Claude Code:
claude mcp add --transport http bsp-mcp https://bsp.hermitcrab.me/mcp/v1
Generic MCP client config:
{ "mcpServers": { "bsp-mcp": { "type": "http", "url": "https://bsp.hermitcrab.me/mcp/v1" } } }
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.pscale-commons/bsp-mcp · referral link https://mcpqueen.com/go/io.github.pscale-commons/bsp-mcp (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/io.github.pscale-commons/bsp-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.
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 18:45 | A | 99 | 218ms |