Remote MCP · Endpoint
pl.biletyna/events-search MCP server
No. pl.biletyna/events-search answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://biletyna.pl/mcp
The last check completed an MCP handshake.
- Registry name
- pl.biletyna/events-search
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-11-25
- Handshake latency
- 586 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Event search at Biletyna.pl - Poland's top-rated ticket distributor, widest offer in all cities.
- Website
- https://biletyna.pl/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 586 ms |
| 1 day ago | Handshake completed | 526 ms |
| 2 days ago | Handshake completed | 547 ms |
| 3 days ago | Handshake completed | 592 ms |
| 4 days ago | Handshake completed | 432 ms |
| 5 days ago | Handshake completed | 563 ms |
| 6 days ago | Handshake completed | 503 ms |
| 8 days ago | Handshake completed | 596 ms |
| 11 days ago | Handshake completed | 430 ms |
| 13 days ago | Handshake completed | 622 ms |
| 15 days ago | Handshake completed | 559 ms |
| 18 days ago | Handshake completed | 505 ms |
| 20 days ago | Handshake completed | 721 ms |
| 22 days ago | Handshake completed | 655 ms |
| 24 days ago | Handshake completed | 557 ms |
| 26 days ago | Handshake completed | 638 ms |
| 27 days ago | Handshake completed | 674 ms |
| 29 days ago | Handshake completed | 672 ms |
| 29 days ago | Handshake completed | 650 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 pl.biletyna/events-search and makes no claim about it beyond what these checks measured.