Skip to content

Hungry eSIM MCP server

com.hungry-esim/esimhungry-esim.comstreamable-httpv1.1.0Scanned

Travel eSIMs: unlimited data, pick your days, top up existing eSIMs, card checkout, no API key.

10 tools: 1 do something that can't be undone, 2 change things and 7 only read.

Tools: 0 delete, 1 irreversible, 2 write, 7 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Hungry eSIM MCP server can do

The Hungry eSIM MCP server is published by hungry-esim.com, a domain the MCP Registry verified. It has 10 tools. It can do things that cannot be undone, such as sending, paying or publishing (topup_esim) and create or change data (2 tools: create_checkout and check_destination_coverage), but cannot delete data. 7 tools only read.

1 tool brings in text other people can write (get_order_status).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 10, 2026, version 1.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

10 tools

Can't be undone 1Claude Code: ask
  • topup_esimRecharge 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.No findings

    Why it is in this group

    • The name "topup_esim" says "topup": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
Changes things 2Claude Code: ask
  • check_destination_coverageCheck 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?".No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • create_checkoutBuy 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.No findings

    Why it is in this group

    • The name "create_checkout" says "create": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
Only reads 7Show 7 read-only tools
  • find_cheapest_planFind the lowest-priced eSIM data plan for a destination — for "what's the cheapest", "budget option", "cheapest SIM / data plan for X".No findings

    Why it is in this group

    • The name "find_cheapest_plan" says "find": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_order_statusLook up an eSIM order and return its status plus the SIM install details: install link, LPA activation code, QR image URL, and ICCID.Reads text others writeNo findings

    Why it is in this group

    • The name "get_order_status" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_plan_detailsGet everything about one eSIM data plan: which countries the SIM roams in, data volume, validity in days, speed and fair-use throttling, and price.No findings

    Why it is in this group

    • The name "get_plan_details" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • list_esim_topupsList the data top-up (recharge / refill) packages that can be added to an eSIM the customer already owns.No findings

    Why it is in this group

    • The name "list_esim_topups" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • my_esimsList the SIM cards (eSIMs) already on the signed-in Hungry eSIM account: ICCID, status, data package, expiry, and install link.No findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • my_ordersList the signed-in customer's recent eSIM purchases with payment and provisioning status.No findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • search_esim_plansSearch prepaid travel eSIM data plans for a destination — the SIM card / mobile data / roaming option for a trip.No findings

    Why it is in this group

    • The name "search_esim_plans" says "search": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:40 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://api.hungry-esim.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://api.hungry-esim.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 irreversible, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.hungry-esim.com/mcp: tools/list returned 10 tools to an anonymous client, including topup_esim (irreversible), create_checkout (write), check_destination_coverage (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http esim https://api.hungry-esim.com/mcp
claude mcp add --transport http esim https://api.hungry-esim.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__esim__search_esim_plans",
      "mcp__esim__get_plan_details",
      "mcp__esim__get_order_status",
      "mcp__esim__my_esims",
      "mcp__esim__list_esim_topups",
      "mcp__esim__my_orders",
      "mcp__esim__find_cheapest_plan"
    ],
    "ask": [
      "mcp__esim__create_checkout",
      "mcp__esim__topup_esim",
      "mcp__esim__check_destination_coverage"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as esim. Review it before you use it.

Capability tags behind 1 rule
  • mcp__esim__get_order_status untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.hungry-esim/esim/verify?hash=685da827ff51ccf6d93f4085cb1d1875bb6a3e39fd24d173f83d29c163d19ff9" | jq -e '.changed == false'

Pinned hash 685da827ff51, from Nov 10, 2026, 17:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.hungry-esim/esim/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.hungry-esim/esim
[![Anlyon Radar](https://radar.anlyon.com/badge/com.hungry-esim/esim.svg)](https://radar.anlyon.com/servers/com.hungry-esim/esim)

Source: MCP Registry · repository. Synced Oct 21, 2026, 17:56 UTC.

Hungry eSIM MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Hungry eSIM MCP server safe?

No scan can promise that. What its definitions show: 10 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Hungry eSIM MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Hungry eSIM MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: topup_esim.

What tools does the Hungry eSIM MCP server have?

10 tools: 1 irreversible, 2 write, 7 read. topup_esim, create_checkout, check_destination_coverage, search_esim_plans, get_plan_details, get_order_status, my_esims, list_esim_topups and 2 more.

Does the Hungry eSIM MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Hungry eSIM MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Hungry eSIM MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.