Remote MCP · Endpoint

esimoa — travel eSIM comparison MCP server

No. esimoa — travel eSIM comparison answered an MCP handshake 40 minutes ago.

UpLast checked 40 minutes ago

Server URL

https://api.esimoa.com/mcp

The last check completed an MCP handshake.

Registry name
com.esimoa/esim
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
683 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Compare travel eSIM plans by country, days and data — live prices and links to buy on esimoa.
Listing
From the official MCP registry (active).
Recent checks of esimoa — travel eSIM comparison
CheckedResultHandshake
40 minutes agoHandshake completed683 ms
3 days agoHandshake completed780 ms
13 days agoHandshake completed636 ms
13 days agoHandshake completed573 ms
15 days agoHandshake completed729 ms
16 days agoHandshake completed795 ms
17 days agoHandshake completed569 ms
18 days agoHandshake completed568 ms
18 days agoHandshake completed777 ms
20 days agoHandshake completed566 ms
22 days agoHandshake completed598 ms
25 days agoHandshake completed564 ms
27 days agoHandshake completed572 ms

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

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 esimoa — travel eSIM comparison and makes no claim about it beyond what these checks measured.