Remote MCP · Endpoint
pl.biletyna/events-search MCP server
No. pl.biletyna/events-search answered an MCP handshake 55 minutes ago.
UpLast checked 55 minutes 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
- 721 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 17 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 |
|---|---|---|
| 55 minutes ago | Handshake completed | 721 ms |
| 2 days ago | Handshake completed | 655 ms |
| 4 days ago | Handshake completed | 557 ms |
| 5 days ago | Handshake completed | 638 ms |
| 7 days ago | Handshake completed | 674 ms |
| 8 days ago | Handshake completed | 672 ms |
| 9 days ago | Handshake completed | 650 ms |
| 12 days ago | Handshake completed | 680 ms |
| 13 days ago | Handshake completed | 718 ms |
| 15 days ago | Handshake completed | 539 ms |
| 17 days ago | Handshake completed | 660 ms |
| 18 days ago | Handshake completed | 567 ms |
| 19 days ago | Handshake completed | 563 ms |
| 20 days ago | Handshake completed | 554 ms |
| 21 days ago | Handshake completed | 612 ms |
| 21 days ago | Handshake completed | 593 ms |
| 23 days ago | Handshake completed | 590 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.
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.