Remote MCP · Endpoint

數位健康與遠距醫療指南 MCP server

No. 數位健康與遠距醫療指南 answered an MCP handshake 8 hours ago.

UpLast checked 8 hours ago

Server URL

https://wellness.penguindriver.com/mcp

The last check completed an MCP handshake.

Registry name
com.penguindriver/wellness
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
562 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
數位健康與遠距醫療指南:視訊看診、心情自評與睡眠放鬆。台灣繁體中文 MCP 工具。
Listing
From the official MCP registry (active).
Recent checks of 數位健康與遠距醫療指南
CheckedResultHandshake
8 hours agoHandshake completed562 ms
10 days agoHandshake completed68 ms
11 days agoHandshake completed114 ms
11 days agoHandshake completed83 ms
13 days agoHandshake completed65 ms
15 days agoHandshake completed81 ms
15 days agoHandshake completed65 ms
16 days agoHandshake completed278 ms
17 days agoHandshake completed60 ms
19 days agoHandshake completed327 ms
22 days agoHandshake completed82 ms
24 days agoHandshake completed62 ms
26 days agoHandshake completed91 ms
29 days agoHandshake completed66 ms

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

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 數位健康與遠距醫療指南 and makes no claim about it beyond what these checks measured.