MCP QUEEN
com.borisinc/memory A
Persistent agent memory paid per call via x402 USDC. Your wallet is your private memory namespace.
AI & Agentsv1.0.0streamable-httpmem.borisinc.com
Grade evidence — probed 2026-07-12 23:00 UTC
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 929ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo memory-mcp@1.28.1 |
| tooling | 35 / 35 | tools/list OK: 4 tools e.g. "memory_write"; 4/4 described, 4/4 fully-typed schemas, median description 140 chars |
| latency | 7 / 10 | initialize round-trip 929ms |
| provenance | 12 / 15 | description present; no repository URL; version 1.0.0; namespace com.borisinc matches endpoint/repo |
Score 94/100 · latency 929ms · 4 tools · auth: open
Connect your agent
Claude Code:
claude mcp add --transport http memory https://mem.borisinc.com/mcp
Generic MCP client config:
{ "mcpServers": { "memory": { "type": "http", "url": "https://mem.borisinc.com/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.borisinc/memory · referral link https://mcpqueen.com/go/com.borisinc/memory (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/com.borisinc/memory)
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-12 23:00 | A | 94 | 929ms |