iDevice Wearables
REMOTE · IDEVICE.COM · SCANNED SEP 20
Wearable tech roadmaps: Apple, Meta, Samsung, Google, Oura. Claims, timelines, analysis.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 632 tokens (~105/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the iDevice Wearables MCP server?
iDevice Wearables is a hosted endpoint at https://idevice.com/api/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 · idevice.com
claude mcp add --transport http ralphieusa-idevice-wearables 'https://idevice.com/api/mcp'
{
"mcpServers": {
"ralphieusa-idevice-wearables": {
"url": "https://idevice.com/api/mcp"
}
}
} {
"servers": {
"ralphieusa-idevice-wearables": {
"type": "http",
"url": "https://idevice.com/api/mcp"
}
}
} [mcp_servers.ralphieusa-idevice-wearables] url = "https://idevice.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ralphieusa-idevice-wearables": {
"type": "remote",
"url": "https://idevice.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add ralphieusa-idevice-wearables --url 'https://idevice.com/api/mcp' --transport streamable-http
mcp_servers:
ralphieusa-idevice-wearables:
url: "https://idevice.com/api/mcp" {
"McpServers": {
"ralphieusa-idevice-wearables": {
"Transport": "http",
"Url": "https://idevice.com/api/mcp"
}
}
} assistant mcp add ralphieusa-idevice-wearables -t streamable-http -u 'https://idevice.com/api/mcp'
{
"mcpServers": {
"ralphieusa-idevice-wearables": {
"type": "http",
"url": "https://idevice.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 16 Sept 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_claims” rewrote its description, which is the text the model reads security
- Tool “get_product” rewrote its description, which is the text the model reads security
- Tool “list_products” rewrote its description, which is the text the model reads security
- Tool “search_claims” rewrote its description, which is the text the model reads security
- Schema quality: 67 → 105 ▼ functional
- Tool coverage: 80% → 100% ▲ functional
- Schema quality: good → excellent functional
- Server version: 2.0.0 → 2.1.0 functional
- New tool “compare_products” functional
- New tool “get_product_facts” functional
- “list_products” added an optional parameter “query” cosmetic
- “get_product” reworded the description of “product_slug” cosmetic
- 30 Aug 26 +1
- Stability: 0.97 → pass security
- 28 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 1 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 20 Sept 2026 · Probed https://idevice.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=idevice.com | CN=YE2,O=Let's Encrypt,C=US | 27 Aug 2026 | 25 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 50e30d2751c25be9255855fd54c10be2b69 |
| SANs: *.idevice.com, idevice.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of idevice.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| idevice.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://idevice.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://idevice.com/api/mcp | HTTPS enforced | 301 | https://idevice.com/api/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 →
compare_products Compare two or three products ~116
Side-by-side specs for 2 or 3 products, from the same engine as idevice.com/compare. Each cell carries Confirmed/Rumored/Our read and its source outlet and date. Products in different categories are compared on shared structured facts only. Optional specs filters rows by keyword, e.g. ['battery','sleep'].
| Name | Type | Req | Description |
|---|---|---|---|
| product_slugs | array | yes | e.g. ['oura-ring-4','samsung-galaxy-ring-1'] |
| specs | array | – | Keywords to keep only matching rows |
No output schema declared.
No examples provided.
get_claims Get reported claims for a product ~109
Every well-sourced claim for one product, each with its status (Right, Partly right, Wrong, Never settled, Not comparable, Not checked yet, No outcome yet), how many outlets reported it, who reported it first, and a link to the evidence on idevice.com.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by claim type, e.g. 'hardware', 'design', 'pricing' |
| product_slug | string | yes | From list_products, e.g. 'apple-glasses' |
No output schema declared.
No examples provided.
get_product Get one product's status ~55
Lifecycle, official or estimated price, key dates, claim count and how well-sourced the claims are. Works for products with no claims yet.
| Name | Type | Req | Description |
|---|---|---|---|
| product_slug | string | yes | From list_products, e.g. 'apple-watch' |
No output schema declared.
No examples provided.
get_product_facts Get price, dates and specs for a product ~83
Official price (only when the maker announced or is selling it; otherwise labelled as an estimate), announcement and availability dates with their source, and specs. Every spec is marked Confirmed, Rumored, Our read or No source on file, with the source outlet and date.
| Name | Type | Req | Description |
|---|---|---|---|
| product_slug | string | yes | From list_products, e.g. 'apple-watch' |
No output schema declared.
No examples provided.
list_products List tracked products ~92
Every product iDevice tracks, with its lifecycle (rumored, announced, preorder, shipping, previous) and how many well-sourced claims it has (can be 0). Use this first to find the product_slug for the other tools. Optional query filters by name, e.g. 'iphone 18 pro'.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Words in the product name, e.g. 'galaxy ring' |
No output schema declared.
No examples provided.
search_claims Search claims across all products ~62
Find well-sourced claims by keyword across every tracked product, e.g. 'battery', 'display', 'price'. Each result carries its status and product lifecycle.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Default 20 |
| query | string | yes | Keyword or phrase |
No output schema declared.
No examples provided.
What is the iDevice Wearables MCP server?
iDevice Wearables is an MCP server listed in the public MCP registry as io.github.ralphieusa/idevice-wearables. Wearable tech roadmaps: Apple, Meta, Samsung, Google, Oura. Claims, timelines, analysis. This page covers its hosted endpoint (https://idevice.com/api/mcp).
Is the iDevice Wearables MCP server safe to use?
iDevice Wearables scores 82 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 iDevice Wearables MCP server expose?
iDevice Wearables exposes 6 tools: list_products, get_product, get_product_facts, compare_products, get_claims, search_claims. Their descriptions and schemas cost roughly 517 tokens of context every time the server is loaded.
Does the iDevice Wearables MCP server require authentication?
No. We connected to iDevice Wearables without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the iDevice Wearables MCP server still maintained?
iDevice Wearables is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.