Remote MCP · Endpoint
tickadoo Experiences and Events MCP server
No. tickadoo Experiences and Events answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.tickadoo.com/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.tickadoo/tickadoo-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 209 ms
- Tools exposed
- 27 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Discover and book theatre, tours, attractions, and live experiences worldwide. No API key required.
- Website
- https://mcp.tickadoo.com/
- Repository
- https://github.com/tickadoo/tickadoo-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 209 ms |
| 1 day ago | Handshake completed | 283 ms |
| 2 days ago | Handshake completed | 407 ms |
| 3 days ago | Handshake completed | 728 ms |
| 4 days ago | Handshake completed | 273 ms |
| 5 days ago | Handshake completed | 185 ms |
| 6 days ago | Handshake completed | 211 ms |
| 9 days ago | Handshake completed | 330 ms |
| 11 days ago | Handshake completed | 251 ms |
| 14 days ago | Handshake completed | 129 ms |
| 16 days ago | Handshake completed | 178 ms |
| 18 days ago | Handshake completed | 119 ms |
| 20 days ago | Handshake completed | 210 ms |
| 22 days ago | Handshake completed | 137 ms |
| 24 days ago | Handshake completed | 128 ms |
| 26 days ago | Handshake completed | 603 ms |
| 27 days ago | Handshake completed | 125 ms |
| 29 days ago | Handshake completed | 121 ms |
The last 18 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 tickadoo Experiences and Events and makes no claim about it beyond what these checks measured.