Remote MCP · Endpoint

iDevice Buyer's Guide MCP server

No. iDevice Buyer's Guide answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://idevice.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.idevice/wearables
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
149 ms
Tools exposed
27 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Independent buyer's guide for wearables and phones: buy now or wait, compatibility, prices. Sourced.
Listing
From the official MCP registry (active).
Recent checks of iDevice Buyer's Guide
CheckedResultHandshake
1 hour agoHandshake completed149 ms
2 days agoHandshake completed290 ms
5 days agoHandshake completed308 ms
7 days agoHandshake completed86 ms
9 days agoHandshake completed123 ms
11 days agoHandshake completed1.19 s
13 days agoHandshake completed1.82 s
15 days agoHandshake completed110 ms
16 days agoHandshake completed95 ms
18 days agoHandshake completed74 ms
19 days agoHandshake completed476 ms
20 days agoHandshake completed96 ms
23 days agoHandshake completed57 ms
24 days agoHandshake completed252 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with iDevice Buyer's Guide and makes no claim about it beyond what these checks measured.