iDevice Buyer's Guide MCP server
com.idevice/wearablesidevice.comstreamable-httpv2.18.0Scanned
Independent buyer's guide for wearables and phones: buy now or wait, compatibility, prices. Sourced.
31 tools: 8 change things and 23 only read.
- Reads private data · 2
- Reads text others write · 1
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
8 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the iDevice Buyer's Guide MCP server can do
The iDevice Buyer's Guide MCP server is published by idevice.com, a domain the MCP Registry verified. It has 31 tools. It can create or change data (8 tools: should_i_buy, check_deal, pick_between, whats_coming and 4 more), but cannot delete data. 23 tools only read.
2 tools read private data (get_release_calendar and get_company_profile); 1 tool brings in text other people can write (get_reviews).
The fixed checks matched 2 findings (long-description). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 3 times since Anlyon Radar first saw them.
Last scanned Nov 11, 2026, version 2.18.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
31 tools
Changes things 8Claude Code: ask
check_dealWhether a price offered for one product is a good deal: GOOD DEAL, NOT A GOOD DEAL or NOT ENOUGH DATA, by the same written rules as should_i_buy.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Whether a price offered for one product is a good deal: GOOD DEAL, NOT A GOOD DEAL or NOT ENOUGH DATA, by the same written rules as should_i_buy. Compares the price with the lowest current retailer price iDevice read today, the lowest verified price of this exact model (over low_period_days, said as low_period; only once iDevice has 30 days of verified checks, and called a 90-day low only when 90 days are covered) and the near-low band the rules use, and gives the buy-or-wait verdict at that price where the rules can state one. Each line says what it rests on. No model is involved and no probability is given. A line slug (for example 'samsung-galaxy-ring') names the line's newest model; when that model is not on sale the answer is for the newest model of the line that is, and resolved_to says which and why.
Annotations the server declares
- title: Is this price a good deal
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
- idempotentHint: true
is_good_priceFor 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 the las…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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 the last 30 days and, once 90 days are covered, the last 90 days, each with its dates; where today sits against them in percent; and a verdict, good_price, normal, wait or not_enough_data, which is iDevice's published Prices verdict for the product. No low is stated under 30 days of checks, and no price is stated without the day it was read.
Annotations the server declares
- title: Is today's price a good price
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
- idempotentHint: true
pick_betweenFor 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…1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
The description is 2,344 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...ffer from this tool's answer for a phone platform or a budget given as arguments."
Description, as the server wrote it 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, skip, check_fit or not_enough_data), its fit with the phone given, today's retailer price and the reasons, each with its source and how sure iDevice is. A product that does not work with the phone given goes last; then the verdict decides, then the fit answer. Price alone does not put one ahead. When the rules leave two products level, review_tiebreak says whether outlets' published review scores separate them (at least two independent outlets that reviewed each, all one way, a clear margin) and lists the themes reviewers agree on, each with the outlets that reported it. purchase_today and product_for_you split the answer in two: the better purchase today on the rules, and the better product, named only on the phone or fit answer or on outlets' review scores, else No clear winner; where the companies' own figures lean one way, product_for_you says which product leads on which criteria, conditionally, and names no winner (lead null). A lead on the verdict alone (lead_basis timing) is about when to buy, not which product is better; a product that only reads BUY NOW or FINE TO BUY against NO RUSH is not a lead, and a product whose answer is not_enough_data (NEWER MODEL OUT, NOT ENOUGH DATA) is not out-bought unless the other product is its own newer model already out. The same comparison as the decision card on idevice.com. No model is involved. A line slug (for example 'samsung-galaxy-ring') names the line's newest model; when that model is not on sale the answer is for the newest model of the line that is, and resolved_to says which and why. With buyer_context, the answer also carries buyer_decision: the personal answer the idevice.com decision page for the same question gives for that context (a recommendation class, its rule_id, the decisive factors, the trade-offs, what would change it and what is unknown, each with its evidence), and buyer_decision_info with the same answer in plain words and the page it belongs to. buyer_decision.base_answers are that page's own answers, which can differ from this tool's answer for a phone platform or a budget given as arguments.
Annotations the server declares
- title: Pick between two or three products
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
- idempotentHint: true
release_oddsFor 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) …No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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) and who stated it, and the published probability where iDevice publishes one: how often reported windows of that width have held for products later announced, for the window's calendar year and for the window as stated, with the sample size. A window with no recorded basis, or a reported window with no recorded source, is refused (answered: false, refused says why); so is a product already released.
Annotations the server declares
- title: Release window and its odds
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
- idempotentHint: true
should_i_buyFor 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.1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
The description is 2,995 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...ffer from this tool's answer for a phone platform or a budget given as arguments."
Description, as the server wrote it 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 rule behind it, reasons that each carry a source link and how sure iDevice is (Confirmed, Reported, Our read or Not confirmed), the fit with the shopper's phone platform, timing (a newer model out, announced or reported), price (iDevice's published verdict and the lowest verified price over the period iDevice has checked it, low_period; none under 30 days of checks), what changed from the model the shopper owns when that comparison is available, and which of those four parts could not be answered. Reported dates are worded as reported. No probability is given. For a shopper who owns the model this one directly replaces, the answer also carries the two parts the /upgrade page on idevice.com says apart: upgrade_merit, whether replacing the owned model is worth it (worth_upgrading, not_a_clear_upgrade, depends_on_your_needs or too_early_to_say), and purchase_timing, whether today is a good time to buy the new one (good_time_to_buy, fine_at_this_price, no_rush, wait_for_price, newer_model_close, newer_model_out, price_not_confirmed or not_on_sale_yet), each with its basis, and upgrade_answer, both parts in the page's own words; all five are null for any other question. decision_word is the word iDevice shows for the verdict: BUY NOW, FINE TO BUY (a buy_now because the model is new and at its launch price, with no price signal: no reason to wait, no deal to chase), NO RUSH, WAIT, SKIP, KEEP YOURS, UPGRADE, CHECK FIT, NOT ENOUGH DATA or NEWER MODEL OUT (PRICE NOT CONFIRMED when no price is confirmed for the exact model); the verdict field is the same whichever word is shown. display_label is the same answer in the words idevice.com prints (Good to buy, Fine to buy, No need to rush, Wait for a better price (a wait on the price; wait_basis "price"), Wait (a wait for a newer model, or a product not on sale yet), Look elsewhere, Newer model out, Price not confirmed, Keep what you have, Worth upgrading, Check the fit first, Too early to say); say that label to a person, and key on decision_word. A line slug (for example 'samsung-galaxy-ring') names the line's newest model; when that model is not on sale the answer is for the newest model of the line that is, and resolved_to says which and why. With buyer_context, the answer also carries buyer_decision: the personal answer the idevice.com decision page for the same question gives for that context (a recommendation class, its rule_id, the decisive factors, the trade-offs, what would change it and what is unknown, each with its evidence), and buyer_decision_info with the same answer in plain words and the page it belongs to. buyer_decision.base_answers are that page's own answers, which can differ from this tool's answer for a phone platform or a budget given as arguments.
Annotations the server declares
- title: Should I buy this
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
- idempotentHint: true
source_track_recordFor 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 ri…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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 recent graded reports with their dates, and the reports iDevice credits it with being first to make. profile_url links its page on idevice.com when that page holds a reporting record.
Annotations the server declares
- title: A reporter's or outlet's track record
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
- idempotentHint: true
whats_comingFor 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 Gu…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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, Expected or Our estimate), the track record of reporting like it with the group that record comes from, how many independent origins and outlets carried it, whether sources disagree, and the outlet and link it names. A detail that has already turned out right or wrong is not listed. The same rows as the Guide's own tab on idevice.com.
Annotations the server declares
- title: What is coming for a product
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
- idempotentHint: true
whats_movedThe 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 c…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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 with its Guide link. Optional week is the last day of the week asked (YYYY-MM-DD, up to 26 weeks back); without it, the 7 days to now.
Annotations the server declares
- title: What moved this week
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
- idempotentHint: true
Only reads 23Show 23 read-only tools
compare_productsSide-by-side specs for 2 or 3 products, from the same engine as idevice.com/compare.No findings
Why it is in this group
- The name "compare_products" says "compare": a word for reading.
Description, as the server wrote it 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. Optional specs filters rows by keyword, e.g. ['battery','sleep'].
Annotations the server declares
- title: Compare two or three products
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
- idempotentHint: true
find_best_deviceA 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 a…No findings
Why it is in this group
- The name "find_best_device" says "find": a word for reading.
Description, as the server wrote it 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-video). Each product comes with its verdict (buy_now or wait), its fit with the phone given, today's retailer price, a one-line reason and its sources, and the place its Guide gives a named priority. In the list: a verdict of Buy now or Wait, and Works or Works with limits with the phone given. Order: the verdict, then the fit answer, then where the product's Guide places a named priority among the uses it lists, then price. A priority outside the Guides' uses is refused and the uses are listed. The same list rule as the decision card on idevice.com. No model is involved. For earbuds, when iDevice's earbuds recommendation is published, the order is that recommendation's instead: quality and fit from independent reviewers' findings, card by card (all-around, music and sound, workouts, noise cancellation, calls, value), with the buy-or-wait verdict shown beside each product, where it does not move the product; the answer adds a recommendation block naming each card's pick, strong choices or why there is none, and reads at most two priorities from calls, sound, anc, workouts and comfort. iDevice's own pick answers first, in every category it covers (earbuds, headphones, watches, fitness trackers, glasses, headsets and phones): the product it names for your question, then the alternatives it names, each with its verdict, fit, price and sources, and a best_answer block with the reviews behind the pick. Your phone and budget decide which products fit you, not which is better. Priorities are the uses the pick covers (for example sleep, running, battery life, calls); a use outside them is refused and the uses are listed.
Annotations the server declares
- title: Find the device that fits
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
- idempotentHint: true
find_productsWhat 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.No findings
Why it is in this group
- The name "find_products" says "find": a word for reading.
Description, as the server wrote it 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, its list price, iDevice's published verdict and the Guide link. Current and previous models are listed; pre-orders and unreleased products are in get_release_calendar.
Annotations the server declares
- title: Find products by category and price
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
- idempotentHint: true
get_best_forWhat 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, o…No findings
Why it is in this group
- The name "get_best_for" says "get": a word for reading.
Description, as the server wrote it 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 'sleep', 'running', 'gaming', 'travel', 'photos and video') with an optional category to list the products on sale whose Guide puts that use in its top three.
Annotations the server declares
- title: What a product is best for
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
- idempotentHint: true
get_company_profileA 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 …Reads private dataNo findings
Why it is in this group
- The name "get_company_profile" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "directory": it reads files.
Description, as the server wrote it 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 or key, for example 'oura' or 'Samsung'.
Annotations the server declares
- title: A company and the products iDevice covers for it
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
- idempotentHint: true
get_compatibilityWhether a product works with a given phone or device, from its Guide's Works with tab: iPhone, Android, apps, other devices and standards.No findings
Why it is in this group
- The name "get_compatibility" says "get": a word for reading.
Description, as the server wrote it 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 missing), Needs extra hardware, Does not work or Not confirmed, with its requirements, limits, an evidence word (Confirmed, Reported, Our read or Not confirmed) and the source page link. Not confirmed means unknown, never incompatible. Optional query narrows to one thing, e.g. 'iphone' or 'android'.
Annotations the server declares
- title: What a product works with
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
- idempotentHint: true
get_detailed_factsEvery individual fact for one product, grouped by topic: water and durability, temperature, battery and charging, display, camera, audio, connectivity, health sensors, lenses and s…No findings
Why it is in this group
- The name "get_detailed_facts" says "get": a word for reading.
Description, as the server wrote it 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 value, unit, who stated it (Confirmed is an official first-party statement) and the source page. Optional topic narrows the list, e.g. 'temperature' or 'battery'. A product with more than 20 facts is read in pages with offset and limit.
Annotations the server declares
- title: Detailed facts for a product
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
- idempotentHint: true
get_guide_extrasThree 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 Gui…No findings
Why it is in this group
- The name "get_guide_extras" says "get": a word for reading.
Description, as the server wrote it 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); section 'glossary' defines one term, the same text as the Guide's mouse-over.
Annotations the server declares
- title: A Guide's timeline, FAQ and glossary
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
- idempotentHint: true
get_guide_summaryThe 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 …No findings
Why it is in this group
- The name "get_guide_summary" says "get": a word for reading.
Description, as the server wrote it 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 newer model is out or announced, the expected window with who stated it, the current retailer read against the list price and the lowest and typical price seen, and iDevice's published verdict with its reasons.
Annotations the server declares
- title: A product's Guide summary
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
- idempotentHint: true
get_in_the_boxWhat 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…No findings
Why it is in this group
- The name "get_in_the_box" says "get": a word for reading.
Description, as the server wrote it 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 variant narrows to one configuration.
Annotations the server declares
- title: What is in the box
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
- idempotentHint: true
get_ownership_factsWhat 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…No findings
Why it is in this group
- The name "get_ownership_facts" says "get": a word for reading.
Description, as the server wrote it 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 the first-year cost where the price and billing period are both stated; the official support status as of a stated date; and published recalls, service programs and security-update windows. Optional section narrows the answer to one part.
Annotations the server declares
- title: What owning a product commits you to
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
- idempotentHint: true
get_price_historyDated 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 conf…No findings
Why it is in this group
- The name "get_price_history" says "get": a word for reading.
Description, as the server wrote it 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_since) and on how many days (history_days). Lows come only from verified checks of this exact model, one price a day: none under 30 days of checks; from 30 to 89 days the low (lowest_checked) with the days it covers (low_period_days, low_period), and lowest_last_30_days with the 30-day low and high; lowest_last_90_days only when 90 days are covered. Also the researched history (first and last observation, range, the points themselves, with bundles and refurbs marked and left out of the range).
Annotations the server declares
- title: Price history
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
- idempotentHint: true
get_productLifecycle, 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.No findings
Why it is in this group
- The name "get_product" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get one product's status
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
- idempotentHint: true
get_product_factsOfficial price (only when it was officially announced or is sold officially; otherwise labelled as an estimate), announcement and availability dates with their source, availability…No findings
Why it is in this group
- The name "get_product_facts" says "get": a word for reading.
Description, as the server wrote it 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 read), a short compatibility summary, and specs. Every spec is marked Confirmed, Reported, Our read or Not confirmed, with the source outlet and date.
Annotations the server declares
- title: Get price, dates and specs for a product
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
- idempotentHint: true
get_product_newsLatest iDevice news about one product, each story with the sources it rests on.No findings
Why it is in this group
- The name "get_product_news" says "get": a word for reading.
Description, as the server wrote it 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 based on (outlet, URL, date). The same stories as the News tab on the product's Guide. Optional limit (default 5, at most 15) and since (YYYY-MM-DD); a company_key returns a company's news instead. A story with no source link says so.
Annotations the server declares
- title: Latest news about a product
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
- idempotentHint: true
get_release_calendarProducts 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 comp…Reads private dataNo findings
Why it is in this group
- The name "get_release_calendar" says "get": a word for reading.
What it can reach
- private-dataThe name "get_release_calendar" says "get" and "calendar": it reads calendars.
Description, as the server wrote it 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 estimate) and how many pre-release reports it has. Defaults to the next 120 days; optional from and to (YYYY-MM-DD, at most one year), category (watches, earbuds, glasses, phones, rings) and company narrow it. Products with no dated or sourced window are counted, not listed.
Annotations the server declares
- title: Release calendar
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
- idempotentHint: true
get_release_historyEvery 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 …No findings
Why it is in this group
- The name "get_release_history" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Release history and gaps between releases
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
- idempotentHint: true
get_report_cardA 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 …No findings
Why it is in this group
- The name "get_report_card" says "get": a word for reading.
Description, as the server wrote it 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, who reported it, the outlet that carried it, its status and a link on idevice.com. Optional query narrows the reports to words in the summary or the outlet.
Annotations the server declares
- title: Report card for a product's pre-release reports
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
- idempotentHint: true
get_reportsEvery 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 o…No findings
Why it is in this group
- The name "get_reports" says "get": a word for reading.
Description, as the server wrote it 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 evidence on idevice.com.
Annotations the server declares
- title: Get pre-release reports for a product
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
- idempotentHint: true
get_reviewsWhat 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, a…Reads text others writeNo findings
Why it is in this group
- The name "get_reviews" says "get": a word for reading.
What it can reach
- untrusted-inputThe name "get_reviews" says "get" and "review": it reads comments, which other people can write.
- untrusted-inputThe description's first sentence says "review": it reads comments, which other people can write.
Description, as the server wrote it 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. The scores are the outlets' work; iDevice did not test these products for them.
Annotations the server declares
- title: Reviews and review consensus
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
- idempotentHint: true
get_variants_and_offersThe 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 ar…No findings
Why it is in this group
- The name "get_variants_and_offers" says "get": a word for reading.
Description, as the server wrote it 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 member price, coupon, bundle, refurbished or trade-in offer, for the retailers where iDevice has read a price for it. Pass retailer (for example 'Best Buy') to see one store's conditions, with or without a product.
Annotations the server declares
- title: Configurations, listings and offer conditions
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
- idempotentHint: true
list_productsEvery product iDevice covers, with its lifecycle (reported, announced, preorder, shipping, previous) and how many well-sourced reports it has (can be 0).No findings
Why it is in this group
- The name "list_products" says "list": a word for reading.
Description, as the server wrote it 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 pro'. A line slug such as 'samsung-galaxy-ring' names the line's newest model (which can be one not yet on sale); a generation slug such as 'samsung-galaxy-ring-1' names one model; is_line: true marks a line slug, and part_of names a generation's line. Up to 20 entries per call with the total; a query narrows a longer list.
Annotations the server declares
- title: List tracked products
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
- idempotentHint: true
search_reportsFind well-sourced pre-release reports by keyword across every covered product, e.g.No findings
Why it is in this group
- The name "search_reports" says "search": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Search pre-release reports across all products
- readOnlyHint: true
- openWorldHint: false
- destructiveHint: false
- idempotentHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:40 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 8
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 8 tools that change things (8 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://idevice.com/api/mcp: tools/list returned 31 tools to an anonymous client, including should_i_buy (write), check_deal (write), pick_between (write), whats_coming (write), is_good_price (write) and 3 more
Posture changes
- Nov 6, 2026
- Tools that change things, listed without credentials: 4 to 8
Findings
Matches of fixed checks, with the text they matched.
- Infoshould_i_buy
The description is 2,995 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...ffer from this tool's answer for a phone platform or a budget given as arguments."
- Infopick_between
The description is 2,344 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...ffer from this tool's answer for a phone platform or a budget given as arguments."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:should_i_buyChanges thingsdescription
PostureRemote posture changed. Tools that change things, listed without credentials: 4 -> 8.View diff
- Tools that change things, listed without credentials: 4 to 8
Tools4 added.+4 addedView diff
- Added:is_good_priceChanges things
- Added:release_oddsChanges things
- Added:source_track_recordChanges things
- Added:whats_movedChanges things
Tools2 changed.~2 changedView diff
- Changed:find_best_deviceOnly readsdescriptioninputSchema
- Changed:get_compatibilityOnly readsdescription
Install
Pinned to version 2.18.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http wearables https://idevice.com/api/mcpclaude mcp add --transport http wearables https://idevice.com/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__wearables__find_best_device",
"mcp__wearables__get_product_news",
"mcp__wearables__list_products",
"mcp__wearables__get_product",
"mcp__wearables__get_product_facts",
"mcp__wearables__compare_products",
"mcp__wearables__get_compatibility",
"mcp__wearables__get_reports",
"mcp__wearables__search_reports",
"mcp__wearables__get_in_the_box",
"mcp__wearables__get_release_history",
"mcp__wearables__get_reviews",
"mcp__wearables__get_price_history",
"mcp__wearables__get_detailed_facts",
"mcp__wearables__get_release_calendar",
"mcp__wearables__find_products",
"mcp__wearables__get_guide_summary",
"mcp__wearables__get_report_card",
"mcp__wearables__get_ownership_facts",
"mcp__wearables__get_best_for",
"mcp__wearables__get_variants_and_offers",
"mcp__wearables__get_company_profile",
"mcp__wearables__get_guide_extras"
],
"ask": [
"mcp__wearables__should_i_buy",
"mcp__wearables__check_deal",
"mcp__wearables__pick_between",
"mcp__wearables__whats_coming",
"mcp__wearables__is_good_price",
"mcp__wearables__release_odds",
"mcp__wearables__source_track_record",
"mcp__wearables__whats_moved"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as wearables. Review it before you use it.
Capability tags behind 3 rules
- mcp__wearables__get_reviews untrusted-input
- mcp__wearables__get_release_calendar private-data
- mcp__wearables__get_company_profile private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.idevice/wearables/verify?hash=898452832cb088a23e1d2d5f9ee4a197e81f4f14c02d4e1b8be10c10ee137aa5" | jq -e '.changed == false'Pinned hash 898452832cb0, from Nov 11, 2026, 22:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.idevice/wearables/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.idevice/wearables)Source: MCP Registry · repository. Synced Oct 30, 2026, 07:17 UTC.
iDevice Buyer's Guide MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the iDevice Buyer's Guide MCP server safe?
- No scan can promise that. What its definitions show: 31 tools, 8 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the iDevice Buyer's Guide MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the iDevice Buyer's Guide MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the iDevice Buyer's Guide MCP server have?
- 31 tools: 8 write, 23 read. should_i_buy, check_deal, pick_between, whats_coming, is_good_price, release_odds, source_track_record, whats_moved and 23 more.
Does the iDevice Buyer's Guide MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the iDevice Buyer's Guide MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the iDevice Buyer's Guide MCP server changed its tools?
- Yes, 3 times since Anlyon Radar started tracking it, most recently on Nov 11, 2026. Every change is on this page and in its Atom feed.