Index / MCP servers / iDevice Wearables

iDevice Wearables MCP server

Connect iDevice Wearables and your agent gets 6 tools, among them compare_products, get_claims, get_product. It answers at https://idevice.com/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 7 times since 11 September 2026; the last check, on 11 November 2026, succeeded.

Status
Answering
Tools
6
Reliability
6 of 7 checks
Response time
611 ms
Transport
streamable HTTP
Last checked
11 November 2026

Wearable tech roadmaps: Apple, Meta, Samsung, Google, Oura. Claims, timelines, analysis.

Description as the publisher wrote it.

The 6 tools iDevice Wearables offers

ToolWhat it does
compare_productsSide-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.
Inputs: product_slugs, specs
get_claimsEvery 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
Inputs: product_slug, category
get_productLifecycle, official or estimated price, key dates, claim count and how well-sourced the claims are. Works for products with no claims yet.
Inputs: product_slug
get_product_factsOfficial 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, wi
Inputs: product_slug
list_productsEvery 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 n
Inputs: query
search_claimsFind well-sourced claims by keyword across every tracked product, e.g. 'battery', 'display', 'price'. Each result carries its status and product lifecycle.
Inputs: query, limit

Add iDevice Wearables to your AI client

Every block below points at https://idevice.com/api/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http idevice-wearables https://idevice.com/api/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "idevice-wearables": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://idevice.com/api/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "idevice-wearables": {
      "url": "https://idevice.com/api/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "idevice-wearables": {
      "type": "http",
      "url": "https://idevice.com/api/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "idevice-wearables": {
      "url": "https://idevice.com/api/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "idevice-wearables": {
      "serverUrl": "https://idevice.com/api/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "idevice-wearables": {
      "url": "https://idevice.com/api/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: iDevice Wearables
version: 0.0.1
schema: v1
mcpServers:
  - name: iDevice Wearables
    type: streamable-http
    url: https://idevice.com/api/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "idevice-wearables": {
      "httpUrl": "https://idevice.com/api/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "idevice-wearables": {
      "type": "http",
      "url": "https://idevice.com/api/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "idevice-wearables": {
      "url": "https://idevice.com/api/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fidevice.com%2Fapi%2Fmcp&type=streamable_http&id=idevice-wearables&name=iDevice%20Wearables

Is iDevice Wearables up right now?

It answered our last check on 11 November 2026 in 611 ms. Over 7 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to iDevice Wearables

Questions about iDevice Wearables

How many tools does iDevice Wearables have?

6, as returned by the server's own tools/list on 20 September 2026: compare_products, get_claims, get_product, get_product_facts, list_products, search_claims.

Is iDevice Wearables down?

It answered our last check on 11 November 2026 in 611 ms. Over 7 checks since 11 September 2026 it answered 6.

How do I add iDevice Wearables to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://idevice.com/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does iDevice Wearables need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: io.github.ralphieusa. Endpoint host: idevice.com. ARD identifier: urn:air:io.github.ralphieusa:mcp:idevice-wearables. First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.