EN Diagram — structural verification for concurrent systems. Pure math, no AI.
Dev & Codev0.3.16streamable-httpapi.endiagram.com repository
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 526ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-03-26, serverInfo endiagram@0.2.1 |
| tooling | 35 / 35 | tools/list OK: 7 tools e.g. "structure"; 7/7 described, 7/7 fully-typed schemas, median description 521 chars |
| latency | 7 / 10 | initialize round-trip 526ms |
| provenance | 15 / 15 | description present; repository linked; version 0.3.16; namespace io.github.dushyant30suthar matches endpoint/repo |
Score 97/100 · latency 526ms · 7 tools · auth: open
Claude Code:
claude mcp add --transport http endiagram-mcp https://api.endiagram.com/mcp
Generic MCP client config:
{ "mcpServers": { "endiagram-mcp": { "type": "http", "url": "https://api.endiagram.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/io.github.dushyant30suthar/endiagram-mcp · referral link https://mcpqueen.com/go/io.github.dushyant30suthar/endiagram-mcp (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/io.github.dushyant30suthar/endiagram-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 00:30 | A | 97 | 526ms |