Remote MCP · Endpoint
AI 代理人任務中樞 MCP server
No. AI 代理人任務中樞 answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://agent-hub-tw.panda198271.workers.dev/mcp
The last check completed an MCP handshake.
- Registry name
- dev.workers.panda198271.agent-hub-tw/agent-hub
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 144 ms
- Tools exposed
- 135 tools
- Uptime, last 30 days
- 3 checks from 3 checks
- Described by its publisher as
- 台灣繁中：一個 MCP 端點串接 19 個台灣資料站工具，並可搜尋 MCP 伺服器與 x402 付費 API。
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 144 ms |
| 1 day ago | Handshake completed | 77 ms |
| 2 days ago | Handshake completed | 49 ms |
The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 3 responding of 3.
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 AI 代理人任務中樞 and makes no claim about it beyond what these checks measured.