io.github.SmarthomeNinja/myio-mcp

myIO

Is the myIO MCP server down? It gave no valid answer in the probe of 2026-11-15: crashed on start. One failed probe is not an outage.

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

crashed on start no valid answer since 2026-11-15 · probed 2026-11-15

MCP error -32000: Connection closed
    at file:///work/node_modules/myio-mcp/dist/index.js:119:1
    at ModuleJob.run (node:internal/modules/esm/module_job:343

Run it: npx -y myio-mcp@1.6.1 (stdio, probed in a container with the network off)
Host: npmjs.com
Repository: https://github.com/SmarthomeNinja/myio-mcp
Website: https://myio.hu/en/
Registry: active, updated 2026-11-15 · registry entry

Compare this server with others.

More servers

Other registry entries on npmjs.com, the ones next to this name; all of them.

io.github.Sisuthros/claude-amplifier · crashed on start
io.github.Skillproofdev/skillproof · alive
io.github.Skitchy/rekindle · crashed on start
io.github.Slowper/anylens · crashed on start
io.github.Sndevore77/glp1search · alive
io.github.Soboljem/transcribe-mcp · alive
io.github.Sofiia7/actually · needs env
ArcBounty io.github.Sofiia7/arcbounty-mcp · needs env

Servers that mention controller or lighting.

FrameThrower ai.framethrower/framethrower · alive
ai.smithery/keremurat-mcp · not found
3D New Era AI com.3dneweraai/newera · needs auth
com.lightres/booking · needs auth
Whoppah com.whoppah/commerce · alive
Cloudgate Workflow dev.cloudgate/workflow · needs auth
Regex Tester API io.github.Br0ski777/regex-generator · TLS error
Remotion-Factory io.github.Evozim/render-stream · not found

Badge for the README

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Atom feed

A mail when this server changes

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

For the publisher

The package did not start as an MCP server at its probe on 2026-11-15. One failed probe is not an outage: the board calls a package down when it fails again at its next probe, a week later.
The process exited on start before it answered initialize. The error output is above.