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.

myIO

NPM · MYIO-MCP

Read and control a myIO smart home controller: heating, lighting, blinds and energy.

Available components

+18 this week 66 Trust /100

Last scanned (20 hours ago)

Scores higher than 38% of npm 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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability75
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 17593 tokens (~135/item across 130 items; 102 tools + 28 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage77
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 32% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 104 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 (16)

  • Malware scan
  • 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

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.

  • 20 Nov 26 +1

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

  • 18 Nov 26 +1

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

  • 16 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.

  • 15 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
    • Stability: unverified → 0.03 ▲ functional
    • Package version: 1.6.1 → 1.6.2 functional
  • 14 Nov 26 48

    First indexed and scored.

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 npm/myio-mcp@1.6.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 102 exposed · ~15,466 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
myio_alarm ~121

The alarm panel receiver (GIGA/Opta 4.5.8+, SIA DC-09 over TCP/UDP): enabled, listeners, frame counters, troubles (AC, battery, tamper, communication, zone, supervision), per-partition state (disarmed / partial / armed / ALARM) with the last event code, zone and user, and the universal sensor each partition feeds. Monitoring only (no arming). Editor/admin level.

NameTypeReqDescription
serverstring–controller name (default 192.168.1.170)

No output schema declared.

No examples provided.

myio_alarm_set ~228

Change the SIA receiver (saved with AlarmSave): enabled, tcp, udp, ack_timestamp (desired values), port 1024..49151 (not 80/843), account (max 32), supervision_min 0..1440, partition_sensor {partition 1.., usens (0 = none)}. simulate = a DC-03 test event like "Nri1/BA01" (burglary alarm partition 1 zone 1) - drives the partition state and its usens; reset_counters=true. TCP on/off takes effect after a restart. Editor/admin level.

NameTypeReqDescription
accountstring––
ack_timestampboolean––
enabledboolean––
partition_sensorobject––
portinteger––
reset_countersboolean––
serverstring–controller name (default 192.168.1.170)
simulatestring––
supervision_mininteger––
tcpboolean––
udpboolean––

No output schema declared.

No examples provided.

myio_cloud ~79

myIO Cloud remote access (GIGA/Opta 4.4+): enabled, connection state, broker, pairing window, paired phone keys (label, user slot, revoked). Credentials and keys are never shown. Admin level on the controller.

NameTypeReqDescription
serverstring–controller name (default 192.168.1.170)

No output schema declared.

No examples provided.

myio_cloud_set ~139

myIO Cloud actions (admin): enable (enabled=true|false), pair (user_slot 1.., label: opens a 5-minute pairing window for one phone - show the QR from the web page), pair_stop, revoke (key, revoked=true|false), delete_key (key). Needs MYIO_WRITE=admin.

NameTypeReqDescription
actionstringyes–
enabledboolean––
keyinteger––
labelstring––
revokedboolean––
serverstring–controller name (default 192.168.1.170)
user_slotinteger––

No output schema declared.

No examples provided.

myio_config_vars ~106

The raw settings block of the controller (the JS variables behind the Setup page: energy manager, SDM, dew point, sensor tables, every array). Give `names` to read specific variables, or `prefix` to list those starting with it; without arguments the variable names are listed. Editor/admin level.

NameTypeReqDescription
namesarray––
prefixstring––
serverstring–controller name (default 192.168.1.170)

No output schema declared.

No examples provided.

myio_dali ~122

Ext-DALI gateway on an Opta (4.8.6+): panels, the registered endpoints (short address / group / broadcast), the myIO PCA channel each is bound to (dim it with myio_output), last sent and driver-reported level, desired vs driver-read parameters (fade, power-on, failure level, min/max, curve) and group membership. ep = one endpoint. Editor/admin level.

NameTypeReqDescription
epinteger––
serverstring–controller name (default 192.168.1.170)

No output schema declared.

No examples provided.

myio_dali_set ~434

DALI registry and driver settings (Opta 4.8.6+; saved automatically). action: bind (ep, pca_id 2001.. or 0), settings (ep, any of fade_time 0..15, fade_rate 0..15, power_on, system_failure, min, max 0..254, curve 0 log / 1 linear; write=true (default) sends them to the driver), groups (ep, group 0..15, member true|false), read (ep: read the driver), identify (ep), add (panel, address 0..63 short / 64..79 group / 80 broadcast), add_all (panel: everything the last scan found), delete (ep), pool (lo, hi PCA ids), auto_bind, scan (panel: find drivers on the bus), abort (panel), commission (panel, mode 0 = re-address ALL / 1 = only unaddressed, start 0..63 - admin), short_address (ep, new 0..63 - admin), reset (ep - admin), panel_config (panel, field 0..6, value). Editor/admin level.

NameTypeReqDescription
actionstringyes–
addressinteger––
curveinteger––
epinteger––
fade_rateinteger––
fade_timeinteger––
fieldinteger––
groupinteger––
hiinteger––
lointeger––
maxinteger––
memberboolean––
mininteger––
modeinteger––
new_addressinteger––
panelinteger––
pca_idinteger––
power_oninteger––
serverstring–controller name (default 192.168.1.170)
startinteger––
system_failureinteger––
valueinteger––
writeboolean––

No output schema declared.

No examples provided.

myio_delete_timer ~53

Delete the timer with the given id (from myio_timers). Editor level.

NameTypeReqDescription
idintegeryes–
serverstring–controller name (default 192.168.1.170)

No output schema declared.

No examples provided.

myio_dmx ~91

Ext-DMX gateway on an Opta (4.9+): panels, fixtures (start address, type dimmer/RGB/RGBW/generic, channels) and the myIO PCA channel each DMX channel follows (dim it with myio_output / myio_set_rgb). Editor/admin level.

NameTypeReqDescription
serverstring–controller name (default 192.168.1.170)

No output schema declared.

No examples provided.

myio_dmx_set ~266

DMX fixtures (Opta 4.9+; saved automatically). action: add (panel, address 1..512, type 0 dimmer / 1 RGB / 2 RGBW / 3 generic), delete (fixture), address (fixture, address), type (fixture, type), channels (fixture, count 1..16 - generic only), bind (fixture, channel 1.., pca_id 2001.. or 0), auto_bind, pool (lo, hi), test (fixture: full on for 1.5 s - state), blackout (panel: all 512 slots to 0 - state), panel_config (panel, field 0..5, value). Editor/admin level.

NameTypeReqDescription
actionstringyes–
addressinteger––
channelinteger––
countinteger––
fieldinteger––
fixtureinteger––
hiinteger––
lointeger––
panelinteger––
pca_idinteger––
serverstring–controller name (default 192.168.1.170)
typeinteger––
valueinteger––

No output schema declared.

No examples provided.

myio_expander_set ~241

Expander settings (Opta 4.5+): failsafe {addr, mode 0 hold / 1 all off / 2 preset / 3 standalone, timeout_s 1..250, master, rules_linked, relink_truth, autosync, thermo_stale, stale_period_s} (saved; sync=true pushes the rules to the panel now), capture_preset (addr: the current outputs become the failsafe preset), aux {addr, pin 0=AUX2 1=AUX3, mode 0 0-10V / 1 LED strip}, onewire_rescan=true, onewire_forget (eeprom id of an OFFLINE sensor), forget_panel (addr of an OFFLINE panel). Editor/admin level.

NameTypeReqDescription
auxobject––
capture_presetinteger––
failsafeobject––
forget_panelinteger––
onewire_forgetinteger––
onewire_rescanboolean––
serverstring–controller name (default 192.168.1.170)

No output schema declared.

No examples provided.

myio_expanders ~127

RS485 expander panels on an Opta (4.5+): per address the configured type (Ext16 I/O, Ext-KNX, Ext-DALI, Ext-DMX, Ext-RS485 Modbus), online state, firmware/protocol, last seen, failsafe/standalone rules for losing the master, AUX output modes, Ext16 1-Wire thermometers. addr = one panel (1..). Editor/admin level.

NameTypeReqDescription
addrinteger––
serverstring–controller name (default 192.168.1.170)

No output schema declared.

No examples provided.

myio_file_op ~169

File operations: delete (a file or an EMPTY folder), mkdir, rename (move within the volume: path -> to), copy (path -> to, folders recursively; on GIGA/Opta also between volumes with to_vol). The controller refuses to delete slot_0, the boot scene slot or a slot a button/timer refers to. System files need MYIO_WRITE=admin. Editor/admin level.

NameTypeReqDescription
opstringyes–
pathstringyes–
serverstring–controller name (default 192.168.1.170)
tostring––
to_vol–––
volstring–q = internal flash (GIGA/Opta default), s = SD card (the only volume on a Due)

No output schema declared.

No examples provided.

myio_file_read ~132

Download a file from the controller. Text files come back as text (truncated at max_bytes, default 64 KB); binary files as size + hex preview, or base64=true for the content (max 512 KB). Editor/admin level.

NameTypeReqDescription
base64boolean––
max_bytesinteger––
pathstringyes–
serverstring–controller name (default 192.168.1.170)
volstring–q = internal flash (GIGA/Opta default), s = SD card (the only volume on a Due)

No output schema declared.

No examples provided.

myio_file_write ~187

Upload a file to the controller (creates or overwrites; the write is not atomic). content = text (UTF-8) or base64 = binary. make_dirs=true creates missing parent folders. System files (network, passwords, licence, cloud keys, web UI folders htm/ js/, slot folders) need MYIO_WRITE=admin. For flows.jsn / prog/N.txt prefer myio_flow_save / myio_script_save (validated + reloaded). Editor/admin level.

NameTypeReqDescription
base64string––
contentstring––
make_dirsboolean––
pathstringyes–
serverstring–controller name (default 192.168.1.170)
volstring–q = internal flash (GIGA/Opta default), s = SD card (the only volume on a Due)

No output schema declared.

No examples provided.

myio_files ~115

List a folder on the controller's storage: name, size, date; folders first; free/total space. vol q = internal flash (GIGA/Opta), s = SD card (Due: only s). Editor/admin level.

NameTypeReqDescription
dirstring–default /
serverstring–controller name (default 192.168.1.170)
volstring–q = internal flash (GIGA/Opta default), s = SD card (the only volume on a Due)

No output schema declared.

No examples provided.

myio_find ~81

Search outputs, groups, sensors, inputs and universal sensors by name (accent- and case-insensitive substring, e.g. "nappali"). Returns ids and live state so you can use the right control tool.

NameTypeReqDescription
querystringyesname fragment
serverstring–controller name (default 192.168.1.170)

No output schema declared.

No examples provided.

myio_flow ~148

Runtime control of the Flow engine (does NOT change flows.jsn): enable / disable a rule until the next reload or restart (use myio_flow_save en=0|1 to make it permanent), fire = run its THEN chain now (WHEN/AND skipped), set_var = set global variable id (1..32) to value (variable triggers are evaluated). The answer shows the outputs that changed and the trace. Editor/admin level.

NameTypeReqDescription
actionstringyes–
idintegeryesflow id, or the variable id for set_var
serverstring–controller name (default 192.168.1.170)
valueinteger––

No output schema declared.

No examples provided.

myio_flow_save ~462

Edit flows.jsn and reload the engine (no restart). Give ONE of: flow (a whole rule object; replaces the rule with the same id or adds it), delete (flow id), variable {id,name,init} / delete_variable, hook {id,name,met,url,body,err,gap} / delete_hook, or file (the complete flows.jsn). The rule is validated against the controller's card rules first; nothing is written on error. dry_run=true only validates. Card format (keys are short): WHEN t=sens{src:thermo|hum|usens, ch|id, op:gt|lt, val x10, hyst x10} | scmp | out{id, dir 0 off/1 on/2 any} | time{min, days} | sun{ev:rise|set, off} | var{id, op, val} | boot; AND t=sens | scmp | out{id, on 0|1} | twin{from, to, days} | var; THEN t=rel|grp{id, act 0 off/1 on/2 toggle} | pca|fet{id, val 0..255} | delay{s|m} | var{id, op:set|inc|dec, val} | log{val} | msg | http{id: webhook slot, val}. days = bitmask bit0=Mon..bit6=Sun (127 = every day); minutes of day for time/twin; temperatures x10 (21.5 °C = 215). Full reference: myio_reference topic=flow. Editor/admin level.

NameTypeReqDescription
deleteinteger–flow id to delete
delete_hookinteger––
delete_variableinteger––
dry_runboolean––
file––the complete flows.jsn (replaces everything)
flowobject–{"id":1,"name":"...","en":1,"when":{...},"and":[...],"then":[...]}
hookobject––
serverstring–controller name (default 192.168.1.170)
variableobject––

No output schema declared.

No examples provided.

myio_flow_trace ~103

What the Flow engine did recently (newest first): fired, AND failed, actions, delays, errors, webhook results, with seconds ago. since = the tseq of a previous call to get only newer entries (incremental). Also the engine budget statistics. Editor/admin level.

NameTypeReqDescription
limitinteger–default 40
serverstring–controller name (default 192.168.1.170)
sinceinteger––

No output schema declared.

No examples provided.

myio_flows ~138

The Flow rule engine (GIGA/Opta 4.4+): every rule as WHEN trigger / AND conditions / THEN actions in plain words with element names, its live state (enabled, running, last fired), the 32 global variables with live values and the webhook targets. id = one rule (with its raw JSON for editing); raw=true returns the whole flows.jsn (the format myio_flow_save takes). Editor/admin level.

NameTypeReqDescription
idinteger–only this flow id
rawboolean––
serverstring–controller name (default 192.168.1.170)

No output schema declared.

No examples provided.

myio_fm_sync ~108

The QSPI -> SD card configuration mirror (GIGA/Opta 4.4.3+): op status (default), config (mirror the configuration now), web (configuration + web UI folders), adopt (adopt a foreign card: write mirror.tag, then mirror). Needs an SD card and MYIO_WRITE=admin for the actions.

NameTypeReqDescription
opstring––
serverstring–controller name (default 192.168.1.170)

No output schema declared.

No examples provided.

myio_get_status ~202

Fetch a raw JSON endpoint of the controller. Default sens_out.json (live state of all outputs and sensors, minimal fields). Others: d_sens_out.json (with names), f_sens_out.json (all fields), sens_IO.json (+inputs, 4.3.12+/3.12.7+), output.json, relay.json, pca.json, groups.json, prot.json, joiner.json, sensor.json, info.json, usensor.json / shelly.json / link.json / sysdiag.json / flowtrace.json / prog.json / ai.json / alarm.json (4.x, editor level). Keys the account has no permission for are simply absent. Values: temp ×100, hum ×10, thresholds ×10, PCA level 0..255.

NameTypeReqDescription
endpointstring–file name, e.g. sens_out.json
serverstring–controller name (default 192.168.1.170)

No output schema declared.

No examples provided.

myio_globals ~117

Global settings: device name, controller clock, time zone (+ automatic EU daylight saving time on/off and whether summer time is in force, 3.12.35 / 4.18.9+), location (for sunrise/sunset), today's sunrise/sunset, button timing (hit/press limits), protection cooldown (4.x), sensor polling periods, pulse meter unit, current/boot scene slot, loggers. Editor/admin level.

NameTypeReqDescription
serverstring–controller name (default 192.168.1.170)

No output schema declared.

No examples provided.

myio_group_off ~85

Turn OFF all members of a group of outputs. id = 501..520 (1..20 also accepted). Group commands need EDITOR level on most firmware (a plain user cannot switch groups even with member permissions).

NameTypeReqDescription
idintegeryesgroup id (501..)
serverstring–controller name (default 192.168.1.170)

No output schema declared.

No examples provided.

myio_group_on ~85

Turn ON all members of a group of outputs. id = 501..520 (1..20 also accepted). Group commands need EDITOR level on most firmware (a plain user cannot switch groups even with member permissions).

NameTypeReqDescription
idintegeryesgroup id (501..)
serverstring–controller name (default 192.168.1.170)

No output schema declared.

No examples provided.

myio_group_toggle ~101

Smart-toggle a group of outputs. id = 501..520 (1..20 also accepted). Group commands need EDITOR level on most firmware (a plain user cannot switch groups even with member permissions). Mixed state: pullUP=1 turns ALL ON, pullUP=0 turns ALL OFF.

NameTypeReqDescription
idintegeryesgroup id (501..)
serverstring–controller name (default 192.168.1.170)

No output schema declared.

No examples provided.

myio_info ~134

Identify the controller: serial, firmware version, CPU/board, device name, element counts (RQ relays, SQ inputs, PCAQ PCA channels, SHQ Shelly, SENQ universal sensors), the permission level of this account (0 admin, 1 editor, 2 user), uptime, found I2C expanders and storage health. Call this first: the version decides which features exist (3.12.x = Due, only base features; 4.x = GIGA/Opta, all features).

NameTypeReqDescription
serverstring–controller name (default 192.168.1.170)

No output schema declared.

No examples provided.

myio_input_config ~137

What the physical inputs (wall buttons) do: enabled, NC contact, hit-block, and the targets of hit (short press), press (long press) and release in the unified id space (relay 1.., FET 101.., group 501.., scene 1000+slot, PCA 2001.., LED strip 3100+). Give id for one input; otherwise the named / bound ones. Editor/admin level.

NameTypeReqDescription
idinteger––
include_unusedboolean––
serverstring–controller name (default 192.168.1.170)

No output schema declared.

No examples provided.

myio_inputs ~114

State of the physical inputs (wall buttons / switches): id (1..SQ), name, pressed/closed now, enabled, NC. Polled state, not events - a short press can be missed. Needs 4.3.12+ or Due 3.12.7+; inputs the account has no permission for are absent.

NameTypeReqDescription
only_activeboolean–only inputs that are pressed/closed now
serverstring–controller name (default 192.168.1.170)

No output schema declared.

No examples provided.

myio_knx ~108

Ext-KNX gateway on an Opta (4.5+): the group-address table of the selected panel (row, name, group address, direction IN/OUT/SENSOR, DPT, local channel, flags, target universal sensor), the KNXnet/IP tunnelling interface for ETS (4.14+) and the KNX devices found/programmed without ETS. Editor/admin level.

NameTypeReqDescription
serverstring–controller name (default 192.168.1.170)

No output schema declared.

No examples provided.

myio_knx_device ~146

KNX device operations over the Ext-KNX panel (Opta 4.14+): scan (who is on the line, ~2 s), add (address a.l.d to the list), ping / info / delete / rename (index from myio_knx), program (address: writes the individual address into the ONE device whose programming button is pressed - needs MYIO_WRITE=admin). The answer waits for the result.

NameTypeReqDescription
actionstringyes–
addressstring––
indexinteger––
namestring––
serverstring–controller name (default 192.168.1.170)

No output schema declared.

No examples provided.

myio_knx_set ~225

Edit the Ext-KNX group-address table (the panel stores it; save=true (default) commits with KnxSave). panel = select another Ext-KNX panel first. rows: [{row 0..47, ga "main/middle/sub" ("" deletes the row), dir 0 none / 1 IN / 2 OUT / 3 SENSOR, dpt 1 bool / 2 percent / 3 float, local 0..15 (panel channel), target usens (SENSOR rows), invert, init_read (desired values), name (max 20, saved at once, 4.15+)}]. tunnel = enable/disable the ETS interface (4.14+), drop_tunnel=true closes the active ETS connection. Editor/admin level.

NameTypeReqDescription
drop_tunnelboolean––
panelinteger––
rowsarray––
saveboolean––
serverstring–controller name (default 192.168.1.170)
tunnelboolean––

No output schema declared.

No examples provided.

myio_ledstrip ~120

Addressable LED strips (GIGA/Opta 4.3.4+): enabled, strips per IO pin (LED count, running program), programs (effect, speed, brightness, colours, blend/kill transitions...). prog = one program with the effect list. Event id 3100+100*(IO-1)+program starts/stops a program (buttons, timers, Flow). Editor/admin level.

NameTypeReqDescription
proginteger––
serverstring–controller name (default 192.168.1.170)

No output schema declared.

No examples provided.

myio_ledstrip_set ~208

LED strips: event (id 3100+100*(IO-1)+program: run that program on that IO, the same id again stops it - MYIO_WRITE=state), enabled (desired), program edits (prog 1..32 with fields {fx, speed, brightness, intensity, density, length, palette, direction, color1, color2 (0xRRGGBB number), a, b, blend, blend_fx, blend_dir, kill, kill_fx, kill_dir, off_pause}, name) applied live and saved (ls_save); led_count {io 1..8, count} needs a restart. Editor/admin level.

NameTypeReqDescription
enabledboolean––
eventinteger––
fieldsobject––
led_countobject––
namestring––
proginteger––
serverstring–controller name (default 192.168.1.170)

No output schema declared.

No examples provided.

myio_link ~101

myIO Link (GIGA/Opta 4.2+): the other myIO controllers this one polls, their online state, the output links (a local output mirrors / drives a remote one) and sensor links (a remote sensor feeds a local universal sensor). scan=true shows network scan results. Editor/admin level.

NameTypeReqDescription
scanboolean––
serverstring–controller name (default 192.168.1.170)

No output schema declared.

No examples provided.

myio_link_set ~286

Change myIO Link; saved with ml_save. action: add (ip), add_found (index), scan (start), delete / probe / refresh_names (server slot 0..), disable (server, disabled), port / poll / rename / auth (server, port | ms | name | user+password), link (index, local_id, server 1.., remote_id: local output follows the remote one), unlink (index), link_disable (index, disabled), sensor_link (index, remote_id, server 1.., local_usens), sensor_link_disable (index, disabled). Editor/admin level.

NameTypeReqDescription
actionstringyes–
disabledboolean––
indexinteger––
ipstring––
local_idinteger––
local_usensinteger––
msinteger––
namestring––
passwordstring––
portinteger––
remote_idinteger––
serverstring–controller name (default 192.168.1.170)
server_nointeger–server number 1.. for link / sensor_link
srvinteger–server slot (0-based, as in myio_link)
startboolean––
userstring––

No output schema declared.

No examples provided.

myio_list_devices ~184

List outputs with id, name, live state and level: relays (1..RQ), FET/PWM channels (101..116, only on old hardware), PCA dimmer channels (2001..2000+PCAQ), groups (501..). Shows roles in braces: thermostat / sun-controlled / mixer / shutter-up / shutter-down / joiner / rgb:<group> / group:<group>, thermostat thresholds, running timers and group members. By default only NAMED elements are listed (unnamed ones are counted); set include_unnamed=true to see all. Use the ids with the control tools.

NameTypeReqDescription
include_unnamedboolean–also list elements without a name (default false)
serverstring–controller name (default 192.168.1.170)
typestring–only this type

No output schema declared.

No examples provided.

myio_log ~237

Read one day of a log (default: today's event log) with filters: level (error | info | debug - 4.x event log lines start with E/I/D), contains (text), since / until (HH:MM), tail (last N matching lines, default 150; 0 = all). date = YYYY-MM-DD, YYMMDD, today or yesterday; or give path (e.g. /ev_log/e_261025.csv). vol: q | s (default: the controller's own lookup, internal flash first). Editor/admin level.

NameTypeReqDescription
channelinteger––
containsstring––
datestring––
kindstring––
levelstring––
pathstring––
serverstring–controller name (default 192.168.1.170)
sincestring––
tailinteger––
untilstring––
volstring–q = internal flash (GIGA/Opta default), s = SD card (the only volume on a Due)

No output schema declared.

No examples provided.

myio_logs ~143

Which daily CSV logs exist: event log (ev_log/), consumption (c_log/), SDM meter (sdm_log/), per-sensor temperature (t_log_N/), humidity (h_log_N/), universal sensor (u_log_N/). Without kind: the log folders on each volume and the newest event-log days. kind (+channel for temperature/humidity/usens) = every file of that log with size and date. Read one with myio_log. Editor/admin level.

NameTypeReqDescription
channelinteger––
kindstring––
serverstring–controller name (default 192.168.1.170)

No output schema declared.

No examples provided.

myio_metrics ~99

The /metrics text (Prometheus format: uptime, loop rate, RAM, M4, link, WiFi RSSI, sockets, webhook counters, storage, usens values, 1-Wire temperatures). filter = only lines containing this text. GIGA/Opta 4.4.1+.

NameTypeReqDescription
filterstring––
serverstring–controller name (default 192.168.1.170)

No output schema declared.

No examples provided.

myio_mia ~113

MIA, the self-learning heating layer (GIGA/Opta 4.11+): features (thermal model, window detection, preheating, pause), and per thermostat zone the learned heat/cool rates, dead time, over/undershoot, duty, confidence, window events, preheating plan and result. zone = one relay id. Editor/admin level.

NameTypeReqDescription
serverstring–controller name (default 192.168.1.170)
zoneinteger––

No output schema declared.

No examples provided.

myio_mia_set ~264

Change MIA (saved immediately): enabled, features {model, window, preheat, pause} (desired values), window_drop_c 0.1..5, window_min 2..15, window_hold_min 5..240, preheat_max_min 15..240 (4.12+), learn_days 1..6, exclude {relay, excluded} (MIA does not act on that zone), exclude_f3 {relay, excluded} (4.13+), min_on_off {relay, on_min, off_min} (0 = auto, 4.13+), reset_learned (relay id, 0 = all zones). Editor/admin level.

NameTypeReqDescription
enabledboolean––
excludeobject––
exclude_f3object––
featuresobject––
learn_daysinteger––
min_on_offobject––
preheat_max_mininteger––
reset_learnedinteger––
serverstring–controller name (default 192.168.1.170)
window_drop_cnumber––
window_hold_mininteger––
window_mininteger––

No output schema declared.

No examples provided.

myio_modbus ~124

Ext-RS485 Modbus RTU master on an Opta (4.16+): per panel the bus settings, the poll blocks (slave, function, start register, count, period), the fields decoded from them (type, byte order, scale, target universal sensor) with live values, the writer slots (myIO relay/PCA -> Modbus register), and raw-request / address-scan results. Editor/admin level.

NameTypeReqDescription
panelinteger––
serverstring–controller name (default 192.168.1.170)

No output schema declared.

No examples provided.

myio_modbus_set ~668

Modbus panel table (Opta 4.16+; the panel saves 8 s after the last change, or save=true now). action: block (panel, index 0..7, slave 1..247, func 1..4, start, count 1..125, period_s, enabled), field (panel, index 0..31, block, offset, dtype 1 u16 / 2 i16 / 3 u32 / 4 i32 / 5 f32 / 6 u64 / 7 i64 / 8 f64 / 9 bit / 10 bool, order 0 ABCD / 1 CDAB / 2 BADC / 3 DCBA, bit, scale -9..9, sf_offset (255 none), target usens, enabled, invert), writer (panel, index 0..15, slave, func 5/6/16, reg, dtype, order, source_pca, off, on, period_s, enabled, invert), delete (panel, table 0 block / 1 field / 2 writer, index), bus (panel, baud code 0 9600 / 1 19200 / 2 38400 / 3 57600 / 4 115200, frame 0 8N1 / 1 8E1 / 2 8O1 / 3 8N2, timeout_ms, retries, gap_ms), name (panel, field_index or writer_index or none for the panel, name), preset (panel, preset id e.g. SDM630), reload (panel), clear (panel - admin), raw (panel, slave, func, reg, count: one request, result shown) and scan (panel, from, to, func, reg: which slave addresses answer). Editor/admin level.

NameTypeReqDescription
actionstringyes–
baudinteger––
bitinteger––
blockinteger––
countinteger––
dtypeinteger––
enabledboolean––
field_indexinteger––
frameinteger––
frominteger––
funcinteger––
gap_msinteger––
indexinteger––
invertboolean––
namestring––
offinteger––
offsetinteger––
oninteger––
orderinteger––
panelintegeryes–
period_sinteger––
presetstring––
reginteger––
retriesinteger––
saveboolean––
scaleinteger––
serverstring–controller name (default 192.168.1.170)
sf_offsetinteger––
slaveinteger––
source_pcaboolean––
startinteger––
tableinteger––
targetinteger––
timeout_msinteger––
tointeger––
writer_indexinteger––

No output schema declared.

No examples provided.

myio_mqtt ~110

MQTT client settings and live state (GIGA/Opta 4.3+, Due 3.12.31+): broker, connection state, topics, retain/QoS, Home Assistant discovery, publish masks, subscribe/command channel, external sensor bindings (topic + JSON key -> universal sensor, 4.5+). Passwords and TLS keys are never shown. Editor/admin level.

NameTypeReqDescription
serverstring–controller name (default 192.168.1.170)

No output schema declared.

No examples provided.

myio_mqtt_set ~353

Change the MQTT client. Only the given fields change; on/off fields are desired values (sent only when different). save=true (default) persists and reconnects (MqttSave). Fields: enabled, host, port, user, password, client_id, base_topic, retain, qos 0|1, ha_discovery, economy (4.x), tls (4.x), publish_on_change {buttons, outputs, activators}, periodic {outputs, temperatures, humidity, usens (4.x), sdm} + period_s 5..65000, subscribe, command_channel, command_slot; sensor_binding {slot, topic, key, usens} (4.5+; usens 0 = unbind); rediscover=true refreshes the Home Assistant entities without reconnecting. Editor/admin level.

NameTypeReqDescription
base_topicstring––
client_idstring––
command_channelboolean––
command_slotinteger––
economyboolean––
enabledboolean––
ha_discoveryboolean––
hoststring––
passwordstring––
period_sinteger––
periodicobject––
portinteger––
publish_on_changeobject––
qosinteger––
rediscoverboolean––
retainboolean––
saveboolean––
sensor_bindingobject––
serverstring–controller name (default 192.168.1.170)
subscribeboolean––
tlsboolean––
userstring––

No output schema declared.

No examples provided.

myio_network ~92

Network configuration and live state (GIGA/Opta 4.x): host name, LAN (DHCP/static, link), WiFi mode (off / STA / AP), STA and AP settings, live addresses, RSSI, which services run on which interface. Passwords are never shown. Editor/admin level.

NameTypeReqDescription
serverstring–controller name (default 192.168.1.170)

No output schema declared.

No examples provided.

myio_network_set ~177

DANGEROUS: a wrong value can make the controller unreachable (then only USB serial or the service access point helps). Changes: host, wifi_mode 0 off / 1 STA / 2 AP, sta {ssid, password, dhcp}, ap {ssid, password, channel 1..13}, lan {enabled, dhcp, static_primary}. apply=true saves AND applies now (no restart; the connection may drop), apply=false only saves for the next boot. Needs MYIO_WRITE=admin.

NameTypeReqDescription
apobject––
applybooleanyes–
hoststring––
lanobject––
serverstring–controller name (default 192.168.1.170)
staobject––
wifi_modeinteger––

No output schema declared.

No examples provided.

myio_output ~169

One tool for every output type, by id: relay (1..RQ), FET (101..116), group (501..), PCA dimmer (2001..). action: on | off | toggle | level (level needs `level` 0..255 or `percent` 0..100; PCA/FET only). ON on a dimmer = its configured MAX, OFF = MIN. Reads the state back.

NameTypeReqDescription
actionstringyes–
idintegeryeselement id
levelinteger–raw level 0..255 (action=level)
percentnumber–level in percent (action=level, when level is not given)
serverstring–controller name (default 192.168.1.170)

No output schema declared.

No examples provided.

Install

How do I install the myIO MCP server?

myIO runs locally as an npm package, launched with npx -y myio-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · myio-mcp

# add to Claude Code
claude mcp add smarthomeninja-myio-mcp -- npx -y myio-mcp
Common questions

What is the myIO MCP server?

myIO is an MCP server listed in the public MCP registry as io.github.SmarthomeNinja/myio-mcp. Read and control a myIO smart home controller: heating, lighting, blinds and energy. This page covers its npm package (myio-mcp).

Is the myIO MCP server safe to use?

myIO scores 66 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. 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 myIO MCP server expose?

myIO exposes 102 tools: myio_servers, myio_info, myio_find, myio_list_devices, myio_read_sensors, and 97 more. Their descriptions and schemas cost roughly 15,466 tokens of context every time the server is loaded.

Is the myIO MCP server still maintained?

myIO 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 myIO MCP server under?

myIO 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 myIO MCP server?

VerifyMCP ran 16 checks on myIO, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.