Remote MCP · Endpoint
haalaan China eSIM MCP server
No. haalaan China eSIM answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.haalaan.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.haalaan/travel-esim
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 511 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 12 checks
- Described by its publisher as
- Browse haalaan China, Hong Kong, Macau and Greater China eSIM plans in USD. Get a checkout link.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 511 ms |
| 3 days ago | Handshake completed | 596 ms |
| 13 days ago | Handshake completed | 728 ms |
| 14 days ago | Handshake completed | 565 ms |
| 15 days ago | Handshake completed | 578 ms |
| 16 days ago | Handshake completed | 473 ms |
| 18 days ago | Handshake completed | 554 ms |
| 18 days ago | Handshake completed | 555 ms |
| 19 days ago | Handshake completed | 550 ms |
| 21 days ago | Handshake completed | 637 ms |
| 22 days ago | Handshake completed | 759 ms |
| 25 days ago | Handshake completed | 676 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 haalaan China eSIM and makes no claim about it beyond what these checks measured.