Industrial-AIOps runs on your own machine — the client starts it, so there is no endpoint to ping. 1 333 installs a week from pypi. Last commit 16 Sep 2026.
Governed OT data tap: 14 field protocols + cross-protocol RCA brain; audit + MOC gating.
We read the source, 20 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
proc = subprocess.run( # nosec B603 — fixed argv, shell=False, no interpolation
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add iaiops -- uvx iaiops
{
"mcpServers": {
"iaiops": {
"args": [
"iaiops"
],
"command": "uvx"
}
}
}
[mcp_servers.iaiops]
command = "uvx"
args = ["iaiops"]
{
"mcpServers": {
"iaiops": {
"args": [
"iaiops"
],
"command": "uvx"
}
}
}
{
"mcpServers": {
"iaiops": {
"args": [
"iaiops"
],
"command": "uvx"
}
}
}
This one needs environment variables set before it will start:
IAIOPS_MCP (Tool-menu selection: comma-separated protocols or a named profile (e.g. 'fab', 'process', 'building', 'opcua,modbus'). No default since 0.10.0 — unset prints the selection menu and exits; set to a profile name (e.g. factory) or comma-list of protocols.), IAIOPS_CONFIG (Path to the endpoints config YAML (default: ~/.iaiops/config.yaml).), IAIOPS_MASTER_PASSWORD (Master password unlocking the encrypted secret store (~/.iaiops/secrets.enc).), IAIOPS_NO_EGRESS (Set to 1 to withhold every data-shipping tool (message bus, external historian, remote LLM) from list_tools() at registration time, for an airgap/sealed-box deployment. This is a data-exfiltration axis only, not read/write authorisation — whether a write is allowed is the caller's decision, and every call (read or write) is audited. Gates MCP tools only — not a firewall.).
The author declared them in the registry entry; get the values from the project itself.
DeFi protocol data: TVL, yield pools, and cross-chain analytics
Governed GPU inference ops (vLLM + Ray Serve): latency RCA, scaling, drain, 39 tools.
Governed MinIO ops: capacity RCA, exposure audit, ILM, WORM retention, IAM, healing, 48 tools.
Governed Cisco Meraki fabric ops: uplink RCA, health score, drift; 34 tools with audit/undo.
Governed Proxmox VE VM/container ops — 43 MCP tools with audit, budget, undo & risk-tier guards.
FIX trading-protocol bridge — parse, map, govern (MiFID II / MAR).
Governed OPNsense + pfSense firewall ops: rules, NAT, VPN, DHCP, RCA. 35 tools.
Governed Ceph mgr ops: HEALTH_WARN RCA, OSD/PG/pool/RBD/CephFS/RGW, 37 tools.
Answers built from our own checks of this server.