Remote MCP · Endpoint

eSIM SOS MCP server

No. eSIM SOS answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://esimsos.net/api/mcp

The last check completed an MCP handshake.

Registry name
net.esimsos/esimsos
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
290 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Find travel eSIM plans, compare prices and create an order the user pays by link.
Listing
From the official MCP registry (active).
Recent checks of eSIM SOS
CheckedResultHandshake
1 hour agoHandshake completed290 ms
1 day agoHandshake completed287 ms
2 days agoHandshake completed294 ms
3 days agoHandshake completed426 ms
3 days agoHandshake completed290 ms
5 days agoHandshake completed296 ms
7 days agoHandshake completed298 ms
10 days agoHandshake completed302 ms
12 days agoHandshake completed297 ms
14 days agoHandshake completed291 ms
17 days agoHandshake completed297 ms
19 days agoHandshake completed291 ms
21 days agoHandshake completed287 ms
23 days agoHandshake completed287 ms
24 days agoHandshake completed303 ms

The last 15 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 eSIM SOS and makes no claim about it beyond what these checks measured.