Remote MCP · Endpoint
io.github.pratikgajjar/sf-beverage-skus MCP server
Yes, as of 46 minutes ago: the server returned an HTTP error.
DownLast checked 46 minutes ago
Server URL
https://sf-beverage-skus.luff.workers.dev/mcp
The last check failed: the server returned an HTTP error.
- Registry name
- io.github.pratikgajjar/sf-beverage-skus
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 92.3% from 13 checks
- Described by its publisher as
- SF coffee, matcha, and chai catalog API: 439 SKUs across 13 merchants, prices in cents.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 46 minutes ago | Failed - the server returned an HTTP error | — |
| 3 days ago | Handshake completed | 124 ms |
| 13 days ago | Handshake completed | 259 ms |
| 13 days ago | Handshake completed | 191 ms |
| 15 days ago | Handshake completed | 125 ms |
| 16 days ago | Handshake completed | 126 ms |
| 17 days ago | Handshake completed | 116 ms |
| 18 days ago | Handshake completed | 143 ms |
| 18 days ago | Handshake completed | 174 ms |
| 20 days ago | Handshake completed | 202 ms |
| 22 days ago | Handshake completed | 187 ms |
| 25 days ago | Handshake completed | 162 ms |
| 27 days ago | Handshake completed | 143 ms |
| 30 days ago | Handshake completed | 128 ms |
The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 23 responding of 24.
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.pratikgajjar/sf-beverage-skus and makes no claim about it beyond what these checks measured.