Hungry eSIM
REMOTE · API.HUNGRY-ESIM.COM
Travel eSIMs: unlimited data, pick your days, top up existing eSIMs, card checkout, no API key.
Available components
Last scanned (2 hours ago)
Scores higher than 96% of remote servers
Reachable. Last reached 17 Oct 2026.
Category E-commerce
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1667 tokens (~166/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Oct 26 +1
- “create_checkout” reworded the description of “period_num” cosmetic
- “search_esim_plans” reworded the description of “days” cosmetic
2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 28 Sept 26 +6
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Aug 26 0
- Tool “search_esim_plans” rewrote its description, which is the text the model reads security
- “search_esim_plans” added an optional parameter “days” cosmetic
- 21 Aug 26 0
- Tool “search_esim_plans” rewrote its description, which is the text the model reads security
- 19 Aug 26 0
- Tool “create_checkout” rewrote its description, which is the text the model reads security
- Tool “get_order_status” rewrote its description, which is the text the model reads security
- Tool “get_plan_details” rewrote its description, which is the text the model reads security
- Tool “list_esim_topups” rewrote its description, which is the text the model reads security
- Tool “my_esims” rewrote its description, which is the text the model reads security
- Tool “my_orders” rewrote its description, which is the text the model reads security
- Tool “search_esim_plans” rewrote its description, which is the text the model reads security
- Tool “topup_esim” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “check_destination_coverage” functional
- New tool “find_cheapest_plan” functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Probed https://api.hungry-esim.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hungry-esim.com | CN=YE1,O=Let's Encrypt,C=US | 1 Sept 2026 | 30 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 65685028233f717fe87ecdba8e313b4a10b |
| SANs: *.hungry-esim.com, hungry-esim.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.hungry-esim.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| hungry-esim.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.hungry-esim.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.hungry-esim.com/mcp | HTTPS enforced | 308 | https://api.hungry-esim.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_destination_coverage Check destination coverage ~130
Check whether we cover a destination before choosing a plan — answers "do you work in X?", "can I get mobile data / a SIM card in X?", "is X supported?". Returns yes/no, how many plans cover it, and the cheapest unlimited and fixed-data plan as examples. Use search_esim_plans or find_cheapest_plan for the full list.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO 3166-1 alpha-2 country code of the destination, e.g. 'JP', 'US' |
| currency | string | – | ISO currency for prices, default the store currency |
No output schema declared.
No examples provided.
create_checkout Create eSIM checkout link ~256
Buy the chosen eSIM data plan: builds a cart and returns a checkout URL the traveller opens to pay by credit card on hungry-esim.com — no crypto wallet and no API key needed. Use once a plan is picked. Does NOT charge — the user completes payment on the website. For unlimited plans, period_num (how many days of data the traveller wants) is required. If the customer is signed in, the order is linked to their account automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Number of eSIMs, default 1 |
| country | string | yes | Customer's CHECKOUT country (ISO alpha-2) — sets checkout region/currency and URL locale. NOT the eSIM's coverage country. If the store doesn't serve it, the store's default region is used. |
| string | – | Guest email — prefills checkout so it skips the details step. Ignored when the customer is signed in (their account email is used). Never determines which account the order belongs to. | |
| period_num | integer | – | Days for unlimited plans (1-90; each plan states its own maximum). Required for unlimited, ignored otherwise. |
| variant_id | string | yes | Variant id from search_esim_plans |
No output schema declared.
No examples provided.
find_cheapest_plan Find the cheapest eSIM plan ~223
Find the lowest-priced eSIM data plan for a destination — for "what's the cheapest", "budget option", "cheapest SIM / data plan for X". Pass days (trip length) to rank by what the traveller actually pays for the whole trip: unlimited plans are priced per day with a multi-day discount, fixed-data plans by their sticker price, and plans that expire before the trip ends are dropped. Without days it ranks by daily rate. Returns up to 3 options with variant_id for create_checkout.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO 3166-1 alpha-2 country code of the destination, e.g. 'JP', 'US' |
| currency | string | – | ISO currency for prices, default the store currency |
| days | integer | – | Trip length in days. When given, plans are ranked by total trip cost. |
| limit | integer | – | How many options to return, default 3 |
| min_data_gb | number | – | Minimum data in GB (applies to fixed-data plans; unlimited always qualifies) |
No output schema declared.
No examples provided.
get_order_status Get eSIM order status ~177
Look up an eSIM order and return its status plus the SIM install details: install link, LPA activation code, QR image URL, and ICCID. Use for "where is my eSIM", "resend my QR code", or "did my order go through" when an order number is known. Signed-in customers can look up their own orders by number without an email. Otherwise, a short order number MUST be paired with the email used for the order — the eSIM install details are only returned to the buyer.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Email used for the order. Required when 'order' is a short order number and the customer is not signed in. | |
| order | string | yes | Order number (e.g. '32') or Medusa order id (order_01K...) from the confirmation email |
No output schema declared.
No examples provided.
get_plan_details Get eSIM plan details ~95
Get everything about one eSIM data plan: which countries the SIM roams in, data volume, validity in days, speed and fair-use throttling, and price. Use after search_esim_plans or find_cheapest_plan when the traveller asks what exactly a plan includes before buying.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | ISO currency, default USD |
| variant_id | string | yes | Variant id from search_esim_plans |
No output schema declared.
No examples provided.
list_esim_topups List eSIM top-up options ~112
List the data top-up (recharge / refill) packages that can be added to an eSIM the customer already owns. Use when the traveller ran out of mobile data or wants more days on a SIM they already bought — topping up reuses the installed SIM, so no new QR code is needed. Pass the ICCID from my_esims. Returns package_code values to pass to topup_esim.
| Name | Type | Req | Description |
|---|---|---|---|
| iccid | string | yes | ICCID of the eSIM, from my_esims |
No output schema declared.
No examples provided.
my_esims My eSIMs ~89
List the SIM cards (eSIMs) already on the signed-in Hungry eSIM account: ICCID, status, data package, expiry, and install link. Use for "my eSIM", "my SIM card", "how much data do I have left", or before topping up a SIM the traveller already owns. Requires connecting the Hungry eSIM account (OAuth) — no API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
my_orders My orders ~63
List the signed-in customer's recent eSIM purchases with payment and provisioning status. Use for "what did I buy" or "did my order go through" when no order number is at hand. For the install QR and activation code of one order, use get_order_status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_esim_plans Search eSIM plans ~350
Search prepaid travel eSIM data plans for a destination — the SIM card / mobile data / roaming option for a trip. Use this first for any "data plan for my trip to X" request. Includes unlimited plans where the traveller picks the number of days, and fixed-data plans. Filter by unlimited vs fixed-data, minimum data, and validity. Unlimited plans are quoted per day, fixed-data plans as a one-off total — never compare those two numbers directly. The unlimited total is the per-day price × days, with a volume discount from 7 days, so pass days (trip length) to get that total quoted alongside the daily rate. Price differences between similar plans come from the routing IP country (routing_ip_country) and the supported networks (speed) — quote both when comparing plans. Results are grouped: fixed-data plans first, then unlimited; each group sorted by price. Returns variant_id values to pass to create_checkout.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO 3166-1 alpha-2 country code, e.g. 'JP', 'US' |
| currency | string | – | ISO currency for prices, default USD |
| days | integer | – | Trip length in days (1-90; each unlimited plan states its own maximum). When given, unlimited plans also quote the total for that many days. |
| limit | integer | – | Max results, default 10 |
| max_validity_days | integer | – | Maximum validity in days (fixed-data plans) |
| min_data_gb | number | – | Minimum data in GB (fixed-data plans) |
| unlimited | boolean | – | If set, return only unlimited (true) or only fixed-data (false) plans |
No output schema declared.
No examples provided.
topup_esim Create eSIM top-up checkout link ~172
Recharge an eSIM the customer already owns with more data: builds a cart and returns a checkout URL to pay by credit card on hungry-esim.com. The installed SIM keeps working — no new QR code is issued. Use this instead of create_checkout when the traveller already has one of our eSIMs. Does NOT charge — the user completes payment on the website. Get iccid from my_esims and package_code from list_esim_topups.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Customer's CHECKOUT country (ISO alpha-2) — sets checkout region/currency and URL locale. Defaults to US. |
| iccid | string | yes | ICCID of the eSIM to top up, from my_esims |
| package_code | string | yes | Top-up package code from list_esim_topups |
No output schema declared.
No examples provided.
How do I install the Hungry eSIM MCP server?
Hungry eSIM is a hosted endpoint at https://api.hungry-esim.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.hungry-esim.com
claude mcp add --transport http com-hungry-esim-esim 'https://api.hungry-esim.com/mcp'
What is the Hungry eSIM MCP server?
Hungry eSIM is an MCP server listed in the public MCP registry as com.hungry-esim/esim. Travel eSIMs: unlimited data, pick your days, top up existing eSIMs, card checkout, no API key. This page covers its hosted endpoint (https://api.hungry-esim.com/mcp).
Is the Hungry eSIM MCP server safe to use?
Hungry eSIM scores 88 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Hungry eSIM MCP server expose?
Hungry eSIM exposes 10 tools: search_esim_plans, get_plan_details, create_checkout, get_order_status, my_esims, and 5 more. Their descriptions and schemas cost roughly 1,667 tokens of context every time the server is loaded.
Does the Hungry eSIM MCP server require authentication?
No. We connected to Hungry eSIM without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Hungry eSIM MCP server still maintained?
Hungry eSIM is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.