io.github.dushyant30suthar/endiagram-mcp
REMOTE · API.ENDIAGRAM.COM · 2 COMPONENTS · SCANNED SEP 22
EN Diagram — structural verification for concurrent systems. Pure math, no AI.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2269 tokens (~324/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.dushyant30suthar/endiagram-mcp server?
io.github.dushyant30suthar/endiagram-mcp is a hosted endpoint at https://api.endiagram.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.endiagram.com
claude mcp add --transport http dushyant30suthar-endiagram-mcp 'https://api.endiagram.com/mcp'
{
"mcpServers": {
"dushyant30suthar-endiagram-mcp": {
"url": "https://api.endiagram.com/mcp"
}
}
} {
"servers": {
"dushyant30suthar-endiagram-mcp": {
"type": "http",
"url": "https://api.endiagram.com/mcp"
}
}
} [mcp_servers.dushyant30suthar-endiagram-mcp] url = "https://api.endiagram.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dushyant30suthar-endiagram-mcp": {
"type": "remote",
"url": "https://api.endiagram.com/mcp",
"enabled": true
}
}
} openclaw mcp add dushyant30suthar-endiagram-mcp --url 'https://api.endiagram.com/mcp' --transport streamable-http
mcp_servers:
dushyant30suthar-endiagram-mcp:
url: "https://api.endiagram.com/mcp" {
"McpServers": {
"dushyant30suthar-endiagram-mcp": {
"Transport": "http",
"Url": "https://api.endiagram.com/mcp"
}
}
} assistant mcp add dushyant30suthar-endiagram-mcp -t streamable-http -u 'https://api.endiagram.com/mcp'
{
"mcpServers": {
"dushyant30suthar-endiagram-mcp": {
"type": "http",
"url": "https://api.endiagram.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Sept 26 0
- Stability: 0.97 → pass security
- 3 Sept 26 0
- Stability: pass → 0.97 functional
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Aug 26 0
- DNSSEC: unverified → fail ▼ security
- HSTS header: unverified → fail ▼ security
- TLS certificate: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Stability: unverified → 0.33 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 4 Aug 26 0
- TLS certificate: pass → unverified ▼ security
- Stability: 0.27 → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- DNSSEC: fail → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- First check of Schema quality: unverified functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Sept 2026 · Probed https://api.endiagram.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=endiagram.com | CN=YE1,O=Let's Encrypt,C=US | 5 Sept 2026 | 4 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 56e43cb5a3bce21b4feccb9cb1417611c5c |
| SANs: *.endiagram.com, endiagram.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.endiagram.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| endiagram.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.endiagram.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.endiagram.com/mcp | HTTPS enforced | 301 | https://api.endiagram.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compose ~265
How do parts combine, or how does a part stand alone? Merge mode (source_a + source_b + links): declare which entities in A are the same as entities in B; the combined graph is wired via string-equality of shared names. Extract mode (source + subsystem): pull a named subsystem out as standalone EN with boundary inputs/outputs, actors, and locations. Valid subsystem names come from structure's `subsystems` field — call structure on the source first to discover them. See the server instructions for EN language syntax.
| Name | Type | Req | Description |
|---|---|---|---|
| links | string | – | Entity identifications, one per line. Format: `a.<entity name>=b.<entity name>` (A's entity is the same as B's entity). `#` starts a comment. Example: `a.user session=b.authenticated session`. |
| source | string | – | EN source code for extract mode |
| source_a | string | – | EN source code or path to .en/.txt file for the first system |
| source_b | string | – | EN source code or path to .en/.txt file for the second system |
| subsystem | string | – | Subsystem name to extract. Valid names come from structure's `subsystems` field — call structure on the source first to discover them. |
No output schema declared.
No examples provided.
equivalent ~282
Are two systems the same, or what changes if I change this one? Compare mode (source_a + source_b): structural differences, edit distance, spectral equivalence. isCospectral=true means identical graph structure up to relabeling — topologically the same despite different names, actors, or locations. Evolve mode (source + patch): dry-run a change, shows diff plus new/lost bridge nodes. Patch has three directive types — plain EN statement adds an action; a line starting with `-` (and not containing `do:`) removes the named action; a statement whose action name matches an existing one replaces the original. See the server instructions for EN language syntax.
| Name | Type | Req | Description |
|---|---|---|---|
| patch | string | – | EN patch for evolve mode. Three directive types: plain EN statement (`actor do: X needs: Y yields: Z at: W`) adds action X; a line starting with `-` (and not containing `do:`) removes the named actio… |
| source | string | – | EN source code for evolve mode |
| source_a | string | – | EN source code or path to .en/.txt file for the first system |
| source_b | string | – | EN source code or path to .en/.txt file for the second system |
No output schema declared.
No examples provided.
invariant ~320
What's always true — automatic findings and on-demand checks. Automatic outputs: conservationLaws (weighted entity sums constant across executions), sustainableCycles (T-invariants — action sequences returning to start state), depletableSets (entity groups whose simultaneous depletion is irreversible), behavioral.deficiency (0 means structure fully determines dynamics), behavioral.isReversible, behavioral.hasUniqueEquilibrium. On-demand via `rules`: encode domain-specific claims and verify them against the graph — this is how to check things the topology alone can't see (precedence, coverage, centrality bounds, resilience). See the rules parameter for supported sentence shapes.
| Name | Type | Req | Description |
|---|---|---|---|
| rules | string | – | Custom structural rules, one per line. Four supported sentence shapes (regex-matched): (1) `no bridge that is also hub` — flags nodes that are both a bridge and a hub. (2) `every path from X to Y pas… |
| source | string | yes | EN source code, or path to .en/.txt file |
No output schema declared.
No examples provided.
live ~107
Can it deadlock? Can entities overflow? isStructurallyLive means every siphon contains a trap — no structural deadlock possible. uncoveredSiphons are entity groups that can drain permanently, with the actors and locations affected. isStructurallyBounded means no entity can accumulate without limit. unboundedCycles are action sequences that could cause overflow. See the server instructions for EN language syntax.
| Name | Type | Req | Description |
|---|---|---|---|
| source | string | yes | EN source code, or path to .en/.txt file |
No output schema declared.
No examples provided.
reachable ~135
Can X reach Y? Follows directed data flow first; falls back to undirected. `from` and `to` accept entity names or action names (resolved against the program). Path shows each step with actor and location. locationCrossings counts boundary transitions. defense_nodes checks if guards cover all paths; coverage.fullCoverage=false means unguarded routes exist. See the server instructions for EN language syntax.
| Name | Type | Req | Description |
|---|---|---|---|
| defense_nodes | string | – | Comma-separated guard nodes to check coverage |
| from | string | yes | Starting node name |
| source | string | yes | EN source code |
| to | string | yes | Target node name |
No output schema declared.
No examples provided.
render ~432
SVG or PNG diagram. Only call when user explicitly asks to visualize. The rendered image is delivered to the user, not injected into the model's context. See the server instructions for EN language syntax.
| Name | Type | Req | Description |
|---|---|---|---|
| color | string | – | Seed color hex (#RRGGBB) to generate a custom theme. Overrides theme parameter. One color generates the entire palette. |
| direction | string | – | Layout direction: LR (left-to-right) or TB (top-to-bottom). Default auto-detects from condensation DAG aspect ratio. |
| isDark | string | – | true or false. Selects the dark or light variant of a named preset. If omitted, defaults to dark unless theme=light. |
| output | string | – | File path to save the rendered image |
| quality | string | – | Output quality: small, mid, or max |
| source | string | yes | EN source code, or path to .en/.txt file |
| structure_layers | string | – | Bitmask for structure overlays. Bits: 1=subsystems, 2=pipelines, 4=cycles, 8=forks, 16=joins, 32=hubs, 64=deadlock, 128=overflow. Default 255 (all on). Pass 0 to hide all. |
| theme | string | – | Color theme. Curated presets (each with light + dark variants; pair with `isDark`): `Editorial` (stone paper + rust focal, adapted from cathrynlavery/diagram-design), `Primer` (GitHub design system —… |
| type | string | – | Output format: png (default) or svg. PNG is rasterized server-side via Batik. |
| view | string | – | Group by: actors (partition by actor) or locations (partition by location). Default auto-detects topology. |
No output schema declared.
No examples provided.
structure ~266
What is this system? Returns shape (Pipeline, Fork-Join, DAG, Star, Cycle, Tree, Complete, etc.), stages with roles, bridge nodes, cycles, parallelism, critical path, dominator tree, min-cuts, subsystems, interface nodes, actors (who does what, workload entropy), locations (where work happens, boundary crossings). Levers: node=X returns per-node centrality (betweenness, closeness, eigenvector) for a specific node. detect_findings=true flags named structural risks — unguarded-sink (sinks reachable via only pipeline actions, no JOIN/HUB gating), single-cut-path (source-sink pairs with only one vertex-disjoint path), multi-cut-path (paths with redundant defense, min-cut > 1). See server instructions for EN language syntax.
| Name | Type | Req | Description |
|---|---|---|---|
| detect_findings | string | – | Set to 'true' to flag named structural findings. Possible values: unguarded-sink, single-cut-path, multi-cut-path. |
| node | string | – | Node name. When provided, returns per-node centrality (betweenness, closeness, eigenvector) for this specific node instead of the overview. |
| source | string | yes | EN source code, or path to .en/.txt file |
No output schema declared.
No examples provided.
What is the io.github.dushyant30suthar/endiagram-mcp server?
io.github.dushyant30suthar/endiagram-mcp is listed in the public MCP registry as io.github.dushyant30suthar/endiagram-mcp. EN Diagram, structural verification for concurrent systems. Pure math, no AI. This page covers its hosted endpoint (https://api.endiagram.com/mcp).
Is the io.github.dushyant30suthar/endiagram-mcp server safe to use?
io.github.dushyant30suthar/endiagram-mcp scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.dushyant30suthar/endiagram-mcp server expose?
io.github.dushyant30suthar/endiagram-mcp exposes 7 tools: structure, invariant, live, reachable, equivalent, and 2 more. Their descriptions and schemas cost roughly 1,807 tokens of context every time the server is loaded.
Does the io.github.dushyant30suthar/endiagram-mcp server require authentication?
No. We connected to io.github.dushyant30suthar/endiagram-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.dushyant30suthar/endiagram-mcp server still maintained?
io.github.dushyant30suthar/endiagram-mcp is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.