iDevice Wearables MCP Server

by ralphieusa Your server? Claim it

answering

iDevice Wearables is answering right now. Last checked 6 min ago. It exposes 6 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 52 days of history · worst day 92%

52 days agonow

92.3%

Uptime 24h

84 of 91 checks

Tools

read from the server

510 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 9

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 16 September 2026. No other catalogue keeps this.

15 Sep 4 tool descriptions were rewritten get_claims, get_product, list_products and 1 more

15 Sep 2 tools appeared compare_products, get_product_facts

15 Sep 2 tools changed the parameters they ask for get_product, list_products

15 Sep a tool changed version

iDevice Wearables does not always answer

Over the last week it answered 97.3% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

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 6

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 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.

search_claims

Find well-sourced claims by keyword across every tracked product, e.g. 'battery', 'display', 'price'. Each result carries its status and product lifecycle.

product

get_product

Lifecycle, official or estimated price, key dates, claim count and how well-sourced the claims are. Works for products with no claims yet.

get_product_facts

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.

compare

compare_products

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'].

products

list_products

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'.

Endpoints

URL	Transport	State	Latency	Checked
https://idevice.com/api/mcp	streamable-http	answering	455 ms	6 min ago

Alternatives to iDevice Wearables

same job, measured the same way

Adextract MCP

by anuragind003

Search Meta, Google Ads, LinkedIn, and TikTok ad libraries plus creative analysis via MCP.

answering

Google Search Console

by getmcpads

Google Search Console: 20 read-only tools for Search Analytics, sitemaps and indexing.

230 installs/wk local only

SEO Tools: Google Search Console

by antohins

Google Search Console: Search Analytics, URL Inspection, sitemaps (read-only, OAuth/service acct).

61 installs/wk local only

Agency MCP

by jiyumarketing-mcp

Run a marketing agency from Claude: Google Ads, Analytics, Search Console, Meta, WordPress and CRM.

answering

Googlesearch API

by jojapi

GoogleSearch API: Fetch real-time Google Search results including title, links Ideal for serp api.

1 tools answering

Google Search Console MCP

by a1-x-tech

MCP server for the Google Search Console API: search analytics, sitemaps, URL inspection, sites.

236 installs/wk local only

Google Search Console MCP

by scalably

Read-only Google Search Console MCP: Search Analytics, sitemaps, URL inspection. 5 tools.

local only

HYPD AI - Paid Ads & Analytics

by hypd-ai

Google Ads, Meta (Facebook) Ads, GA4 and Merchant Center analysis in plain language. Read-only.

answering

iDevice Wearables — questions

Answers built from our own checks of this server.

What can iDevice Wearables do?

It exposes 6 tools, read directly from the server on our last check. Among them: compare_products, get_claims, get_product, get_product_facts, 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 →

What is iDevice Wearables mostly used for?

Its tools cluster around claims and product. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is iDevice Wearables working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 84 of 91 checks got a reply (92.3%), average response time 510 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 6 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 510 ms on average, which is faster than 30% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.