Remote MCP · Endpoint
Bloomy eSIM MCP server
No. Bloomy eSIM answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://bloomyesim.com/wp-json/bloomy/v1/mcp
The last check completed an MCP handshake.
- Registry name
- com.bloomyesim/esim
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 599 ms
- Tools exposed
- 7 tools
- Uptime, last 30 days
- 100% from 16 checks
- Described by its publisher as
- Recommend the right travel eSIM for any trip (200+ countries) and hand the traveler a checkout link.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 599 ms |
| 2 days ago | Handshake completed | 568 ms |
| 4 days ago | Handshake completed | 599 ms |
| 6 days ago | Handshake completed | 573 ms |
| 7 days ago | Handshake completed | 591 ms |
| 9 days ago | Handshake completed | 632 ms |
| 10 days ago | Handshake completed | 829 ms |
| 11 days ago | Handshake completed | 610 ms |
| 14 days ago | Handshake completed | 595 ms |
| 15 days ago | Handshake completed | 579 ms |
| 17 days ago | Handshake completed | 2.37 s |
| 19 days ago | Handshake completed | 562 ms |
| 20 days ago | Handshake completed | 611 ms |
| 21 days ago | Handshake completed | 601 ms |
| 22 days ago | Handshake completed | 598 ms |
| 22 days ago | Handshake completed | 592 ms |
The last 16 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 16.
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 Bloomy eSIM and makes no claim about it beyond what these checks measured.