Remote MCP · Endpoint
Beaches of Mallorca MCP server
No. Beaches of Mallorca answered an MCP handshake 7 hours ago.
UpLast checked 7 hours ago
Server URL
https://beachesofmallorca.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.beachesofmallorca/beaches
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 149 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 12 checks
- Described by its publisher as
- Live swimming and family conditions and reviewed guides for 77 Mallorca beaches
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 7 hours ago | Handshake completed | 149 ms |
| 4 days ago | Handshake completed | 815 ms |
| 14 days ago | Handshake completed | 121 ms |
| 15 days ago | Handshake completed | 131 ms |
| 15 days ago | Handshake completed | 117 ms |
| 17 days ago | Handshake completed | 155 ms |
| 18 days ago | Handshake completed | 275 ms |
| 19 days ago | Handshake completed | 129 ms |
| 20 days ago | Handshake completed | 122 ms |
| 21 days ago | Handshake completed | 104 ms |
| 23 days ago | Handshake completed | 152 ms |
| 26 days ago | Handshake completed | 210 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 Beaches of Mallorca and makes no claim about it beyond what these checks measured.