Cultural color intelligence. Every colour anchored to a person, a year, and a consequence.
Dev & Codev2.0.0streamable-httpcolour-memory-api-production.up.railway.app repository
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 1545ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-11-25, serverInfo colour-memory@2.3.4 |
| tooling | 35 / 35 | tools/list OK: 71 tools e.g. "query_conceptual"; 71/71 described, 71/71 fully-typed schemas, median description 406 chars |
| latency | 4 / 10 | initialize round-trip 1545ms |
| provenance | 15 / 15 | description present; repository linked; version 2.0.0; namespace io.github.DigbyO matches endpoint/repo |
Score 94/100 · latency 1545ms · 71 tools · auth: open
Claude Code:
claude mcp add --transport http colour-memory https://colour-memory-api-production.up.railway.app/mcp
Generic MCP client config:
{ "mcpServers": { "colour-memory": { "type": "http", "url": "https://colour-memory-api-production.up.railway.app/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.DigbyO/colour-memory · referral link https://mcpqueen.com/go/io.github.DigbyO/colour-memory (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/io.github.DigbyO/colour-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.
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 | 94 | 1545ms |