io.github.Koneisto/HomeAssistant-Light-MCP

Is the io.github.Koneisto/HomeAssistant-Light-MCP MCP server down? Yes. It has given no valid answer since 2026-10-19: not found.

Control Home Assistant lights and scenes. Lights only by design for safety.

not found down since 2026-10-19 · probed 2026-11-14 · unchanged since 2026-10-26

npm error notarget In most cases you or one of your dependencies are requesting npm error notarget a package version that doesn't exist. npm error A complete lo

Run it: npx -y ha-mcp-server@0.6.1 (stdio, probed in a container with the network off)
Host: npmjs.com
Repository: https://github.com/Koneisto/HomeAssistant-Light-MCP
Registry: active, updated 2025-12-08 · 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.KnockOutEZ/wigolo · crashed on start
io.github.Koala-Studios/newton-browser · alive
io.github.KojimaHyui01/ja-normalize · crashed on start
komnet io.github.Komdosh/komnet · needs env
io.github.Koneisto/no-as-a-service · alive
io.github.Kosmo-Protocol/kosmo-mcp · alive
Project Bourne io.github.KozakHou/project-bourne · crashed on start
Webhook Crash Lab io.github.Krrishkumar125/webhook-crash-lab-mcp · alive

Servers that mention homeassistant or control or design.

io.github.homeassistant-ai/ha-mcp · needs env
io.github.daedalus/mcp-homeassistant · crashed on start
Agentic Fabrication Network (AFN) ai.agenticfabricationnetwork/ufp · alive
Authoryze ai.authoryze/authoryze · needs auth
Conveo ai.conveo/conveo · needs auth
ai.crayonz/mcp · needs auth
ai.creationloop/creationloop · alive
TVWizard ai.djwizard/tvwizard · TLS error

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

No valid answer since 2026-10-19, in every probe since then.
The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.