Hungry eSIM
warningsapi.hungry-esim.com
Travel eSIMs: unlimited data, pick your days, top up existing eSIMs, card checkout, no API key.
https://api.hungry-esim.com/mcpWebsiteOAuthMCP 2025-11-25v1.1.0last checked 24 Aug 2026spoke MCP on 3 of 3 checks (30 days)initialize in 935 msHow to authenticate
Checked against the endpoint by our probe on 24 Aug 2026. These are the capabilities the server advertises, not a prediction about any particular client.
| Scheme | OAuth |
|---|---|
| Issuer | https://api.hungry-esim.com |
| Dynamic client registration | ✓Advertised (RFC 7591) |
| Client ID Metadata Document | ✕Not advertised |
| PKCE | ✓S256 |
| Grant types | authorization_code, refresh_token |
| Scopes | esim:read, esim:write, order:read, offline_access |
| Protected-resource metadata | ✓Published (RFC 9728) |
| Anonymous access | Handshake succeeds; 10 tools listable |
| Credentials demanded in prose | ✕create_checkout, my_esims These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error. |
| Documentation | https://hungry-esim.com/for-agents |
What the probe found
2 of the 10 tools listed anonymously say in their own descriptions that they need an account or a key (create_checkout, my_esims), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.
A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.
The server exposes a public surface before authorization: search_esim_plans, get_plan_details, create_checkout, get_order_status, my_esims, list_esim_topups, topup_esim, my_orders, check_destination_coverage, find_cheapest_plan.
Tools
Contract history
Get alerted when this contract changes
Depend on this server? Leave an email and get a message when a probe records a change — a tool removed, an argument newly required, an enum narrowed. Alerts are being built; signing up is what tells us to hurry.
Prefer a feed reader? This page's contract changes are also an Atom feed.
Status badge
Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.
[](https://mcpi.app/servers/hungry-esim)Own this server?
Sign in to claim this listing by proving control of the endpoint.