Home / MCP registry index / io.usefulapi/adafruit-io
Adafruit IO MCP by usefulapi
io.usefulapi/adafruit-io in the official MCP registry.
Endpoint https://adafruit-io.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Read Adafruit IO feeds, data, groups and dashboards; publish a data point or create a feed.
We read its 17 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
adafruitio_get_user adafruitio_get_throttle adafruitio_list_feeds adafruitio_get_feed adafruitio_get_feed_details adafruitio_list_feed_data adafruitio_get_last_data adafruitio_get_data_point adafruitio_get_feed_chart adafruitio_list_groups adafruitio_get_group adafruitio_list_dashboards adafruitio_get_dashboard adafruitio_list_blocks adafruitio_list_activities adafruitio_publish_data_point adafruitio_create_feed
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-adafruit-io)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.