Remote MCP · Endpoint
io.github.kewelin/ecpro-mcp MCP server
No. io.github.kewelin/ecpro-mcp answered an MCP handshake 49 minutes ago.
UpLast checked 49 minutes ago
Server URL
https://ecpro.tw/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.kewelin/ecpro-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 199 ms
- Tools exposed
- 17 tools
- Uptime, last 30 days
- 4 checks from 4 checks
- Described by its publisher as
- 台灣電商情報與商品比價：跨通路查 momo、PChome、品牌官網即時價格與歷史最低價、偵測網站電商技術、搜尋電商知識庫。資料來源 ecpro.tw。
- Website
- https://ecpro.tw/price/
- Repository
- https://github.com/kewelin/ecpro-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 49 minutes ago | Handshake completed | 199 ms |
| 1 hour ago | Handshake completed | 216 ms |
| 1 day ago | Handshake completed | 201 ms |
| 2 days ago | Handshake completed | 266 ms |
The last 4 checks. Full history is kept for 30 days; the all-time counter stands at 4 responding of 4.
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 io.github.kewelin/ecpro-mcp and makes no claim about it beyond what these checks measured.