_ registry / mcp + a2a http-sse · checked 1h ago

idevice-wearables

https://idevice.com

Registry code: ede7590612532c0b

api record

iDevice is an independent buyer's guide for wearables and phones, as tools: what to buy, what works with what, whether to buy now or wait, and what is coming. Every fact shows its source and how sure we are, as Confirmed, Reported, Our read or Not confirmed; "Not confirmed" means unknown, not incompatible. list_products returns each product's product_slug. Tools by question: should I buy it, should_i_buy; this or that, pick_between or compare_products; is this price good, check_deal; what fits me in a category, find_best_device or find_products; does it work with my phone, get_compatibility;…

endpoint
https://idevice.com/api/mcp
door code
d37154d5144ea6f3
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is idevice-wearables live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is idevice-wearables free to use?
Yes — the hub reached it with no key and no payment.
What tools does idevice-wearables have?
31 tools: get_compatibility, get_reports, search_reports, get_release_history, get_detailed_facts, whats_moved, get_in_the_box, get_price_history, ….
Is idevice-wearables safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.2%

90 days 98.9%· all time 99.1%

latency
435ms

last good check

priced tools
0

of 31 tools

_ answered our checks, 90 days 268 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· endpoint unreachable (timeout after 20000ms); card still served
  • degraded → live
  • live → degraded· timeout after 20000ms
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 31 tools
5 open 26 never probed 5 of 31 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_release_calendar open 15h ago

    Products not yet on sale, in date order, with the date or window and who stated it; default the next 120 days. Up to 20 per call.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "to": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Last day, YYYY-MM-DD. Default 120 days after from; at most 366 days."
        },
        "from": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "First day, YYYY-MM-DD"
        },
        "company": {
          "type": "string",
          "description": "A company or brand, e.g. 'samsung'"
        },
        "category": {
          "type": "string",
          "description": "A category, e.g. 'watches'"
        }
      },
      "additionalProperties": false
    }
    arguments 24 lines
  • get_best_for open 15h ago

    What one product is best for, from its Guide, with how each use is known; or, with use_case, the products whose Guide ranks that use in its top three.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "category": {
          "type": "string",
          "description": "Narrows a use_case search, e.g. 'rings'"
        },
        "use_case": {
          "type": "string",
          "description": "A use, e.g. 'sleep'"
        },
        "product_slug": {
          "type": "string",
          "description": "A product_slug, e.g. 'oura-ring-4'"
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • get_variants_and_offers open 12h ago

    One product's configurations with launch prices, its exact retailer listings, and the conditions on member, coupon, bundle, refurbished or trade-in prices.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "retailer": {
          "type": "string",
          "description": "A store name, e.g. 'Costco'"
        },
        "product_slug": {
          "type": "string",
          "description": "A product_slug, e.g. 'oura-ring-4'"
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • list_products open 12h ago

    Every product iDevice covers, with its product_slug, lifecycle and report count; optional query filters by name. is_line marks a line slug, part_of a generation's line. Up to 20 per call.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "query": {
          "type": "string",
          "description": "Words in the product name, e.g. 'galaxy ring'"
        }
      },
      "additionalProperties": false
    }
    arguments 10 lines
  • get_product_news open 15h ago

    Latest iDevice news about one product, each story with the sources it rests on. Newest first; optional limit and since, or a company_key for a company's news.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 15,
          "minimum": 1,
          "description": "Default 5, max 15"
        },
        "since": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Stories on or after this day, YYYY-MM-DD"
        },
        "company_key": {
          "type": "string",
          "description": "A company key, e.g. 'apple'"
        },
        "product_slug": {
          "type": "string",
          "description": "A product_slug, e.g. 'apple-watch'"
        }
      },
      "additionalProperties": false
    }
    arguments 25 lines
  • get_compatibility unknown 23h ago

    Whether a product works with a phone or device: Works, Works with limits (features missing, named), Needs extra hardware, Does not work or Not confirmed (unknown, not incompatible), with source.

    mcp-tool

    {
      "type": "object",
      "required": [
        "product_slug"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "What it should work with, e.g. 'iphone'"
        },
        "product_slug": {
          "type": "string",
          "description": "A product_slug, e.g. 'apple-airpods-pro-3'"
        }
      },
      "additionalProperties": false
    }
    arguments 17 lines
  • get_reports unknown 1h ago

    Every well-sourced pre-release report for one product, each with its status (Right, Partly right, Wrong, Not checked yet and the rest), outlet count, first reporter and evidence link.

    mcp-tool

    {
      "type": "object",
      "required": [
        "product_slug"
      ],
      "properties": {
        "category": {
          "type": "string",
          "description": "A report type, e.g. 'design'"
        },
        "product_slug": {
          "type": "string",
          "description": "A product_slug, e.g. 'apple-glasses'"
        }
      },
      "additionalProperties": false
    }
    arguments 17 lines
  • search_reports unknown 25h ago

    Well-sourced pre-release reports by keyword across every covered product, each with its status and the product's lifecycle. Up to 20 per call.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 20,
          "minimum": 1,
          "description": "Default 20, max 20"
        },
        "query": {
          "type": "string",
          "minLength": 2,
          "description": "Keyword or phrase"
        }
      },
      "additionalProperties": false
    }
    arguments 20 lines
  • get_release_history unknown 1h ago

    Every generation of a product's line with announcement and release dates, sources and launch price, and the gaps between releases.

    mcp-tool

    {
      "type": "object",
      "required": [
        "product_slug"
      ],
      "properties": {
        "product_slug": {
          "type": "string",
          "description": "A product_slug, e.g. 'apple-watch'"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • get_detailed_facts unknown 20h ago

    Every individual fact for one product by topic, each with value, unit, who stated it and source. Optional topic; paged with offset and limit.

    mcp-tool

    {
      "type": "object",
      "required": [
        "product_slug"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 20,
          "minimum": 1,
          "description": "Facts per page. Default and maximum 20."
        },
        "topic": {
          "type": "string",
          "description": "A topic, e.g. 'battery'"
        },
        "offset": {
          "type": "integer",
          "minimum": 0,
          "description": "Facts to skip, for the next page"
        },
        "product_slug": {
          "type": "string",
          "description": "A product_slug, e.g. 'apple-watch'"
        }
      },
      "additionalProperties": false
    }
    arguments 28 lines
  • whats_moved unknown never probed

    The week's changes: price moves of 7% or more that held, release windows that changed, and launches, each with its Guide link.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "week": {
          "type": "string",
          "description": "The week's last day, YYYY-MM-DD"
        }
      },
      "additionalProperties": false
    }
    arguments 10 lines
  • get_in_the_box unknown 8h ago

    What ships in the box for one product, per configuration, as the official page states it.

    mcp-tool

    {
      "type": "object",
      "required": [
        "product_slug"
      ],
      "properties": {
        "variant": {
          "type": "string",
          "description": "Part of a configuration name, e.g. 'Pro'"
        },
        "product_slug": {
          "type": "string",
          "description": "A product_slug, e.g. 'apple-watch'"
        }
      },
      "additionalProperties": false
    }
    arguments 17 lines
  • get_price_history unknown 5h ago

    Dated prices for one product: today's verified price (or null with the reason), the lowest recent price with its basis and period, and the price history.

    mcp-tool

    {
      "type": "object",
      "required": [
        "product_slug"
      ],
      "properties": {
        "product_slug": {
          "type": "string",
          "description": "A product_slug, e.g. 'apple-watch'"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • get_product unknown 5h ago

    One product's lifecycle, price, key dates, availability and where to buy.

    mcp-tool

    {
      "type": "object",
      "required": [
        "product_slug"
      ],
      "properties": {
        "product_slug": {
          "type": "string",
          "description": "A product_slug, e.g. 'apple-watch'"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • get_product_facts unknown 5h ago

    One product's price (official, or labelled an estimate), dates, availability and where to buy, a compatibility summary, and specs, each marked Confirmed, Reported, Our read or Not confirmed with its source and date.

    mcp-tool

    {
      "type": "object",
      "required": [
        "product_slug"
      ],
      "properties": {
        "product_slug": {
          "type": "string",
          "description": "A product_slug, e.g. 'apple-watch'"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • find_products unknown 25h ago

    On-sale products in one category, cheapest first, optionally under a price, by company or working with a device, each with its price and date, iDevice's verdict and Guide link. Up to 20 per call.

    mcp-tool

    {
      "type": "object",
      "required": [
        "category"
      ],
      "properties": {
        "company": {
          "type": "string",
          "description": "A company or brand, e.g. 'samsung'"
        },
        "category": {
          "type": "string",
          "description": "glasses, rings, watches, earbuds, phones, headsets or fitness trackers"
        },
        "max_price": {
          "type": "number",
          "description": "Price ceiling in US dollars",
          "exclusiveMinimum": 0
        },
        "works_with": {
          "type": "string",
          "description": "Only products that work with this, e.g. 'iPhone'"
        }
      },
      "additionalProperties": false
    }
    arguments 26 lines
  • get_report_card unknown 1h ago

    One product's pre-release reports rolled up by how they turned out, and the reports, newest first, with reporter, outlet, status and link.

    mcp-tool

    {
      "type": "object",
      "required": [
        "product_slug"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "Words to find, e.g. 'battery'"
        },
        "product_slug": {
          "type": "string",
          "description": "A product_slug, e.g. 'apple-watch'"
        }
      },
      "additionalProperties": false
    }
    arguments 17 lines
  • get_ownership_facts unknown 8h ago

    What owning one product involves, with sources: returns, warranty, any subscription and first-year cost, support status, recalls and update windows.

    mcp-tool

    {
      "type": "object",
      "required": [
        "product_slug"
      ],
      "properties": {
        "section": {
          "enum": [
            "returns",
            "warranty",
            "subscription",
            "support",
            "programs"
          ],
          "type": "string",
          "description": "returns, warranty, subscription, support or programs"
        },
        "product_slug": {
          "type": "string",
          "description": "A product_slug, e.g. 'apple-watch'"
        }
      },
      "additionalProperties": false
    }
    arguments 24 lines
  • get_company_profile unknown 23h ago

    A company as iDevice's directory lists it: name, homepage, description, categories covered and each product with a Guide. Pass a name or key, e.g. 'oura'.

    mcp-tool

    {
      "type": "object",
      "required": [
        "company"
      ],
      "properties": {
        "company": {
          "type": "string",
          "minLength": 2,
          "description": "A company name or key, e.g. 'oura'"
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • is_good_price unknown 29h ago

    For one product: today's verified price against iDevice's daily record of this exact model (low, median, high over 30 and 90 days) and its published Prices verdict.

    mcp-tool

    {
      "type": "object",
      "required": [
        "product_slug"
      ],
      "properties": {
        "product_slug": {
          "type": "string",
          "description": "A product_slug, e.g. 'oura-ring-4'"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • release_odds unknown 25h ago

    For one product not yet released: the expected window, how it is known, who stated it, and the published probability with its sample size where there is one.

    mcp-tool

    {
      "type": "object",
      "required": [
        "product_slug"
      ],
      "properties": {
        "product_slug": {
          "type": "string",
          "description": "A product_slug, e.g. 'apple-glasses'"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • get_guide_extras unknown 12h ago

    A Guide's timeline (events with sources), faq or glossary (one term's definition).

    mcp-tool

    {
      "type": "object",
      "required": [
        "section"
      ],
      "properties": {
        "term": {
          "type": "string",
          "description": "For glossary: the term, e.g. 'field of view'"
        },
        "query": {
          "type": "string",
          "description": "For faq: words to find"
        },
        "section": {
          "enum": [
            "timeline",
            "faq",
            "glossary"
          ],
          "type": "string",
          "description": "timeline, faq or glossary"
        },
        "product_slug": {
          "type": "string",
          "description": "For timeline and faq: a product_slug"
        }
      },
      "additionalProperties": false
    }
    arguments 30 lines
  • source_track_record unknown 23h ago

    For one reporter or outlet: its pre-release reports graded Right, Partly right or Wrong, the share right, and what it reported first.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "maxLength": 80,
          "minLength": 2,
          "description": "A reporter or outlet, e.g. 'Mark Gurman'"
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • get_reviews unknown 29h ago

    Outlets' review scores for one product: the Review Consensus (from two or more publishers), the themes reviewers agree on, and each review with its outlet, rating and link.

    mcp-tool

    {
      "type": "object",
      "required": [
        "product_slug"
      ],
      "properties": {
        "product_slug": {
          "type": "string",
          "description": "A product_slug, e.g. 'apple-watch'"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • get_guide_summary unknown 8h ago

    One product's Guide summary: bottom line, key facts, price, dates, and what bears on buying now or waiting, with iDevice's verdict.

    mcp-tool

    {
      "type": "object",
      "required": [
        "product_slug"
      ],
      "properties": {
        "product_slug": {
          "type": "string",
          "description": "A product_slug, e.g. 'apple-airpods-pro-3'"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • whats_coming unknown 20h ago

    For one product: its stage, the release window and who stated it, and the pre-release reports its Guide lists, each with its status, track record and source.

    mcp-tool

    {
      "type": "object",
      "required": [
        "product_slug"
      ],
      "properties": {
        "product_slug": {
          "type": "string",
          "description": "A product_slug, e.g. 'iphone-pro'"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • compare_products unknown 27h ago

    Side-by-side specs for 2 or 3 products, each cell with its status, source and date. Optional specs keeps matching rows.

    mcp-tool

    {
      "type": "object",
      "required": [
        "product_slugs"
      ],
      "properties": {
        "specs": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 10,
          "description": "Keywords to keep only matching rows"
        },
        "product_slugs": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 3,
          "minItems": 2,
          "description": "e.g. ['oura-ring-4','samsung-galaxy-ring-1']"
        }
      },
      "additionalProperties": false
    }
    arguments 26 lines
  • should_i_buy unknown never probed

    For one product: buy_now, wait, skip, check_fit or not_enough_data, optionally for a shopper's owned device, phone platform, budget or use. With the rule, reasons with sources and status, phone fit, timing, price and what it could not answer; for an owner of the model it replaces, the /upgrade answer. display_label is the answer in the words idevice.com prints. For a line slug whose newest model is not on sale, the answer is for the newest that is, named in resolved_to. With buyer_context, buyer_decision and buyer_decision_info carry the personal answer the idevice.com decision page gives for it.

    mcp-tool

    {
      "type": "object",
      "required": [
        "product_slug"
      ],
      "properties": {
        "use_case": {
          "type": "string",
          "maxLength": 120,
          "description": "What it is for, e.g. 'running'"
        },
        "budget_usd": {
          "type": "number",
          "description": "A price ceiling in US dollars",
          "exclusiveMinimum": 0
        },
        "product_slug": {
          "type": "string",
          "description": "A product_slug, e.g. 'apple-watch'"
        },
        "buyer_context": {
          "description": "Optional. The shopper's own situation in the buyer-context-v1 grammar, set out at https://idevice.com/mcp/docs#buyer-context. A context outside it is answered with buyer_decision_info naming the fields to fix. It is used for this one answer and goes into no log."
        },
        "owned_platform": {
          "enum": [
            "iphone",
            "android",
            "other"
          ],
          "type": "string",
          "description": "The phone platform the shopper uses"
        },
        "owned_device_slug": {
          "type": "string",
          "description": "product_slug of a device the shopper owns"
        }
      },
      "additionalProperties": false
    }
    arguments 39 lines
  • check_deal unknown 29h ago

    Whether a price offered for one product is a GOOD DEAL, NOT A GOOD DEAL or NOT ENOUGH DATA, against today's lowest price and the lowest recent price of this exact model. For a line slug whose newest model is not on sale, the answer is for the newest that is, named in resolved_to.

    mcp-tool

    {
      "type": "object",
      "required": [
        "product_slug",
        "price_usd"
      ],
      "properties": {
        "retailer": {
          "type": "string",
          "maxLength": 60,
          "description": "Where it was offered, e.g. 'Best Buy'"
        },
        "price_usd": {
          "type": "number",
          "maximum": 100000,
          "description": "The price offered, in US dollars",
          "exclusiveMinimum": 0
        },
        "product_slug": {
          "type": "string",
          "description": "A product_slug, e.g. 'oura-ring-4'"
        }
      },
      "additionalProperties": false
    }
    arguments 25 lines
  • pick_between unknown 27h ago

    For two or three products, which one the buy-or-wait rules put ahead, or neither, optionally for a shopper's phone, owned device and budget, each with its verdict, fit, price and reasons; purchase_today and product_for_you split the better purchase from the better product. The same comparison as the decision card on idevice.com. For a line slug whose newest model is not on sale, the answer is for the newest that is, named in resolved_to. With buyer_context, buyer_decision and buyer_decision_info carry the personal answer the idevice.com decision page gives for it.

    mcp-tool

    {
      "type": "object",
      "required": [
        "product_slugs"
      ],
      "properties": {
        "budget_usd": {
          "type": "number",
          "description": "A price ceiling in US dollars",
          "exclusiveMinimum": 0
        },
        "buyer_context": {
          "description": "Optional. The shopper's own situation in the buyer-context-v1 grammar, set out at https://idevice.com/mcp/docs#buyer-context. A context outside it is answered with buyer_decision_info naming the fields to fix. It is used for this one answer and goes into no log."
        },
        "product_slugs": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 3,
          "minItems": 2,
          "description": "Two or three product_slugs"
        },
        "owned_platform": {
          "enum": [
            "iphone",
            "android",
            "other"
          ],
          "type": "string",
          "description": "The phone platform the shopper uses"
        },
        "owned_device_slug": {
          "type": "string",
          "description": "product_slug of a device the shopper owns"
        }
      },
      "additionalProperties": false
    }
    arguments 39 lines
  • find_best_device unknown 27h ago

    A short ranked list of on-sale products in one category, optionally for a phone platform, budget and up to three uses the Guides assign, each with its verdict, phone fit, price, a reason with sources and its Guide's place for the use. In every category iDevice's own pick covers, that pick answers first, then the alternatives it names, each with its verdict, fit, price and sources, and a best_answer block with the reviews behind the pick. The phone and budget decide which products fit, not which is better; priorities are the uses the pick covers.

    mcp-tool

    {
      "type": "object",
      "required": [
        "category"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 5,
          "minimum": 1,
          "description": "1 to 5, default 3"
        },
        "category": {
          "enum": [
            "glasses",
            "rings",
            "watches",
            "earbuds",
            "phones",
            "headsets",
            "fitness trackers",
            "headphones"
          ],
          "type": "string",
          "description": "The kind of product"
        },
        "budget_usd": {
          "type": "number",
          "description": "A price ceiling in US dollars",
          "exclusiveMinimum": 0
        },
        "priorities": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 40
          },
          "maxItems": 3,
          "description": "Up to three uses, e.g. ['sleep','battery-life']"
        },
        "owned_platform": {
          "enum": [
            "iphone",
            "android",
            "other"
          ],
          "type": "string",
          "description": "The phone platform the shopper uses"
        }
      },
      "additionalProperties": false
    }
    arguments 52 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id ede7590612532c0b.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/ede7590612532c0b/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/ede7590612532c0b/badge.svg)](https://brick.blue/agent/ede7590612532c0b?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.