myIO
NPM · MYIO-MCP
Read and control a myIO smart home controller: heating, lighting, blinds and energy.
Available components
Last scanned (20 hours ago)
Scores higher than 38% of npm servers
Category IoT and Hardware
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
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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
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 →
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.
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 →
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 →
myio_output_config Output configuration ~136
Configuration of outputs (relay, FET, PCA): auto-off timer, turn-on delay, inverted wiring, alarm flag, justOn (a button can only switch it on), PCA min/max level, fade speed, PWM (dimmer) vs switch mode, mixer mode, sensor binding and thresholds. Give id for one output, type for one kind, or nothing for all named ones. Editor/admin level.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | – | – |
| include_unnamed | boolean | – | – |
| server | string | – | controller name (default 192.168.1.170) |
| type | string | – | – |
No output schema declared.
No examples provided.
myio_pca_off PCA OFF ~93
Turn OFF a PCA channel (dimmer / universal output). id = 2001..2000+PCAQ (a 1-based channel number is also accepted). ON = the channel's configured MAX level, OFF = its MIN level.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | PCA id (2001..) |
| server | string | – | controller name (default 192.168.1.170) |
No output schema declared.
No examples provided.
myio_pca_on PCA ON ~93
Turn ON a PCA channel (dimmer / universal output). id = 2001..2000+PCAQ (a 1-based channel number is also accepted). ON = the channel's configured MAX level, OFF = its MIN level.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | PCA id (2001..) |
| server | string | – | controller name (default 192.168.1.170) |
No output schema declared.
No examples provided.
myio_pca_set PCA level ~150
Set a PCA channel to an exact level. Give either level (raw 0..255, what the controller stores and shows) or percent (0..100, converted to 0..255). If the channel has an auto-off timer, setting it above MIN (re)starts the timer. id = 2001..2000+PCAQ.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | PCA id (2001..) |
| level | integer | – | raw level 0..255 |
| percent | number | – | level in percent (0..100), used when level is not given |
| server | string | – | controller name (default 192.168.1.170) |
No output schema declared.
No examples provided.
myio_pca_toggle PCA toggle ~92
Toggle a PCA channel (dimmer / universal output). id = 2001..2000+PCAQ (a 1-based channel number is also accepted). ON = the channel's configured MAX level, OFF = its MIN level.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | PCA id (2001..) |
| server | string | – | controller name (default 192.168.1.170) |
No output schema declared.
No examples provided.
myio_permissions User element permissions ~101
Element permissions of a user slot (4.x): read / write per relay (and FET), hit / press per input - the lists of element ids the user may see / switch. On Due 3.x the map cannot be read (only set with fill/clear and explicit toggles). Admin level reads it too.
| Name | Type | Req | Description |
|---|---|---|---|
| server | string | – | controller name (default 192.168.1.170) |
| slot | integer | yes | – |
No output schema declared.
No examples provided.
myio_press_button Simulate a button ~114
Simulate a wall button on input id (1..SQ): kind hit = short press (default), press = long press, release = release after a long press. The controller runs the actions bound to that input (switch/dim/group/scene), exactly like the physical button. The reply lists the outputs that changed.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | input id (1..SQ) |
| kind | string | – | – |
| server | string | – | controller name (default 192.168.1.170) |
No output schema declared.
No examples provided.
myio_pwm_off PWM OFF ~78
Turn OFF a FET/PWM output (legacy hardware only; ids 101..116 - absent on most GIGA/Opta controllers, see myio_list_devices).
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | FET id (101..116) |
| server | string | – | controller name (default 192.168.1.170) |
No output schema declared.
No examples provided.
myio_pwm_on PWM ON ~78
Turn ON a FET/PWM output (legacy hardware only; ids 101..116 - absent on most GIGA/Opta controllers, see myio_list_devices).
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | FET id (101..116) |
| server | string | – | controller name (default 192.168.1.170) |
No output schema declared.
No examples provided.
myio_pwm_set PWM level ~91
Set a FET/PWM output level: level (raw 0..255) or percent (0..100). Legacy hardware only (ids 101..116).
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | FET id (101..116) |
| level | integer | – | – |
| percent | number | – | – |
| server | string | – | controller name (default 192.168.1.170) |
No output schema declared.
No examples provided.
myio_pwm_toggle PWM toggle ~77
Toggle a FET/PWM output (legacy hardware only; ids 101..116 - absent on most GIGA/Opta controllers, see myio_list_devices).
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | FET id (101..116) |
| server | string | – | controller name (default 192.168.1.170) |
No output schema declared.
No examples provided.
myio_read_sensors Read myIO sensors ~174
All sensor readings in real units: 1-Wire temperature (ids 1..100, °C), humidity (101..110, %), pulse energy meter (200), SDM630 power/voltage/current per phase (201..209: W, V, A), and on 4.x firmware the universal sensors (usens 0..SENQ: temperature, humidity, dew point, power, energy, CO2 ... from KNX/Modbus/MQTT/Shelly/Script; activator id = 300+id). Invalid/missing sensors read "invalid"; STALE = no fresh value within the failsafe time.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | only this kind |
| server | string | – | controller name (default 192.168.1.170) |
No output schema declared.
No examples provided.
myio_reference myIO language / API reference ~103
The controller documentation bundled with this server (Hungarian, the canonical API_REFERENCE.md): topic=script = the complete myIO Script language (directives, syntax, built-in functions, error codes, examples); topic=flow = the Flow engine and the flows.jsn card format; topic=api with query = the API sections whose heading contains the query (without query: the table of contents).
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | – |
| topic | string | yes | – |
No output schema declared.
No examples provided.
myio_relay_off Relay OFF ~79
Turn OFF a relay output. id = relay id 1..RQ (see myio_info / myio_list_devices). The reply shows the state read back from the controller.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | relay id (1..RQ) |
| server | string | – | controller name (default 192.168.1.170) |
No output schema declared.
No examples provided.
myio_relay_on Relay ON ~79
Turn ON a relay output. id = relay id 1..RQ (see myio_info / myio_list_devices). The reply shows the state read back from the controller.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | relay id (1..RQ) |
| server | string | – | controller name (default 192.168.1.170) |
No output schema declared.
No examples provided.
myio_relay_toggle Relay toggle ~81
Toggle (invert) a relay output. id = relay id 1..RQ (see myio_info / myio_list_devices). The reply shows the state read back from the controller.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | relay id (1..RQ) |
| server | string | – | controller name (default 192.168.1.170) |
No output schema declared.
No examples provided.
myio_rename Rename an element ~161
Set the name (description) of an element. kind: relay (id 1..RQ), pca (2001.. or channel 1..), fet (101..), group (501.. or 1..), input (1..SQ), thermo (1-Wire sensor id 1..100), humidity (channel index 0..), usens (4.x, id 0..SENQ), shelly (4.x), scene (slot 0..). Empty name clears it. Editor level; accents are fine.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
| kind | string | yes | – |
| name | string | yes | – |
| server | string | – | controller name (default 192.168.1.170) |
No output schema declared.
No examples provided.
myio_rgb RGB lights ~87
RGB lights = groups whose name starts with "RGB", with R/G/B channels (PCA or FET outputs whose names start with R, G, B). Shows on/off, colour (max-normalised 0..255) and brightness (0..255, the highest channel level).
| Name | Type | Req | Description |
|---|---|---|---|
| server | string | – | controller name (default 192.168.1.170) |
No output schema declared.
No examples provided.
myio_scene Scene action ~116
Scene slots: load (apply slot - this changes outputs and settings), save (store the CURRENT configuration into slot, overwriting it), new (create the next free slot), delete (slot 0 and the boot slot cannot be deleted), set_boot (slot loaded at power-up), rename. Editor level; save/delete are destructive.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| name | string | – | – |
| server | string | – | controller name (default 192.168.1.170) |
| slot | integer | – | – |
No output schema declared.
No examples provided.
myio_scenes Scenes (configuration slots) ~91
Scene slots: a slot stores a complete configuration snapshot (outputs, groups, protection, inputs, globals ...) that can be loaded by a timer, a button (target 1000+slot) or myio_scene. Shows the slot list with names, the current and the boot slot. Editor/admin level.
| Name | Type | Req | Description |
|---|---|---|---|
| server | string | – | controller name (default 192.168.1.170) |
No output schema declared.
No examples provided.
myio_script Run / switch / delete a script ~117
Script slot actions: reload (recompile prog/N.txt; id 0 = all), run (run once now, even if disabled), enable / disable (RAM only until reload/restart; persist=true also rewrites #enabled in the file), delete (removes prog/N.txt, needs MYIO_WRITE=config). Editor/admin level.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| id | integer | yes | – |
| persist | boolean | – | – |
| server | string | – | controller name (default 192.168.1.170) |
No output schema declared.
No examples provided.
myio_script_get Read a script ~66
The source code of script slot N (prog/N.txt) and its state. Language reference: myio_reference topic=script. Editor/admin level.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
| server | string | – | controller name (default 192.168.1.170) |
No output schema declared.
No examples provided.
myio_script_save Write a script ~156
Write the source of script slot N (prog/N.txt) and recompile it on the controller; the answer is the compile result (error with line:col and the source line) and the new state. enabled=true|false rewrites the #enabled directive. The file is the truth (#name, #every 1s, #enabled, #onboot header). Max size: 8 KB on GIGA, 4 KB on Opta. Language reference: myio_reference topic=script. Editor/admin level.
| Name | Type | Req | Description |
|---|---|---|---|
| enabled | boolean | – | – |
| id | integer | yes | – |
| server | string | – | controller name (default 192.168.1.170) |
| source | string | yes | – |
No output schema declared.
No examples provided.
myio_scripts Scripts (myIO Script programs) ~125
The program engine (GIGA/Opta 4.10+): every slot (prog/N.txt, 16 on GIGA, 8 on Opta) with name, state (off / RUNNING / ERROR with line:col and message), cycle time, runs, timing, local variables and arrays, plus the 32 global variables and (trace=true) the recent trace. Editor/admin level.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | – | – |
| server | string | – | controller name (default 192.168.1.170) |
| trace | boolean | – | – |
No output schema declared.
No examples provided.
myio_send_command Raw myIO command ~195
Send raw command(s) to the controller, chained with &, e.g. "r_ON=16&r_OFF=5&PCA*2001=128" (PCA level is RAW 0..255). Covers everything in the API reference: thresholds min_temp_ON*<id>=<x10>, names r_descr*<id>=<text>, timers r_timer*<id>=<s>, scene load lo_all=<slot>, button simulation s_hit=<id>, usens*<id>=<x10> etc. Toggle-type config commands (relaysInvert=<id>, PCA_PWM=<id>...) INVERT the flag - read the current value first. Body limit 1024 bytes. The reply lists which outputs changed state.
| Name | Type | Req | Description |
|---|---|---|---|
| commands | string | yes | command string, key=value pairs joined with & |
| server | string | – | controller name (default 192.168.1.170) |
No output schema declared.
No examples provided.
myio_servers Configured myIO controllers ~57
List the configured controllers (name, URL) with a live check: firmware version, device name, permission level, reachability. Use the name as the `server` argument of the other tools; without it the first controller is used.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
myio_set_globals Change controller settings ~303
Change global settings: name, time_zone (hours from UTC; with automatic DST on it is the STANDARD/winter offset, e.g. 1 for Central Europe - changing it moves the clock at once on 3.12.35 / 4.18.9+), auto_dst (true/false: automatic EU daylight saving time, 3.12.35 / 4.18.9+, on by default; stored at once, no save needed), latitude/longitude, hit_time_limit / press_time_limit (ms), prot_cooldown (s, 4.x), temp_timer / hum_timer / mixer_timer (sensor polling s), impulse_per_unit, consumption_unit, sync_time=true (NTP sync now). Only the given fields change. Editor/admin level.
| Name | Type | Req | Description |
|---|---|---|---|
| auto_dst | boolean | – | – |
| consumption_unit | string | – | – |
| hit_time_limit | integer | – | – |
| hum_timer | integer | – | – |
| impulse_per_unit | integer | – | – |
| latitude | number | – | – |
| longitude | number | – | – |
| mixer_timer | integer | – | – |
| name | string | – | – |
| press_time_limit | integer | – | – |
| prot_cooldown | integer | – | – |
| server | string | – | controller name (default 192.168.1.170) |
| sync_time | boolean | – | – |
| temp_timer | integer | – | – |
| time_zone | integer | – | – |
No output schema declared.
No examples provided.
myio_set_group Set group members ~156
Set the member list of a group (id 501..): members = output ids (relay 1.., FET 101.., PCA 2001.., fade variants 4001.. allowed), at most groupSize (usually 10); an empty list clears the group. pull_up = when members are mixed, toggle turns ALL ON (false: all OFF). The controller refuses a group that would contain itself. Editor level.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | group id (501..) or 1.. |
| members | array | yes | – |
| name | string | – | – |
| pull_up | boolean | – | – |
| server | string | – | controller name (default 192.168.1.170) |
No output schema declared.
No examples provided.
myio_set_input_config Change input configuration ~170
Change a physical input (1..SQ): enabled, nc (normally closed), hit_block, and the action targets hit / press / release as element ids (0 = none; relay 1.., FET 101.., group 501.., load scene 1000+slot, PCA 2001.., LED strip 3100+). Flags are set to the given value. Editor level.
| Name | Type | Req | Description |
|---|---|---|---|
| enabled | boolean | – | – |
| hit | integer | – | – |
| hit_block | boolean | – | – |
| id | integer | yes | input id (1..SQ) |
| nc | boolean | – | – |
| press | integer | – | – |
| release | integer | – | – |
| server | string | – | controller name (default 192.168.1.170) |
No output schema declared.
No examples provided.
myio_set_joiner Set a joiner pair ~123
Define or clear a joiner pair (index 0..JQ-1, or omit: an identical existing pair is reused, otherwise the first free one): switching master also switches slave (ids in the unified space); 0/0 clears. just_on = the slave only follows switching ON. Editor level.
| Name | Type | Req | Description |
|---|---|---|---|
| index | integer | – | – |
| just_on | boolean | – | – |
| master | integer | yes | – |
| server | string | – | controller name (default 192.168.1.170) |
| slave | integer | yes | – |
No output schema declared.
No examples provided.
myio_set_output_config Change output configuration ~212
Change an output's configuration (relay 1..RQ, FET 101.., PCA 2001..): timer_s (auto-off, 0 = off), delay_s (turn-on delay), invert, alarm, just_on, and for PCA/FET: min / max level (0..255), fade_speed, pwm (dimmer mode), mixer. Flags are set to the given value (the controller's toggle commands are only sent when the value differs). Editor level.
| Name | Type | Req | Description |
|---|---|---|---|
| alarm | boolean | – | – |
| delay_s | integer | – | – |
| fade_speed | integer | – | – |
| id | integer | yes | output id |
| invert | boolean | – | – |
| just_on | boolean | – | – |
| max | integer | – | – |
| min | integer | – | – |
| mixer | boolean | – | – |
| pwm | boolean | – | – |
| server | string | – | controller name (default 192.168.1.170) |
| timer_s | integer | – | – |
No output schema declared.
No examples provided.
myio_set_permissions Change user element permissions ~166
Change the element permissions of a user slot (ADMIN). fill = grant everything, clear = revoke everything. Then per list the ids to GRANT or REVOKE: relay_read, relay_write, pca_read, pca_write, fet_read, fet_write (output ids), input_hit, input_press (input ids). On 4.x the current map is read first and only differences are sent; on Due 3.x the firmware toggles are sent as given (each id flips its bit).
| Name | Type | Req | Description |
|---|---|---|---|
| clear | boolean | – | – |
| fill | boolean | – | – |
| grant | object | – | – |
| revoke | object | – | – |
| server | string | – | controller name (default 192.168.1.170) |
| slot | integer | yes | – |
No output schema declared.
No examples provided.
myio_set_protection Set a protection pair ~150
Define or clear a protection pair (index 0..PQ-1, or omit index: an identical existing pair is reused, otherwise the first free one): up and down = output ids that may never be on together (relay 1.., PCA 2001..); 0/0 clears the pair. priority = the first (UP) element wins when both are requested. A pair makes a shutter for myio_shutters. Editor level.
| Name | Type | Req | Description |
|---|---|---|---|
| down | integer | yes | – |
| index | integer | – | – |
| priority | boolean | – | – |
| server | string | – | controller name (default 192.168.1.170) |
| up | integer | yes | – |
No output schema declared.
No examples provided.
myio_set_rgb Set RGB light ~152
Control an RGB light (group id from myio_rgb): on/off, colour r,g,b (0..255 each; the brightness is kept unless given), brightness 0..255 (keeps the colour). ON without colour restores the last colour (white at first). The channel levels are written directly (PCA*<id>=<level>) and read back.
| Name | Type | Req | Description |
|---|---|---|---|
| b | integer | – | – |
| brightness | integer | – | – |
| g | integer | – | – |
| id | integer | yes | RGB group id (501..) |
| on | boolean | – | – |
| r | integer | – | – |
| server | string | – | controller name (default 192.168.1.170) |
No output schema declared.
No examples provided.
myio_set_thermostat Set thermostat ~263
Change a thermostat zone: target temperature (°C, keeps the band), band / hysteresis (°C 0.1..10, keeps the middle), or the raw ON/OFF thresholds (°C). Optionally bind the sensor: sensor = 1..100 (1-Wire id), 301.. (universal sensor 300+id), 0 = unbind (editor level). Heating = ON below OFF, cooling = ON above OFF. The controller switches the output itself; the reply reads the zone back.
| Name | Type | Req | Description |
|---|---|---|---|
| band | number | – | band / hysteresis °C (0.1..10) |
| id | integer | yes | relay id (1..RQ) or PCA id (2001..) of the zone |
| off | number | – | OFF threshold °C (raw; use with on) |
| on | number | – | ON threshold °C (raw; use with off) |
| sensor | integer | – | bind this sensor id (1..100 1-Wire, 301+ usens, 0 = unbind) |
| server | string | – | controller name (default 192.168.1.170) |
| target | number | – | target °C (-30..100) |
No output schema declared.
No examples provided.
myio_set_timer Create or change a timer ~291
Create (omit id; an identical existing timer is not duplicated) or change (id) a timer. Time: hour 0..23 + minute 0..59, or sunrise / sunset = "after" | "before" with hour/minute as the offset (max 4 h). Optional month (1..12) and day (1..31) for a one-day timer. days: weekday names ["Mon","Fri"] (omit = every day). event: code or name - 1 load scene (all), 2 relay ON, 3 relay OFF, 4 FET ON, 5 FET OFF, 6 group ON, 7 group OFF, 15 PCA ON, 16 PCA OFF, 8..14/17 load scene parts, 18 SG-Ready mode. param: the target id (relay/FET/group/PCA id, scene slot, SG mode 1..4). Editor level.
| Name | Type | Req | Description |
|---|---|---|---|
| day | integer | – | – |
| days | array | – | – |
| event | – | yes | – |
| hour | integer | – | – |
| id | integer | – | – |
| minute | integer | – | – |
| month | integer | – | – |
| param | integer | yes | – |
| server | string | – | controller name (default 192.168.1.170) |
| sunrise | string | – | – |
| sunset | string | – | – |
No output schema declared.
No examples provided.
myio_set_usens Write a universal sensor ~138
4.x: push a value into a universal sensor slot (id 0..SENQ) from outside, e.g. a temperature from another system: value in real units (21.5 °C -> stored as 215). Thermostats, Flow, MQTT and logs see it like any sensor. The slot must be enabled; the reply reads it back.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | usens id (0..SENQ) |
| server | string | – | controller name (default 192.168.1.170) |
| value | number | yes | value in real units (one decimal is kept) |
No output schema declared.
No examples provided.
myio_sgready SG-Ready heat pump ~93
SG-Ready heat pump control (GIGA/Opta 4.4.2+, Due 3.12.9+): enabled, current mode (1 inhibit / 2 normal / 3 recommended / 4 forced), K1/K2 contact outputs, utility-lock limit. Editor/admin level.
| Name | Type | Req | Description |
|---|---|---|---|
| server | string | – | controller name (default 192.168.1.170) |
No output schema declared.
No examples provided.
myio_sgready_set Set SG-Ready ~157
Change SG-Ready: mode 1..4 (immediate; mode 1 ends automatically after limit_min), enabled, k1 / k2 (output ids: relay 1.. or PCA 2001..; 0 = none; K1 and K2 must differ), limit_min 1..120. Mode is a state change (MYIO_WRITE=state); the others are configuration. Saved immediately (EEPROM).
| Name | Type | Req | Description |
|---|---|---|---|
| enabled | boolean | – | – |
| k1 | integer | – | – |
| k2 | integer | – | – |
| limit_min | integer | – | – |
| mode | integer | – | – |
| server | string | – | controller name (default 192.168.1.170) |
No output schema declared.
No examples provided.
myio_shelly Shelly devices ~122
Shelly integration (GIGA/Opta 4.1+): every registered Shelly with IP, model, online state, relay state, and its bindings (which myIO output a channel follows, which myIO button an input drives, which universal sensor a metric feeds). scan=true also shows the results of a network scan (start one with myio_shelly_set action=scan). Editor/admin level.
| Name | Type | Req | Description |
|---|---|---|---|
| scan | boolean | – | – |
| server | string | – | controller name (default 192.168.1.170) |
No output schema declared.
No examples provided.
myio_shelly_set Configure Shelly ~379
Change the Shelly integration; every change is saved (sh_save). action: enable (enabled=true|false), add (ip), add_found (index from the scan), scan (start=true|false), delete / probe / push (device), disable (device, disabled), rename (device, name), poll (device, ms 500..60000), auth (device, user, password), bind_output (device, channel, output_id: the Shelly channel follows that myIO output; 0 = unbind), bind_input (device, channel, button 1..SQ, mode 0 button / 1 toggle / 2 hit-only), bind_sensor (device, slot 0..3, metric 1 temp / 2 hum / 3 power / 4 volt / 5 curr / 6 energy / 7 device temp, channel, usens id; usens 0 = unbind). After input / sensor bindings send action=push so the Shelly calls back. Device = slot number from myio_shelly. Editor/admin level.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| button | integer | – | – |
| channel | integer | – | – |
| device | integer | – | – |
| disabled | boolean | – | – |
| enabled | boolean | – | – |
| index | integer | – | – |
| ip | string | – | – |
| metric | integer | – | – |
| mode | integer | – | – |
| ms | integer | – | – |
| name | string | – | – |
| output_id | integer | – | – |
| password | string | – | – |
| server | string | – | controller name (default 192.168.1.170) |
| slot | integer | – | – |
| start | boolean | – | – |
| usens | integer | – | – |
| user | string | – | – |
No output schema declared.
No examples provided.
myio_shutter Move a shutter ~136
Move a shutter / cover: action open (down off, up on), close (up off, down on) or stop (both off). Identify it by index (from myio_shutters) or by the id of its up relay. The controller enforces the mutual exclusion; the motor runs until its end switch or until you stop it.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| index | integer | – | pair index from myio_shutters |
| server | string | – | controller name (default 192.168.1.170) |
| up_id | integer | – | id of the UP output instead of index |
No output schema declared.
No examples provided.
myio_shutters Shutters / covers ~84
Shutters, blinds, gates and other UP/DOWN pairs defined as protection pairs on the controller (the two outputs can never be on together): index, name, up and down relay ids, state opening / closing / stopped. Use myio_shutter to move them.
| Name | Type | Req | Description |
|---|---|---|---|
| server | string | – | controller name (default 192.168.1.170) |
No output schema declared.
No examples provided.
myio_structures Protection pairs, joiners, groups ~93
The structural configuration: protection pairs (two outputs never on together = shutters; index, UP, DOWN, priority), joiner pairs (master switches the slave too; justOn), groups (id 501.., members in the unified id space, pullUp = mixed state toggles to ON). Editor/admin level.
| Name | Type | Req | Description |
|---|---|---|---|
| server | string | – | controller name (default 192.168.1.170) |
No output schema declared.
No examples provided.
myio_sysdiag System diagnostics ~114
Health snapshot of the controller: uptime and last reset cause (watchdog?), main-loop speed and the longest stall, free RAM and its minimum, M4 button core, LAN link / WiFi, every network socket with its peer, outgoing HTTP slots, storage space, login brake counters. Due 3.12 gives a shorter set. raw=true = the JSON. Editor/admin level.
| Name | Type | Req | Description |
|---|---|---|---|
| raw | boolean | – | – |
| server | string | – | controller name (default 192.168.1.170) |
No output schema declared.
No examples provided.
myio_system Restart / firmware update ~221
Admin actions: restart (soft reboot, ~1 min offline), ota_upload (file = local path of the firmware package the fleet tool made for THIS controller - GIGA/Opta (4.x): MYIO_UPD.BIN, uploaded to the SD card, or internal flash without a card; Due (3.12+): MYIO_NEW.BIN, SD card only, checked before upload: a raw Arduino build or a package made for another controller is refused), ota_apply (the controller installs the uploaded package and restarts; a GIGA/Opta rolls back by itself if the new image fails, a Due keeps its running firmware if the package is rejected), ota_restore (GIGA/Opta only: go back to the previous image). The answer waits for the controller to come back and reports the running version and the outcome. Needs MYIO_WRITE=admin.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| file | string | – | – |
| server | string | – | controller name (default 192.168.1.170) |
No output schema declared.
No examples provided.
myio_thermostats Thermostats ~109
Outputs controlled by a sensor: thermostat zones (relay or PCA switched by a temperature sensor: target = middle of the ON/OFF thresholds, band = their distance, mode heat if ON<OFF else cool, current temperature, heating/idle), humidity-controlled outputs, sun-controlled outputs (sunrise/sunset) and analog mixers. Use the ids with myio_set_thermostat.
| Name | Type | Req | Description |
|---|---|---|---|
| server | string | – | controller name (default 192.168.1.170) |
No output schema declared.
No examples provided.
myio_timers Timers ~84
Scheduled actions from timer.csv: time (or sunrise/sunset with ± offset), optional month/day, weekday filter (empty = every day), event (relay/FET/group/PCA ON/OFF, load scene, SG-Ready mode) and target. Editor/admin level.
| Name | Type | Req | Description |
|---|---|---|---|
| server | string | – | controller name (default 192.168.1.170) |
No output schema declared.
No examples provided.
myio_usensors Universal sensors ~128
4.x: the universal sensor slots (0..SENQ): name, type (temperature, humidity, dew point, power, energy, CO2 ...), value, ok / STALE / no value, failsafe time, enabled. Sources: KNX, Modbus, MQTT, Shelly, Script, external HTTP (usens*<id>=). Activator id for thermostats = 300+id. Needs editor level.
| Name | Type | Req | Description |
|---|---|---|---|
| include_disabled | boolean | – | – |
| server | string | – | controller name (default 192.168.1.170) |
No output schema declared.
No examples provided.
myio_user Manage a user ~136
User accounts (ADMIN level): action new (next free slot), delete (slot, not 0), rename (slot + name), set_password (slot + password; the login name of the slot is used), set_rights (slot + rights admin|editor|user; not slot 0). Changing the account the server itself uses will break the connection.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| name | string | – | – |
| password | string | – | – |
| rights | string | – | – |
| server | string | – | controller name (default 192.168.1.170) |
| slot | integer | – | – |
No output schema declared.
No examples provided.
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
claude mcp add smarthomeninja-myio-mcp -- npx -y myio-mcp
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.