Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

EPANET MCP Server

PYPI · EPANET-MCP-SERVER

MCP server for EPANET water-distribution network simulation and scenario analysis.

Available components

+13 this week 62 Trust /100

Last scanned (19 hours ago)

Scores higher than 54% of PyPI servers

Category IoT and Hardware

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 5 of 76 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to Applied-Artificial-Intelligence-Eurecat/epanet-mcp-server). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 3910 tokens (~86/item across 45 items; 45 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_control" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 46 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (15)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
    • Stability: unverified → 0.03 ▲ functional
    • Package version: 1.0.1 → 1.0.2 functional
  • 17 Nov 26 +11
    • Malware scan: pass → unverified ▼ security
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • First check of Tool coverage: 0 functional
    • First check of Schema quality: fail functional
    • First check of Destructive annotations: 0 functional
    • First check of Schema quality: pass functional
    • First check of Schema quality: good functional
    • First check of Tool coverage: 100 functional
    • Package version: 1.0.0 → 1.0.1 functional
  • 16 Nov 26 0
    • Package version: 0.2.0 → 1.0.0 functional
  • 14 Nov 26 0
    • Stability: Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare. security
    • Tool safety: Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan. security
    • Schema quality: Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess. functional
    • Capabilities: Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake. functional
    • Tool coverage: Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess. functional
  • 13 Nov 26 +10
    • Provenance: fail → pass ▲ security
    • Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • The attested source repository moved: Applied-Artificial-Intelligence-Eurecat/epanet-mcp-server security
    • Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
    • Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Package version: 0.1.2 → 0.2.0 functional
  • 7 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
Diagnostics

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 21 Nov 2026 · Analysed pypi/epanet-mcp-server@1.0.2

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo Applied-Artificial-Intelligence-Eurecat/epanet-mcp-server
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Applied-Artificial-Intelligence-Eurecat/epanet-mcp-server/.github/workflows/publish.yml@refs/tags/v1.0.2
Rekor log index 3967174171
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:e5235275d9366c44096e846bec07abba4e6435935760e0d90b77cee198a9387e

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 76 packages
Packages resolved 76
Stale 5
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 45 exposed · ~3,863 tokens

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 →

Tool Tokens
add_control ~101

Add a new simple control rule. Example control strings:: "LINK P1 CLOSED IF NODE T1 ABOVE 20" "LINK P1 OPEN IF NODE J2 BELOW 10" "LINK Pump9 1.5 AT TIME 16:00" Args: network_id: Session id. control_string: EPANET simple-control syntax string.

NameTypeReqDescription
control_stringstringyes–
network_idstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

add_pattern ~75

Add a new demand / operational pattern to the network. Args: network_id: Session id. pattern_id: Unique name for the new pattern. values: Multiplier values for consecutive pattern time steps.

NameTypeReqDescription
network_idstringyes–
pattern_idstringyes–
valuesarrayyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

create_contamination_event ~259

Inject a contaminant at a node for a specified time window and simulate. A clone of the source network is created. Quality type is set to CHEM automatically. Args: network_id: Source network id. source_node_id: Node where the contaminant is introduced. concentration: Concentration in mg/L (or model quality units). start_time_s: Injection start time in seconds. end_time_s: Injection end time in seconds. source_type: ``"CONCEN"``, ``"MASS"``, ``"FLOWPACED"``, or ``"SETPOINT"``. scenario_id: Id for the cloned scenario session. run_simulation: Run a full simulation after applying changes. chemical_name: Chemical species name. units: Chemical quality units.

NameTypeReqDescription
chemical_namestring––
concentrationnumberyes–
end_time_sintegeryes–
network_idstringyes–
run_simulationboolean––
scenario_id–––
source_node_idstringyes–
source_typestring––
start_time_sintegeryes–
unitsstring––
NameTypeReqDescription
resultobjectyes–

No examples provided.

create_demand_perturbation ~150

Apply base-demand multipliers to a set of nodes and optionally simulate. A clone of the source network is created; the original is unchanged. Args: network_id: Source network id. node_demands: ``{node_id: multiplier}`` — e.g. ``{"J1": 2.0}`` doubles demand at J1. scenario_id: Id for the cloned scenario session (auto-generated if omitted). run_simulation: Run a full simulation after applying changes.

NameTypeReqDescription
network_idstringyes–
node_demandsobjectyes–
run_simulationboolean––
scenario_id–––
NameTypeReqDescription
resultobjectyes–

No examples provided.

create_leakage_event ~226

Simulate a pipe burst by adding a leakage emitter at the pipe midpoint. A clone of the source network is created; the original is unchanged. The burst pipe is split into two halves and a midpoint junction node with an emitter is added. Args: network_id: Source network id. pipe_id: Id of the pipe that bursts. leak_fraction: Optional fraction of baseline mean pipe flow (0.0–1.0). scenario_id: Id for the cloned scenario session. run_simulation: Run a full simulation after applying changes. target_leak_flow: Optional target flow in the model's flow units. reference_pressure: Pressure at which the target flow applies. emitter_exponent: Pressure exponent; defaults to the model option.

NameTypeReqDescription
emitter_exponent–––
leak_fraction–––
network_idstringyes–
pipe_idstringyes–
reference_pressure–––
run_simulationboolean––
scenario_id–––
target_leak_flow–––
NameTypeReqDescription
resultobjectyes–

No examples provided.

create_multi_failure_scenario ~132

Simulate simultaneous pipe and/or pump failures (closure). A clone of the source network is created; the original is unchanged. Args: network_id: Source network id. failed_pipes: List of pipe ids to close. failed_pumps: List of pump ids to close. scenario_id: Id for the cloned scenario session. run_simulation: Run a full simulation after applying changes.

NameTypeReqDescription
failed_pipes–––
failed_pumps–––
network_idstringyes–
run_simulationboolean––
scenario_id–––
NameTypeReqDescription
resultobjectyes–

No examples provided.

create_pressure_change_scenario ~130

Study pressure changes by modifying reservoir heads. A clone of the source network is created; the original is unchanged. Args: network_id: Source network id. reservoir_heads: ``{reservoir_id: new_head}`` — e.g. ``{"Reservoir1": 120.0}``. scenario_id: Id for the cloned scenario session. run_simulation: Run a full simulation after applying changes.

NameTypeReqDescription
network_idstringyes–
reservoir_headsobjectyes–
run_simulationboolean––
scenario_id–––
NameTypeReqDescription
resultobjectyes–

No examples provided.

create_pump_control_scenario ~180

Apply a time-based pump on/off or speed schedule and simulate. A clone of the source network is created; the original is unchanged. Each pump entry maps to a list of EPANET simple-control strings:: { "Pump9": [ "LINK Pump9 1.0 AT TIME 06:00", "LINK Pump9 CLOSED AT TIME 22:00" ] } Args: network_id: Source network id. pump_schedule: ``{pump_id: [control_string, ...]}`` schedule. scenario_id: Id for the cloned scenario session. run_simulation: Run a full simulation after applying changes.

NameTypeReqDescription
network_idstringyes–
pump_scheduleobjectyes–
run_simulationboolean––
scenario_id–––
NameTypeReqDescription
resultobjectyes–

No examples provided.

create_valve_control_scenario ~116

Apply static valve-setting changes and simulate. A clone of the source network is created; the original is unchanged. Args: network_id: Source network id. valve_settings: ``{valve_id: new_setting}`` map. scenario_id: Id for the cloned scenario session. run_simulation: Run a full simulation after applying changes.

NameTypeReqDescription
network_idstringyes–
run_simulationboolean––
scenario_id–––
valve_settingsobjectyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

delete_control ~63

Delete a simple control by its 1-based index. Args: network_id: Session id. control_index: 1-based index (use ``get_controls`` to list them).

NameTypeReqDescription
control_indexintegeryes–
network_idstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

get_controls ~40

Return all simple controls defined in the network. Args: network_id: Session id of the network to inspect.

NameTypeReqDescription
network_idstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

get_curves ~49

Return all curves (pump head, efficiency, volume, valve) in the network. Args: network_id: Session id of the network to inspect.

NameTypeReqDescription
network_idstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

get_flow_at_time ~62

Return link flows at (or nearest to) a specific simulation time. Args: network_id: Session id of the network. time_s: Simulation time in seconds.

NameTypeReqDescription
network_idstringyes–
time_sintegeryes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

get_links ~67

Return all links (pipes, pumps, valves) with their attributes. Attributes include type, connected nodes, diameter, length, roughness coefficient, and minor loss coefficient. Args: network_id: Session id of the network to inspect.

NameTypeReqDescription
network_idstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

get_network_summary ~58

Return a high-level summary of a loaded network. Includes node/link counts, flow units, simulation duration and hydraulic timestep. Args: network_id: Session id of the network to inspect.

NameTypeReqDescription
network_idstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

get_nodes ~70

Return all nodes (junctions, tanks, reservoirs) with their attributes. Attributes include elevation, base demand, and type. Tanks also include min/max/initial water levels and diameter. Args: network_id: Session id of the network to inspect.

NameTypeReqDescription
network_idstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

get_options ~52

Return simulation options: timesteps, units, quality settings, head-loss formula, and demand model. Args: network_id: Session id of the network to inspect.

NameTypeReqDescription
network_idstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

get_patterns ~42

Return all demand / operational patterns defined in the network. Args: network_id: Session id of the network to inspect.

NameTypeReqDescription
network_idstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

get_pressure_at_time ~73

Return node pressures at (or nearest to) a specific simulation time. Args: network_id: Session id of the network. time_s: Simulation time in seconds (e.g. 3600 = 1 hour).

NameTypeReqDescription
network_idstringyes–
time_sintegeryes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

list_bundled_networks ~30

List every .inp example file bundled with ePyT (usable with load_network).

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultobjectyes–

No examples provided.

list_networks ~19

Return the ids of all currently loaded networks.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultobjectyes–

No examples provided.

load_network ~123

Load an EPANET .inp file into a named session. Args: path: Absolute file path, relative path, or bare filename (e.g. ``"Net1.inp"``) searched in ePyT's bundled networks. network_id: Optional human-readable session identifier. Defaults to the file's base name without extension. Returns: ``network_id``, ``path``, and a network summary (node/link counts, flow units, simulation duration).

NameTypeReqDescription
network_id–––
pathstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

run_full_simulation ~60

Run both hydraulic and water-quality simulations and return combined time-series results (pressures, flows, quality, reaction rates, etc.). Args: network_id: Session id of the network to simulate.

NameTypeReqDescription
network_idstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

run_hydraulic_simulation ~70

Run a full hydraulic simulation and return time-series results. Returns pressures, demands, heads, flows, velocities, head-losses and link statuses at every reporting time step. Args: network_id: Session id of the network to simulate.

NameTypeReqDescription
network_idstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

run_quality_simulation ~66

Run a full water-quality simulation and return time-series results. Includes node/link quality concentrations plus all hydraulic results. Configure the quality type first with ``set_quality_type``. Args: network_id: Session id of the network to simulate.

NameTypeReqDescription
network_idstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

save_network ~70

Save the current (possibly modified) network to a new .inp file. Args: network_id: Session id of the network to save. output_path: Destination file path (should end in ``.inp``).

NameTypeReqDescription
network_idstringyes–
output_pathstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

set_hydraulic_timestep ~54

Set the hydraulic time step. Args: network_id: Session id. timestep_s: Hydraulic time step in seconds.

NameTypeReqDescription
network_idstringyes–
timestep_sintegeryes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

set_node_base_demand ~96

Set the base demand for a junction node. Args: network_id: Session id. node_id: Junction node name/ID. demand: New base demand in the network's flow units. demand_category: Demand category index (default 1).

NameTypeReqDescription
demandnumberyes–
demand_categoryinteger––
network_idstringyes–
node_idstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

set_pattern ~70

Overwrite all multiplier values for a named demand pattern. Args: network_id: Session id. pattern_id: Name of an existing pattern. values: New list of multiplier values.

NameTypeReqDescription
network_idstringyes–
pattern_idstringyes–
valuesarrayyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

set_pattern_timestep ~37

Set the demand and quality-source pattern timestep in seconds.

NameTypeReqDescription
network_idstringyes–
timestep_sintegeryes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

set_pipe_diameter ~75

Set the diameter of a pipe. Args: network_id: Session id. pipe_id: Pipe name/ID. diameter: New diameter in the network's length units (mm or inches).

NameTypeReqDescription
diameternumberyes–
network_idstringyes–
pipe_idstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

set_pipe_length ~74

Set the length of a pipe. Args: network_id: Session id. pipe_id: Pipe name/ID. length: New length in the network's length units (feet or metres).

NameTypeReqDescription
lengthnumberyes–
network_idstringyes–
pipe_idstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

set_pipe_roughness ~83

Set the roughness coefficient of a pipe. Args: network_id: Session id. pipe_id: Pipe name/ID. roughness: Hazen-Williams C factor (or Darcy-Weisbach roughness height).

NameTypeReqDescription
network_idstringyes–
pipe_idstringyes–
roughnessnumberyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

set_pipe_status ~72

Open or close a pipe. Args: network_id: Session id. pipe_id: Pipe name/ID. status: ``"OPEN"`` or ``"CLOSED"``.

NameTypeReqDescription
network_idstringyes–
pipe_idstringyes–
statusstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

set_pump_head_curve ~97

Set (replace) the head-flow curve of a pump. Args: network_id: Session id. pump_id: Pump link name/ID. flow_values: X-axis (flow) values. head_values: Y-axis (head) values.

NameTypeReqDescription
flow_valuesarrayyes–
head_valuesarrayyes–
network_idstringyes–
pump_idstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

set_pump_speed ~83

Set the relative speed setting of a pump. Args: network_id: Session id. pump_id: Pump link name/ID. speed: Speed ratio (1.0 = design speed, 0.5 = half speed).

NameTypeReqDescription
network_idstringyes–
pump_idstringyes–
speednumberyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

set_pump_status ~81

Start or stop a pump. Args: network_id: Session id. pump_id: Pump link name/ID. status: ``"OPEN"`` (running) or ``"CLOSED"`` (stopped).

NameTypeReqDescription
network_idstringyes–
pump_idstringyes–
statusstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

set_quality_timestep ~54

Set the water-quality simulation time step. Args: network_id: Session id. timestep_s: Quality time step in seconds.

NameTypeReqDescription
network_idstringyes–
timestep_sintegeryes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

set_quality_type ~130

Set the water-quality analysis type. Args: network_id: Session id. quality_type: One of ``"NONE"``, ``"AGE"``, ``"TRACE"``, or ``"CHEM"``. tracer_node: Source node for ``TRACE`` analysis. chemical_name: Species name for ``CHEM`` analysis. units: Concentration units (e.g. ``"mg/L"``).

NameTypeReqDescription
chemical_name–––
network_idstringyes–
quality_typestringyes–
tracer_node–––
units–––
NameTypeReqDescription
resultobjectyes–

No examples provided.

set_reservoir_head ~82

Set the total head (water-surface elevation) of a reservoir. Args: network_id: Session id. reservoir_id: Reservoir node name/ID. head: Total head value in the network's pressure-head units.

NameTypeReqDescription
headnumberyes–
network_idstringyes–
reservoir_idstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

set_simulation_duration ~61

Set the total simulation duration. Args: network_id: Session id. duration_s: Duration in seconds (e.g. 86400 = 24 h).

NameTypeReqDescription
duration_sintegeryes–
network_idstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

set_tank_parameters ~123

Update one or more parameters of a tank node. Only provided parameters are changed; others retain their current values. Args: network_id: Session id. tank_id: Tank node name/ID. initial_level: Water level at simulation start. min_level: Minimum operating level. max_level: Maximum operating level. diameter: Tank diameter.

NameTypeReqDescription
diameter–––
initial_level–––
max_level–––
min_level–––
network_idstringyes–
tank_idstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

set_valve_setting ~92

Set the initial setting of a valve. PRV/PSV/PBV → pressure setpoint; FCV → flow rate; TCV → loss coefficient. Args: network_id: Session id. valve_id: Valve link name/ID. setting: New setting value.

NameTypeReqDescription
network_idstringyes–
settingnumberyes–
valve_idstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

set_valve_status ~74

Open or close a valve. Args: network_id: Session id. valve_id: Valve link name/ID. status: ``"OPEN"`` or ``"CLOSED"``.

NameTypeReqDescription
network_idstringyes–
statusstringyes–
valve_idstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

unload_network ~42

Unload a previously loaded network and free its resources. Args: network_id: The session id returned by ``load_network``.

NameTypeReqDescription
network_idstringyes–
NameTypeReqDescription
resultobjectyes–

No examples provided.

Install

How do I install the EPANET MCP Server server?

EPANET MCP Server runs locally as a PyPI package, launched with uvx epanet-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · epanet-mcp-server

# add to Claude Code
claude mcp add applied-artificial-intelligence-eurecat-epanet-m -- uvx epanet-mcp-server
Common questions

What is the EPANET MCP Server server?

EPANET MCP Server is listed in the public MCP registry as io.github.Applied-Artificial-Intelligence-Eurecat/epanet-mc…. MCP server for EPANET water-distribution network simulation and scenario analysis. This page covers its PyPI package (epanet-mcp-server).

Is the EPANET MCP Server server safe to use?

EPANET MCP Server scores 62 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. 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 EPANET MCP Server server expose?

EPANET MCP Server exposes 45 tools: load_network, unload_network, list_networks, list_bundled_networks, get_network_summary, and 40 more. Their descriptions and schemas cost roughly 3,863 tokens of context every time the server is loaded.

Is the EPANET MCP Server server still maintained?

EPANET MCP Server is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the EPANET MCP Server server under?

EPANET MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the EPANET MCP Server server?

VerifyMCP ran 15 checks on EPANET MCP Server, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about EPANET MCP Server: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.