Adafruit IO MCP by usefulapi
REMOTE · ADAFRUIT-IO.USEFULAPI.IO
Read Adafruit IO feeds, data, groups and dashboards; publish a data point or create a feed.
Available components
Last scanned (5 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 18 Oct 2026.
Category IoT and Hardware
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1783 tokens (~104/item across 17 items; 17 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- The server now declares the “prompts” capability functional
- First check of Schema quality: 100 functional
- New prompt “getting_started” functional
- Server version: 1.0.0 → 1.1.0 functional
- 13 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Probed https://adafruit-io.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of adafruit-io.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://adafruit-io.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://adafruit-io.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://adafruit-io.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://adafruit-io.usefulapi.io/mcp |
| Authorisation server | https://adafruit-io.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://adafruit-io.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/adafruit-io/ |
| http (plaintext) | http://adafruit-io.usefulapi.io/mcp | Inconclusive | 302 | http://adafruit-io.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
adafruitio_create_feed Create feed ~98
WRITE: create a new, empty feed (private by default), optionally inside an existing group. Adds a feed only; it does not change or delete anything existing, and fails if the name is taken. POST /feeds.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Optional description. |
| group_key | string | – | Optional existing group key to create the feed in. |
| name | string | yes | Feed name (the key is derived from it). |
No output schema declared.
No examples provided.
adafruitio_get_dashboard Get dashboard ~34
One dashboard by key. GET /dashboards/{dashboard_key}.
| Name | Type | Req | Description |
|---|---|---|---|
| dashboard_key | string | yes | Dashboard key. |
No output schema declared.
No examples provided.
adafruitio_get_data_point Get data point ~89
One stored data point of a feed by its id. GET /feeds/{feed_key}/data/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| data_id | string | yes | Data point id (the `id` field of a data point). |
| feed_key | string | yes | Feed key (the URL-safe key shown in Adafruit IO, for example 'temperature'; 'group-key.feed-key' also works). |
No output schema declared.
No examples provided.
adafruitio_get_feed Get feed ~77
One feed by key: name, description, unit, visibility, last value, status settings and the groups it belongs to. GET /feeds/{feed_key}.
| Name | Type | Req | Description |
|---|---|---|---|
| feed_key | string | yes | Feed key (the URL-safe key shown in Adafruit IO, for example 'temperature'; 'group-key.feed-key' also works). |
No output schema declared.
No examples provided.
adafruitio_get_feed_chart Get feed chart data ~215
Aggregated chart data for a feed: values sliced by `resolution` minutes over the last `hours` (or a start/end range), using avg, sum, min, max, val or val_count. Good for trends without downloading every point. GET /feeds/{feed_key}/data/chart.
| Name | Type | Req | Description |
|---|---|---|---|
| end_time | string | – | ISO 8601 date or date-time, e.g. 2026-10-01T00:00:00Z. |
| feed_key | string | yes | Feed key (the URL-safe key shown in Adafruit IO, for example 'temperature'; 'group-key.feed-key' also works). |
| field | string | – | Aggregation (default avg). |
| hours | integer | – | Hours of history (ignored when start_time and end_time are given). |
| resolution | – | – | Slice size in minutes. |
| start_time | string | – | ISO 8601 date or date-time, e.g. 2026-10-01T00:00:00Z. |
No output schema declared.
No examples provided.
adafruitio_get_feed_details Get feed details ~74
A feed with its details block: first and last data point and the number of stored points. GET /feeds/{feed_key}/details.
| Name | Type | Req | Description |
|---|---|---|---|
| feed_key | string | yes | Feed key (the URL-safe key shown in Adafruit IO, for example 'temperature'; 'group-key.feed-key' also works). |
No output schema declared.
No examples provided.
adafruitio_get_group Get group ~36
One group by key with its feeds. GET /groups/{group_key}.
| Name | Type | Req | Description |
|---|---|---|---|
| group_key | string | yes | Group key. |
No output schema declared.
No examples provided.
adafruitio_get_last_data Get latest data point ~99
The most recent data point of a feed (value, location, created_at). GET /feeds/{feed_key}/data/last.
| Name | Type | Req | Description |
|---|---|---|---|
| feed_key | string | yes | Feed key (the URL-safe key shown in Adafruit IO, for example 'temperature'; 'group-key.feed-key' also works). |
| include | string | – | Comma-separated fields to return: value, lat, lon, ele, id, created_at. |
No output schema declared.
No examples provided.
adafruitio_get_throttle Get data rate limit ~61
The account's data rate limit (data-record modifications per minute: 30 on free accounts, 60 on Plus) and the current active data rate. Check it before publishing many points. GET /api/v2/{username}/throttle.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
adafruitio_get_user Get user ~50
The Adafruit IO account this key belongs to: id, name, username, time zone, created/updated times, plus the data rate limit when reported. GET /api/v2/user.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
adafruitio_list_activities List activity log ~116
The account's activity log (feed/data/dashboard changes), optionally within a time range. GET /activities.
| Name | Type | Req | Description |
|---|---|---|---|
| end_time | string | – | ISO 8601 date or date-time, e.g. 2026-10-01T00:00:00Z. |
| limit | integer | – | Maximum entries, 1-1000. |
| start_time | string | – | ISO 8601 date or date-time, e.g. 2026-10-01T00:00:00Z. |
No output schema declared.
No examples provided.
adafruitio_list_blocks List dashboard blocks ~63
The blocks (widgets: gauges, toggles, charts, sliders...) of a dashboard with their feeds, position and properties. Integration secrets in properties are removed. GET /dashboards/{dashboard_key}/blocks.
| Name | Type | Req | Description |
|---|---|---|---|
| dashboard_key | string | yes | Dashboard key. |
No output schema declared.
No examples provided.
adafruitio_list_dashboards List dashboards ~31
List the account's dashboards with key, name, description and visibility. GET /dashboards.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
adafruitio_list_feed_data List feed data ~252
Data points of a feed (max 1000 per call). Newest first, except that with start_time the API returns the oldest page after that time. Filter by time range and limit; to read further back call again with the reply's next_page_args (the same filters plus `before`). GET /feeds/{feed_key}/data.
| Name | Type | Req | Description |
|---|---|---|---|
| before | string | – | Pagination token: next_before from the previous reply (keep the same other arguments). |
| end_time | string | – | ISO 8601 date or date-time, e.g. 2026-10-01T00:00:00Z. |
| feed_key | string | yes | Feed key (the URL-safe key shown in Adafruit IO, for example 'temperature'; 'group-key.feed-key' also works). |
| include | string | – | Comma-separated fields to return: value, lat, lon, ele, id, created_at. |
| limit | integer | – | Maximum records to return, 1-1000 (default 100). |
| start_time | string | – | ISO 8601 date or date-time, e.g. 2026-10-01T00:00:00Z. |
No output schema declared.
No examples provided.
adafruitio_list_feeds List feeds ~43
List all of the account's feeds with key, name, description, unit, visibility, enabled flag, last value and last update. GET /feeds.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
adafruitio_list_groups List groups ~30
List the account's groups (named sets of feeds) with their feeds. GET /groups.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
adafruitio_publish_data_point Publish data point ~201
WRITE: publish one data point (a value) to a feed. This can drive REAL DEVICES: anything subscribed to the feed (relays, motors, lights, heaters, locks, dashboard toggles) will receive and may act on the value, and it cannot be undone from here. Only publish a value the user has asked for. Counts against the account's data rate limit (30 per minute on free accounts, 60 on Plus). POST /feeds/{feed_key}/data.
| Name | Type | Req | Description |
|---|---|---|---|
| ele | number | – | Elevation of the reading in meters. |
| feed_key | string | yes | Feed key (the URL-safe key shown in Adafruit IO, for example 'temperature'; 'group-key.feed-key' also works). |
| lat | number | – | Latitude of the reading. |
| lon | number | – | Longitude of the reading. |
| value | – | yes | The value to publish (text or number, up to 1000 characters). |
No output schema declared.
No examples provided.
How do I install the Adafruit IO MCP by usefulapi server?
Adafruit IO MCP by usefulapi is a hosted endpoint at https://adafruit-io.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · adafruit-io.usefulapi.io
claude mcp add --transport http io-usefulapi-adafruit-io 'https://adafruit-io.usefulapi.io/mcp'
What is the Adafruit IO MCP by usefulapi server?
Adafruit IO MCP by usefulapi is listed in the public MCP registry as io.usefulapi/adafruit-io. Read Adafruit IO feeds, data, groups and dashboards; publish a data point or create a feed. This page covers its hosted endpoint (https://adafruit-io.usefulapi.io/mcp).
Is the Adafruit IO MCP by usefulapi server safe to use?
Adafruit IO MCP by usefulapi scores 66 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Adafruit IO MCP by usefulapi server expose?
Adafruit IO MCP by usefulapi exposes 17 tools: adafruitio_get_user, adafruitio_get_throttle, adafruitio_list_feeds, adafruitio_get_feed, adafruitio_get_feed_details, and 12 more. Their descriptions and schemas cost roughly 1,569 tokens of context every time the server is loaded.
Does the Adafruit IO MCP by usefulapi server require authentication?
Yes. Adafruit IO MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Adafruit IO MCP by usefulapi server still maintained?
Adafruit IO MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.