mcpbeat

iDevice Wearables MCP Server

io.github.ralphieusa/idevice-wearables
answering

iDevice Wearables is answering right now. Last checked 7 min ago. It exposes 4 tools.

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

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 39 hours of history · worst hour 75%
39 hours agonow
98.9%
Uptime 24h
90 of 91 checks
4
Tools
read from the server
287 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

run in your terminal
claude mcp add idevice-wearables --transport http https://idevice.com/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "idevice-wearables": {
      "url": "https://idevice.com/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.idevice-wearables]
url = "https://idevice.com/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "idevice-wearables": {
      "url": "https://idevice.com/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "idevice-wearables": {
      "url": "https://idevice.com/api/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

claims
get_claims
Every corroborated claim for one product: what is reported, how many outlets reported it, which outlet reported it first, and a link to the evidence on idevice.com.
search_claims
Find corroborated claims by keyword across every tracked product — e.g. 'battery', 'display', 'price'. Use when the product is not known in advance.
product
get_product
Release status, category, and how well-sourced the product's claims are overall.
products
list_products
Products with at least one well-sourced claim. Use this first to find the right product_slug for the other tools.

Endpoints

URLTransportStateLatencyChecked
https://idevice.com/api/mcp streamable-http answering 331 ms 7 min ago

iDevice Wearables — questions

Answers built from our own checks of this server.

What can iDevice Wearables do?
It exposes 4 tools, read directly from the server on our last check. Among them: get_claims, get_product, list_products, search_claims. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is iDevice Wearables working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 90 of 91 checks got a reply (98.9%), average response time 287 ms. The bar chart above shows every period we have measured.
Is iDevice Wearables still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect iDevice Wearables?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does iDevice Wearables need an API key?
No. iDevice Wearables completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is iDevice Wearables?
It answers our handshake in 287 ms on average, which is faster than 48% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.