iDevice Buyer's Guide is an MCP server with 31 tools an agent can call, among them check_deal, compare_products, find_best_device. 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 4 of 4 times since 1 October 2026; the last check, on 16 November 2026, succeeded.
Independent buyer's guide for wearables and phones: buy now or wait, compatibility, prices. Sourced.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
check_deal | Whether a price offered for one product is a good deal: GOOD DEAL, NOT A GOOD DEAL or NOT ENOUGH DATA, on the same basis as should_i_buy. Compares the price with the lowest current retailer price iDevice read today, the lowest recent price Inputs: product_slug, price_usd, retailer |
compare_products | Side-by-side specs for 2 or 3 products, from the same engine as idevice.com/compare. Each cell carries Confirmed/Reported/Our read and its source outlet and date. Products in different categories are compared on shared structured facts only Inputs: product_slugs, specs |
find_best_device | A short ranked list of on-sale products in one category for a shopper: optionally the phone platform they use, a budget, and up to three priorities from the uses iDevice's Guides assign (for example sleep, running, battery-life, photos-vide Inputs: category, owned_platform, budget_usd, priorities, limit |
find_products | What is on sale in one category (glasses, rings, watches, earbuds, phones, headsets, fitness trackers), optionally at or under a price or from one company, cheapest first. Each carries its current retailer price with the retailer and date, Inputs: category, max_price, company, works_with |
get_best_for | What a product is best for, from its Guide's Best For: up to three uses, each with a one-line reason and how it is known (the official page, the specification, a reported detail, or iDevice's own judgement). Or pass use_case (for example 's Inputs: product_slug, use_case, category |
get_company_profile | A company as iDevice's public directory lists it: its name, homepage and a short description, the categories iDevice covers for it, and each of its products that has a Guide, with lifecycle, price and the Guide link. Pass the company's name Inputs: company |
get_compatibility | Whether a product works with a given phone or device, from its Guide's Works with tab: iPhone, Android, apps, other devices and standards. Each answer says Works, Works with limits (to a person, say "Some features missing" and name what is Inputs: product_slug, query |
get_detailed_facts | Every individual fact for one product, grouped by topic: water and durability, temperature, battery and charging, display, camera, audio, connectivity, health sensors, lenses and sun, size and weight, chip and software. Each carries its val Inputs: product_slug, topic, offset, limit |
get_guide_extras | Three parts of the Guide: section 'timeline' gives a product's Timeline tab events, oldest first, with their sources, plus the official lifecycle dates; section 'faq' gives the Guide's questions and answers (optional query narrows them); se Inputs: section, product_slug, term, query |
get_guide_summary | The buying summary of one product's Guide: its one-line summary and bottom line, the at-a-glance facts, price and dates, where it sits in its line (the newest released model), and the facts that bear on buying now or waiting: whether a newe Inputs: product_slug |
get_in_the_box | What ships in the box for one product, per model or configuration, as the official product page states it: each item, its quantity, whether it is included (false means the official page says it is not), and the page it came from. Optional v Inputs: product_slug, variant |
get_ownership_facts | What owning one product involves, each fact with its source page and date: the official return window, who pays return shipping and any restocking fee; the warranty length and what it covers; whether a subscription is needed, its price and Inputs: product_slug, section |
get_price_history | Dated prices for one product: today's verified price for this exact model (price_verified; when it is not verified the price is null and price_unverified_reason says Price not confirmed and why), when iDevice began checking it (tracking_sin Inputs: product_slug |
get_product | Lifecycle, official or estimated price, key dates, availability (on sale or not, release date and its basis, where to buy), report count and how well-sourced the reports are. Works for products with no reports yet. Inputs: product_slug |
get_product_facts | Official price (only when it was officially announced or is sold officially; otherwise labelled as an estimate), announcement and availability dates with their source, availability (is it on sale, and where to buy with the last price we rea Inputs: product_slug |
get_product_news | Latest iDevice news about one product, each story with the sources it rests on. Newest first: the title, the date, the story page on idevice.com, a one-line summary, the kind of story (standalone or cluster) and the outlets and links it is Inputs: product_slug, company_key, limit, since |
get_release_calendar | Products not yet on sale, in date order: a release date, an announcement event, or a window shown as written (for example Fall 2026), each with who stated it (Announced by the company, Company event, Reported date, Reported window, iDevice Inputs: from, to, category, company |
get_release_history | Every generation of a product's line with its announcement and release dates, sources and launch price, plus the gaps between releases: mean, median, shortest and longest, in days and months. Inputs: product_slug |
get_report_card | A roll-up of one product's pre-release reports by how they turned out (Right, Partly right, Wrong, Never settled, Not comparable, Not checked yet, No outcome yet), and the reports themselves, newest first: the date, a one-sentence summary, Inputs: product_slug, query |
get_reports | Every well-sourced pre-release report 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 Inputs: product_slug, category |
get_reviews | What other outlets scored one product: the Review Consensus (a normalized average, shown only from two scored reviews by two different publishers), the themes reviewers agree on, and each review with its outlet, published rating and link. T Inputs: product_slug |
get_variants_and_offers | The configurations of one product with their launch prices, to answer '$399 for which one?': storage, size, colour and material, each with its source; the retailer listings that are this exact model; and the conditions retailers attach to a Inputs: product_slug, retailer |
is_good_price | For one product: today's verified retailer price with the day it was read, compared with iDevice's own daily price record of this exact model: the low, median and high over two recent windows (last_30_days, and last_90_days once there is en Inputs: product_slug |
list_products | Every product iDevice covers, with its lifecycle (reported, announced, preorder, shipping, previous) and how many well-sourced reports it has (can be 0). Each entry includes its product_slug. Optional query filters by name, e.g. 'iphone 18 Inputs: query |
pick_between | For two or three products, which one the written buy-or-wait rules put ahead, or that neither is ahead, optionally for a shopper who owns a device or uses iPhone or Android, with a budget. Each product comes with its verdict (buy_now, wait, Inputs: product_slugs, owned_device_slug, owned_platform, budget_usd, buyer_context |
release_odds | For one product not yet released: the expected release window, how it is known (announced by the company, a reported window, an iDevice estimate, or the company's release cadence) with how sure iDevice is (Confirmed, Reported or Our read) a Inputs: product_slug |
search_reports | Find well-sourced pre-release reports by keyword across every covered product, e.g. 'battery', 'display', 'price'. Each result carries its status and product lifecycle. Up to 20 results per call; a more specific keyword narrows a longer lis Inputs: query, limit |
should_i_buy | For one product: buy now, wait, skip or check fit first, optionally for a shopper who already owns a device or uses iPhone or Android, with a budget or a use. Returns a verdict (buy_now, wait, skip, check_fit or not_enough_data) and the rul Inputs: product_slug, owned_device_slug, owned_platform, budget_usd, use_case, buyer_context |
source_track_record | For one reporter or outlet, by name: its pre-release reports graded against what the company later announced (Right, Partly right, Wrong), how many are not graded yet, the share right or partly right over graded reports only, its most recen Inputs: name |
whats_coming | For one product: its stage, the release window with who stated it (the company, a company event, pre-release reports, or iDevice's own estimate), and the pre-release reports its Guide lists, each with its status (Confirmed, Reported, Expect Inputs: product_slug |
whats_moved | The week's changes in iDevice's records: retailer price moves of at least 7% that held on at least two days (store, was and now, percent, the day last read), release windows that changed, and products that launched or changed stage, each wi Inputs: week |
Every block below points at https://idevice.com/api/mcp. Pick your client and copy.
claude mcp add --transport http idevice-buyer-s-guide https://idevice.com/api/mcp
{
"mcpServers": {
"idevice-buyer-s-guide": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://idevice.com/api/mcp"]
}
}
}{
"mcpServers": {
"idevice-buyer-s-guide": {
"url": "https://idevice.com/api/mcp"
}
}
}{
"servers": {
"idevice-buyer-s-guide": {
"type": "http",
"url": "https://idevice.com/api/mcp"
}
}
}{
"context_servers": {
"idevice-buyer-s-guide": {
"url": "https://idevice.com/api/mcp"
}
}
}{
"mcpServers": {
"idevice-buyer-s-guide": {
"serverUrl": "https://idevice.com/api/mcp"
}
}
}{
"mcpServers": {
"idevice-buyer-s-guide": {
"url": "https://idevice.com/api/mcp"
}
}
}name: iDevice Buyer's Guide
version: 0.0.1
schema: v1
mcpServers:
- name: iDevice Buyer's Guide
type: streamable-http
url: https://idevice.com/api/mcp{
"mcpServers": {
"idevice-buyer-s-guide": {
"httpUrl": "https://idevice.com/api/mcp"
}
}
}{
"mcpServers": {
"idevice-buyer-s-guide": {
"type": "http",
"url": "https://idevice.com/api/mcp"
}
}
}{
"mcpServers": {
"idevice-buyer-s-guide": {
"url": "https://idevice.com/api/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fidevice.com%2Fapi%2Fmcp&type=streamable_http&id=idevice-buyer-s-guide&name=iDevice%20Buyer%27s%20Guide
It answered our last check on 16 November 2026 in 483 ms. Over 4 checks since 1 October 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by idevice.com and served from idevice.com, the vendor's own domain: https://idevice.com/api/mcp.
31, as returned by the server's own tools/list on 19 November 2026: check_deal, compare_products, find_best_device, find_products, get_best_for, get_company_profile, get_compatibility, get_detailed_facts, and 23 more.
It answered our last check on 16 November 2026 in 483 ms. Over 4 checks since 1 October 2026 it answered 4.
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.
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.
Publisher: com.idevice. Endpoint host: idevice.com. ARD identifier: urn:air:com.idevice:mcp:wearables.
First indexed 1 October 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.