Remote MCP · Endpoint

iPadian MCP server

No. iPadian answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://os.ipadian.net/mcp

The last check completed an MCP handshake.

Registry name
net.ipadian.os/ipadian
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
270 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Create and preview self-contained web apps in iPhone, Duo, iPad, and Headless views.
Listing
From the official MCP registry (active).
Recent checks of iPadian
CheckedResultHandshake
2 hours agoHandshake completed270 ms
1 day agoHandshake completed269 ms
2 days agoHandshake completed252 ms
3 days agoHandshake completed272 ms
4 days agoHandshake completed258 ms
5 days agoHandshake completed278 ms
7 days agoHandshake completed297 ms
10 days agoHandshake completed314 ms
12 days agoHandshake completed269 ms
14 days agoHandshake completed265 ms
17 days agoHandshake completed269 ms
19 days agoHandshake completed322 ms
21 days agoHandshake completed268 ms
23 days agoHandshake completed338 ms
25 days agoHandshake completed262 ms

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

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 iPadian and makes no claim about it beyond what these checks measured.