Remote MCP · Endpoint
Дизайн-афиша MCP server
No. Дизайн-афиша answered an MCP handshake 20 minutes ago.
UpLast checked 20 minutes ago
Server URL
https://design-events.fun/mcp
The last check completed an MCP handshake.
- Registry name
- fun.design-events/afisha
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 666 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 12 checks
- Described by its publisher as
- Афиша для дизайнеров: лекции, митапы, выставки. Поиск по городу, датам, теме, только чтение.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 20 minutes ago | Handshake completed | 666 ms |
| 3 days ago | Handshake completed | 596 ms |
| 14 days ago | Handshake completed | 602 ms |
| 14 days ago | Handshake completed | 682 ms |
| 15 days ago | Handshake completed | 711 ms |
| 16 days ago | Handshake completed | 595 ms |
| 18 days ago | Handshake completed | 654 ms |
| 18 days ago | Credentials required | — |
| 19 days ago | Handshake completed | 597 ms |
| 21 days ago | Handshake completed | 719 ms |
| 22 days ago | Handshake completed | 580 ms |
| 25 days ago | Handshake completed | 660 ms |
The last 12 checks. Full history is kept for 30 days; the all-time counter stands at 12 responding of 12.
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.