Remote MCP · Endpoint

MyBestSim eSIM comparator MCP server

No. MyBestSim eSIM comparator answered an MCP handshake 35 minutes ago.

UpLast checked 35 minutes ago

Server URL

https://mcp.mybestsim.com/mcp

The last check completed an MCP handshake.

Registry name
com.mybestsim/esim-comparator
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
349 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Compare prepaid travel eSIM plans by destination, data and trip length; plan multi-country trips.
Listing
From the official MCP registry (active).
Recent checks of MyBestSim eSIM comparator
CheckedResultHandshake
35 minutes agoHandshake completed349 ms
9 days agoHandshake completed483 ms
10 days agoHandshake completed181 ms
11 days agoHandshake completed295 ms
12 days agoHandshake completed542 ms
14 days agoHandshake completed405 ms
14 days agoHandshake completed410 ms
15 days agoHandshake completed353 ms
17 days agoHandshake completed446 ms
19 days agoHandshake completed71 ms
21 days agoHandshake completed284 ms
24 days agoHandshake completed629 ms
26 days agoHandshake completed412 ms
28 days agoHandshake completed265 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

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 MyBestSim eSIM comparator and makes no claim about it beyond what these checks measured.