EN Diagram — structural verification for concurrent systems. Pure math, no AI.
MCP server for EN Diagram — deterministic structural analysis powered by graph theory. Every result is backed by a named mathematical theorem. No AI inside the computation. Add to in your project root: Any MCP client that supports HTTP transport: Variable | Default | Description | ----------|---------|-------------| | | API endpoint for the EN Diagram service | Six questions about any system,…
Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 2 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
MCP server for EN Diagram — deterministic structural analysis powered by graph theory. Every result is backed by a named mathematical theorem. No AI inside the computation. Add to in your project root: Any MCP client that supports HTTP transport: Variable | Default | Description | ----------|---------|-------------| | | API endpoint for the EN Diagram service | Six questions about any system, plus a render tool. Every tool takes (EN code or / file path). Tool names are shorthand, not specs —…
This package was last scanned before Forge began storing the resolved tree. The next scan will record it.