Epanet MCP Server

epanet-mcp-server PyPI v0.1.2

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

MCP server for EPANET water distribution network simulation via ePyT

Trust grade
A
98/100
Last scanned get badge →
Trust
A · 98/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 98/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 2 = 98. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 5

medium Dynamic module load from a non-literal (src/epanet_mcp/tools/inspection.py)MTC-SRC-005

In the server's implementation (`src/epanet_mcp/tools/inspection.py:98`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: """ sess = registry.require(network_id) d = sess.d return _network_summary(d) def get_nodes(network_id: st

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/epanet_mcp/tools/inspection.py

medium Dynamic module load from a non-literal (src/epanet_mcp/tools/modification.py)MTC-SRC-005

In the server's implementation (`src/epanet_mcp/tools/modification.py:31`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: """ sess = registry.require(network_id) sess.d.saveInputFile(output_path) return {"saved": True, "output_pat

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/epanet_mcp/tools/modification.py

medium Dynamic module load from a non-literal (src/epanet_mcp/tools/scenarios.py)MTC-SRC-005

In the server's implementation (`src/epanet_mcp/tools/scenarios.py:38`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: """ src = registry.require(source_id) tmp = tempfile.NamedTemporaryFile(suffix=".inp", delete=False) tmp.cl

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/epanet_mcp/tools/scenarios.py

medium Dynamic module load from a non-literal (src/epanet_mcp/tools/simulation.py)MTC-SRC-005

In the server's implementation (`src/epanet_mcp/tools/simulation.py:44`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: """ sess = registry.require(network_id) d = sess.d with _simulation_cwd(): ts = d.getComputedHydrau

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/epanet_mcp/tools/simulation.py

low Dynamic module load from a non-literal in packaging/dev tooling (tests/test_modification.py)MTC-SRC-005

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_modification.py:13`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: 1): sess = registry.require(net1) idx = sess.d.getLinkIndex("10") old_d = sess.d.getLinkDiameter(idx) re

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/test_modification.py

Tools 44

Each tool and what it can reach — statically extracted from the published source.

  • add_controlno sensitive capability
  • add_patternno sensitive capability
  • create_contamination_eventno sensitive capability
  • create_demand_perturbationno sensitive capability
  • create_leakage_eventno sensitive capability
  • create_multi_failure_scenariono sensitive capability
  • create_pressure_change_scenariono sensitive capability
  • create_pump_control_scenariono sensitive capability
  • create_valve_control_scenariono sensitive capability
  • delete_controlno sensitive capability
Show 34 more tools ↓
  • get_controlsno sensitive capability
  • get_curvesno sensitive capability
  • get_flow_at_timeno sensitive capability
  • get_linksno sensitive capability
  • get_network_summaryno sensitive capability
  • get_nodesno sensitive capability
  • get_optionsno sensitive capability
  • get_patternsno sensitive capability
  • get_pressure_at_timeno sensitive capability
  • list_bundled_networksno sensitive capability
  • list_networksno sensitive capability
  • load_networkno sensitive capability
  • run_full_simulationno sensitive capability
  • run_hydraulic_simulationno sensitive capability
  • run_quality_simulationno sensitive capability
  • save_networkno sensitive capability
  • set_hydraulic_timestepno sensitive capability
  • set_node_base_demandno sensitive capability
  • set_patternno sensitive capability
  • set_pipe_diameterno sensitive capability
  • set_pipe_lengthno sensitive capability
  • set_pipe_roughnessno sensitive capability
  • set_pipe_statusno sensitive capability
  • set_pump_head_curveno sensitive capability
  • set_pump_speedno sensitive capability
  • set_pump_statusno sensitive capability
  • set_quality_timestepno sensitive capability
  • set_quality_typeno sensitive capability
  • set_reservoir_headno sensitive capability
  • set_simulation_durationno sensitive capability
  • set_tank_parametersno sensitive capability
  • set_valve_settingno sensitive capability
  • set_valve_statusno sensitive capability
  • unload_networkno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.1.2 latest A 98/100 5 1.12.1 2026-07-27

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 98/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/epanet-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/epanet-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/epanet-mcp-server"><img src="https://mcptrustchecker.com/registry/epanet-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/epanet-mcp-server/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan epanet-mcp-server --online --registry pypi

Use the free API → How scoring works

More in Learning & Documentation