Skip to content

endiagram-mcp server

io.github.dushyant30suthar/endiagram-mcpdushyant30sutharstreamable-httpv0.3.16Scanned

EN Diagram — structural verification for concurrent systems. Pure math, no AI.

7 tools: 2 do something that can't be undone and 5 change things.

Tools: 0 delete, 2 irreversible, 5 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here do something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the endiagram-mcp server can do

The endiagram-mcp server is published by the GitHub account dushyant30suthar. It has 7 tools. It can do things that cannot be undone, such as sending, paying or publishing (invariant and reachable) and create or change data (5 tools: structure, live, equivalent, compose and 1 more), but cannot delete data. None of its tools only reads.

1 tool can send data out of your system (reachable).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 19, 2026, version 0.3.16.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Can't be undone 2Claude Code: ask
  • invariantWhat's always true — automatic findings and on-demand checks.No findings

    Why it is in this group

    • The description says "irreversible".
    Description, as the server wrote it
    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.
  • reachableCan X reach Y?Can send data outNo findings

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.
    Description, as the server wrote it
    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.
Changes things 5Claude Code: ask
  • composeHow do parts combine, or how does a part stand alone?No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • equivalentAre two systems the same, or what changes if I change this one?No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • liveCan it deadlock?No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • renderSVG or PNG diagram.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • structureWhat is this system?No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:04 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
7
Protocol version
2025-03-26
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 7 tools that change things (2 irreversible, 5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.endiagram.com/mcp: tools/list returned 7 tools to an anonymous client, including invariant (irreversible), reachable (irreversible), structure (write), live (write), equivalent (write) and 2 more

    What this check looks for

Posture changes

  1. Nov 6, 2026
    • Reachable: no to yes
    • HTTP status of an anonymous initialize: none to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 7
    • Protocol version: none to 2025-03-26
  2. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 7 to 0
    • Protocol version: 2025-03-26 to none

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: no -> yes; HTTP status of an anonymous initialize: none -> 200; tools/list served without credentials: no -> yes (and 2 more).View diff
    • Reachable: no to yes
    • HTTP status of an anonymous initialize: none to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 7
    • Protocol version: none to 2025-03-26
  2. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 2 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 7 to 0
    • Protocol version: 2025-03-26 to none

Install

Pinned to version 0.3.16. Values in angle brackets are yours to fill in.

claude mcp add --transport http endiagram https://api.endiagram.com/mcp
claude mcp add --transport http endiagram https://api.endiagram.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__endiagram__structure",
      "mcp__endiagram__invariant",
      "mcp__endiagram__live",
      "mcp__endiagram__reachable",
      "mcp__endiagram__equivalent",
      "mcp__endiagram__compose",
      "mcp__endiagram__render"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as endiagram. Review it before you use it.

Capability tags behind 1 rule
  • mcp__endiagram__reachable outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.dushyant30suthar/endiagram-mcp/verify?hash=81418b711bf1960e74539123bd938244ab837e890e834b48ebee0dbaaf78468f" | jq -e '.changed == false'

Pinned hash 81418b711bf1, from Nov 19, 2026, 14:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.dushyant30suthar/endiagram-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.dushyant30suthar/endiagram-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.dushyant30suthar/endiagram-mcp.svg)](https://radar.anlyon.com/servers/io.github.dushyant30suthar/endiagram-mcp)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:33 UTC.

endiagram-mcp server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the endiagram-mcp server safe?

No scan can promise that. What its definitions show: 7 tools, 7 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the endiagram-mcp server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the endiagram-mcp server do things that cannot be undone?

Yes. 2 tools can send, pay, publish or merge: invariant and reachable.

What tools does the endiagram-mcp server have?

7 tools: 2 irreversible, 5 write. invariant, reachable, structure, live, equivalent, compose and render.

Does the endiagram-mcp server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the endiagram-mcp server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): reachable.

Has the endiagram-mcp server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.