MCP server for EPANET water-distribution network simulation and scenario analysis.
A Model Context Protocol (MCP) server that exposes EPANET water-distribution network modelling capabilities through ePyT - the EPANET Python Toolkit. Any MCP-compatible LLM can load water network models, run simulations, modify parameters, and generate complex what-if scenarios through Load & Inspect | , , , , , , , , , , | Simulate | , , , , | Modify | , , , , , , , , , , , , , , , , , , , , |…
Inferred from the transports this listing declares (stdio). 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 0 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”.
A Model Context Protocol (MCP) server that exposes EPANET water-distribution network modelling capabilities through ePyT - the EPANET Python Toolkit. Any MCP-compatible LLM can load water network models, run simulations, modify parameters, and generate complex what-if scenarios through Load & Inspect | , , , , , , , , , , | Simulate | , , , , | Modify | , , , , , , , , , , , , , , , , , , , , | Scenarios | , , , , , , | (macOS) or the equivalent on your platform: Place this in the root of your…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.