Remote MCP · Endpoint

Hungry eSIM MCP server

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

UpLast checked 1 hour ago

Server URL

https://api.hungry-esim.com/mcp

The last check completed an MCP handshake.

Registry name
com.hungry-esim/esim
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
360 ms
Tools exposed
10 tools
Uptime, last 30 days
94.7% from 19 checks
Described by its publisher as
Travel eSIMs: unlimited data, pick your days, top up existing eSIMs, card checkout, no API key.
Website
https://hungry-esim.com/for-agents
Repository
https://github.com/kangih90/hungry-esim-mcp
Listing
From the official MCP registry (active).
Recent checks of Hungry eSIM
CheckedResultHandshake
1 hour agoHandshake completed360 ms
18 hours agoHandshake completed303 ms
2 days agoHandshake completed298 ms
3 days agoHandshake completed338 ms
4 days agoHandshake completed321 ms
5 days agoHandshake completed329 ms
6 days agoHandshake completed325 ms
7 days agoHandshake completed400 ms
10 days agoHandshake completed334 ms
13 days agoHandshake completed149 ms
15 days agoHandshake completed329 ms
17 days agoHandshake completed313 ms
19 days agoHandshake completed308 ms
21 days agoHandshake completed296 ms
23 days agoFailed - the request timed out—
25 days agoHandshake completed297 ms
27 days agoHandshake completed380 ms
28 days agoHandshake completed355 ms
29 days agoHandshake completed885 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Hungry eSIM and makes no claim about it beyond what these checks measured.