Intelligent context infrastructure for AI teams: knowledge graph, sessions, tasks, documents.
Dev & Codev0.1.0streamable-httpapi.dotnova.io repository
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 1345ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo rmcp@1.1.0 |
| tooling | 34 / 35 | tools/list OK: 62 tools e.g. "accept_org_invite"; 62/62 described, 56/62 fully-typed schemas, median description 97 chars |
| latency | 7 / 10 | initialize round-trip 1345ms |
| provenance | 15 / 15 | description present; repository linked; version 0.1.0; namespace io.github.DotNova matches endpoint/repo |
Score 96/100 · latency 1345ms · 62 tools · auth: open
Claude Code:
claude mcp add --transport http context-layer https://api.dotnova.io/mcp
Generic MCP client config:
{ "mcpServers": { "context-layer": { "type": "http", "url": "https://api.dotnova.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.DotNova/context-layer · referral link https://mcpqueen.com/go/io.github.DotNova/context-layer (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/io.github.DotNova/context-layer)
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-13 15:16 | A | 96 | 1345ms |