Home / MCP registry index / com.idevice/wearables
iDevice Buyer's Guide
com.idevice/wearables in the official MCP registry.
Endpoint https://idevice.com/api/mcp. Source: github.com/idevicewearables/idevice-agent-examples.
The registry describes it as: Independent buyer's guide for wearables and phones: buy now or wait, compatibility, prices. Sourced.
We read its 27 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
should_i_buy check_deal pick_between find_best_device whats_coming get_product_news 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 get_ownership_facts get_best_for get_variants_and_offers get_company_profile get_guide_extras
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-idevice-wearables)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.