Other · Remote MCP server
iDevice Wearables
Wearables and phones: prices, availability, compatibility, specs, comparisons, leak claims. No key.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.idevice/wearables- Version
- 2.2.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-10-01
- Updated
- 2026-10-01
- Publisher
- com.idevice
- Namespace
- Namespace verified by the MCP Registry via the domain idevice.com · how
- Website
- idevice.com/mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://idevice.com/api/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- idevice-wearables 2.5.0 · protocol 2025-06-18
- Tools discovered
16 - show names
list_products,get_product,get_product_facts,compare_products,get_compatibility,get_reports,search_reports,get_in_the_box,get_release_history,get_reviews,get_price_history,get_detailed_facts,get_release_calendar,find_products,get_guide_summary,get_report_card- Checked on
- 2026-10-05
How to connect iDevice Wearables
iDevice Wearables is a remote MCP server: there is nothing to install. Its endpoint is https://idevice.com/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| Identik Firma DigitalFirma digital argentina (Ley 25.506) con certificados de certificador licenciado. | Remote · HTTPLive check: ✓ handshake |
| Identik Firma ElectrónicaFirma electrónica argentina (Ley 25.506): enviar documentos a firmar, seguir estado y validar. | Remote · HTTPLive check: ✓ handshake |
| IdentityMCP server for VerusID identities - register, update, revoke, recover, query, set timelock. | Local · stdio |
| Identity AIopsGoverned Keycloak + authentik identity ops: users, events, clients, MFA, RCA. 29 tools. | Local · stdio |
| Idf EventsÎle-de-France (Greater Paris) Events MCP. | Remote · HTTPLive check: ✓ handshake |
| Idf MCPTurn an IDF domain into an MCP server with invariants and role scopes in every tool description. | Local · stdio |
| Idiolect AILoads your personal writing voice into any AI and scores how closely a draft matches it. | Remote · HTTPLive check: sign-in required |
| IdiosPrivate escrow for AI agent work on Beam: verifiable delivery, worker collateral, M of N disputes. | Local · stdio |