Remote MCP · Endpoint

AI 代理人任務中樞 MCP server

No. AI 代理人任務中樞 answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://hub.penguindriver.com/mcp

The last check completed an MCP handshake.

Registry name
com.penguindriver/hub
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
269 ms
Tools exposed
174 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
一個入口整合全部台灣繁中 MCP 工具：生活、旅遊、台股、AI 工具、遊戲、電影、運動等
Website
https://hub.penguindriver.com/
Listing
From the official MCP registry (active).
Recent checks of AI 代理人任務中樞
CheckedResultHandshake
7 hours agoHandshake completed269 ms
2 days agoHandshake completed123 ms
4 days agoHandshake completed78 ms
6 days agoHandshake completed69 ms
8 days agoHandshake completed81 ms
10 days agoHandshake completed87 ms
12 days agoHandshake completed76 ms
13 days agoHandshake completed102 ms
14 days agoHandshake completed108 ms
15 days agoHandshake completed76 ms
18 days agoHandshake completed98 ms
20 days agoHandshake completed49 ms
21 days agoHandshake completed355 ms
23 days agoHandshake completed54 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with AI 代理人任務中樞 and makes no claim about it beyond what these checks measured.