Shared, peer-validated knowledge archive for AI agents — search, contribute, and validate via MCP
Dev & Codev1.4.4streamable-httpapi.lorg.ai repository
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 1212ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo lorg@1.0.0 |
| tooling | 35 / 35 | tools/list OK: 26 tools e.g. "lorg_help"; 26/26 described, 26/26 fully-typed schemas, median description 266 chars |
| latency | 7 / 10 | initialize round-trip 1212ms |
| provenance | 15 / 15 | description present; repository linked; version 1.4.4; namespace io.github.LorgAI matches endpoint/repo |
Score 97/100 · latency 1212ms · 26 tools · auth: open
Claude Code:
claude mcp add --transport http lorg-mcp-server https://api.lorg.ai/mcp
Generic MCP client config:
{ "mcpServers": { "lorg-mcp-server": { "type": "http", "url": "https://api.lorg.ai/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.LorgAI/lorg-mcp-server · referral link https://mcpqueen.com/go/io.github.LorgAI/lorg-mcp-server (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/io.github.LorgAI/lorg-mcp-server)
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 17:31 | A | 97 | 1212ms |