Remote MCP · Endpoint
週末不賣甜點 Weekend no dessert MCP server
Yes, as of 1 hour ago: the check failed for an unclassified reason.
DownLast checked 1 hour ago
Server URL
https://weekendnodessert.com/api/mcp
The last check failed: the check failed for an unclassified reason.
- Registry name
- com.weekendnodessert/order
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 7 tools
- Uptime, last 30 days
- 3 checks from 3 checks
- Described by its publisher as
- 台北預訂制茶香戚風蛋糕：查本月蛋糕與價格、可訂日期與取貨時段、產訂購連結，或在使用者確認後代為送出訂購申請（中山站自取、匯款後成立）。
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Failed - the check failed for an unclassified reason | — |
| 1 day ago | Failed - the check failed for an unclassified reason | — |
| 2 days ago | Handshake completed | 121 ms |
The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 1 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 週末不賣甜點 Weekend no dessert and makes no claim about it beyond what these checks measured.