Remote MCP · Endpoint
GdzieZabawa.pl MCP server
No. GdzieZabawa.pl answered an MCP handshake 39 minutes ago.
UpLast checked 39 minutes ago
Server URL
https://gdziezabawa.pl/mcp
The last check completed an MCP handshake.
- Registry name
- pl.gdziezabawa/imprezy
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 349 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 12 checks
- Described by its publisher as
- Local events and things to do in every Polish municipality: festivals, fairs, kids' events.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 39 minutes ago | Handshake completed | 349 ms |
| 3 days ago | Handshake completed | 373 ms |
| 13 days ago | Handshake completed | 364 ms |
| 13 days ago | Handshake completed | 384 ms |
| 15 days ago | Handshake completed | 350 ms |
| 16 days ago | Handshake completed | 393 ms |
| 17 days ago | Handshake completed | 367 ms |
| 18 days ago | Handshake completed | 360 ms |
| 18 days ago | Handshake completed | 392 ms |
| 20 days ago | Handshake completed | 362 ms |
| 22 days ago | Handshake completed | 491 ms |
| 25 days ago | Handshake completed | 362 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 GdzieZabawa.pl and makes no claim about it beyond what these checks measured.