Home / MCP registry index / Topics / Smart home

Smart home MCP servers, with their tools checked

Every server in the official MCP registry that mentions Smart home, with a public endpoint, read the way an MCP client reads it and checked for tool poisoning. The list updates as the registry does, and each server is read again every week.

12 listed. We have read the tools of 1 so far; the others want credentials first, could not be reached, or are still waiting for their first read.

Infrastructure servers can change live systems. Check which tools write, deploy or delete before you connect one with real credentials.

Order Group co.ordergroup/public	2 tools, nothing matched 2026-10-22
Kilo IoT Platform io.kiloiot/kilo	needs credentials to list tools 2026-10-22
PostData cloud.postdata/postdata	not read yet
Loxone AI com.loxoneai/loxone-ai	not read yet
com.smarthomeexplorer.www/product-intelligence com.smarthomeexplorer.www/product-intelligence	not read yet
Soracom Knowledge com.soracom/knowledge	not read yet
Chirp Home Automation io.chirpwireless/chirp	not read yet
Band Atlas (Hyper Nexus) io.github.365724-ctrl/band-atlas	not read yet
Catherine Ives-Yim: writing and assessments io.github.catherine-development/ives-yim	not read yet
io.github.FoundryNet/foundrynet-inference io.github.FoundryNet/foundrynet-inference	not read yet
HardwareMCP io.github.saadvz/hardwaremcp	not read yet
TaskMan of London london.taskman/home-services	not read yet

Choosing one

Open a server's page to see the tools it advertises, whether it sets instructions for the model, and our latest read. Here, 1 of the servers shown matched none of our tool-poisoning rules on their last read. A clean read means our rules found nothing, not that a server is harmless; still check what access it asks for. To check one that is not listed, paste its URL into the free MCP server check.