Home / MCP registry index / io.kiloiot/kilo

Kilo IoT Platform

io.kiloiot/kilo in the official MCP registry. Endpoint https://mcp-auth.kiloiot.io/mcp. Source: github.com/Kiloiot/kilo-mcp.

The registry describes it as: The IoT platform where AI controls real-world devices: read, provision, automate and command.

On 2026-10-22 this server asked for credentials before it would list its tools, so we could not read them. Nothing was checked: this is not a clean result.

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-kiloiot-kilo/badge.svg)](https://lazaretto.dev/mcp-registry/io-kiloiot-kilo)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Smart home MCP servers

Order Group
co.ordergroup/public
2 tools, nothing matched
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