Remote MCP · Endpoint
Esoru by resortlife.travel MCP server
No. Esoru by resortlife.travel answered an MCP handshake 57 minutes ago.
UpLast checked 57 minutes ago
Server URL
https://resortlife.travel/api/mcp
The last check completed an MCP handshake.
- Registry name
- travel.resortlife/esoru
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 397 ms
- Tools exposed
- 21 tools
- Uptime, last 30 days
- 100% from 12 checks
- Described by its publisher as
- Read-only Maldives resort research, comparisons and media for approved travel agencies.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 57 minutes ago | Handshake completed | 397 ms |
| 3 days ago | Handshake completed | 709 ms |
| 12 days ago | Handshake completed | 464 ms |
| 13 days ago | Handshake completed | 508 ms |
| 15 days ago | Handshake completed | 460 ms |
| 15 days ago | Handshake completed | 680 ms |
| 17 days ago | Credentials required | — |
| 18 days ago | Credentials required | — |
| 18 days ago | Credentials required | — |
| 20 days ago | Credentials required | — |
| 22 days ago | Credentials required | — |
| 25 days ago | Credentials required | — |
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 Esoru by resortlife.travel and makes no claim about it beyond what these checks measured.