Remote MCP · Endpoint
Супермаркет САМПО MCP server
No. Супермаркет САМПО answered an MCP handshake 38 minutes ago.
UpLast checked 38 minutes ago
Server URL
https://sampo.shop/mcp
The last check completed an MCP handshake.
- Registry name
- shop.sampo/catalog
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-03-26
- Handshake latency
- 595 ms
- Tools exposed
- 9 tools
- Uptime, last 30 days
- 100% from 13 checks
- Described by its publisher as
- Каталог и заказ супермаркета САМПО. Оплата на странице банка.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 38 minutes ago | Handshake completed | 595 ms |
| 3 days ago | Handshake completed | 689 ms |
| 13 days ago | Handshake completed | 544 ms |
| 13 days ago | Handshake completed | 720 ms |
| 15 days ago | Handshake completed | 627 ms |
| 16 days ago | Handshake completed | 581 ms |
| 17 days ago | Handshake completed | 561 ms |
| 18 days ago | Handshake completed | 807 ms |
| 18 days ago | Handshake completed | 929 ms |
| 20 days ago | Handshake completed | 506 ms |
| 22 days ago | Handshake completed | 2.77 s |
| 25 days ago | Handshake completed | 626 ms |
| 27 days ago | Handshake completed | 644 ms |
The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.
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 Супермаркет САМПО and makes no claim about it beyond what these checks measured.