Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

SimoraGo travel eSIM plans

REMOTE · SIMORAGO.COM

Compare travel eSIM plans for 100+ countries: price, price per GB, daily data cap, hotspot rule.

Available components

74 Trust /100

Last scanned (6 hours ago)

Scores higher than 61% of remote servers

Reachable. Last reached 5 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability78
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1564 tokens (~195/item across 8 items; 7 tools + 1 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 Management0
  • Stability check failed: schema churn in the 2 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
  • Supports UI / widget rendering.Pass
Changelog

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.

  • 4 Nov 26 0
    • Stability: unverified → fail ▼ security
    • Tool “get_policies” rewrote its description, which is the text the model reads security
    • Tool “list_destinations” rewrote its description, which is the text the model reads security
    • Tool “search_plans” rewrote its description, which is the text the model reads security
    • Schema quality: 168 → 195 ▼ functional
    • “search_plans” made “destination” required, so existing callers break ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 1.0.0 → 1.1.0 functional
    • New tool “recommend_plan” functional
    • “search_plans” added an optional parameter “also_countries” cosmetic
    • “search_plans” added an optional parameter “max_price_usd” cosmetic
    • “search_plans” added an optional parameter “sort” cosmetic
    • “search_plans” reworded the description of “destination” cosmetic
    • “search_plans” reworded the description of “limit” cosmetic
    • “search_plans” reworded the description of “min_gb” cosmetic
    • “search_plans” reworded the description of “trip_days” cosmetic
    • “search_plans” dropped the optional parameter “country” cosmetic
    • Tool “get_policies” changed its title: Get refund, activation and payment policies → eSIM install guide, refunds and phone compatibility cosmetic
    • Tool “list_destinations” changed its title: List eSIM destinations and coverage → List the countries with travel eSIM plans cosmetic
    • Tool “search_plans” changed its title: Search and compare travel eSIM data plans → Find and compare travel eSIM plans cosmetic
  • 3 Nov 26 74

    First indexed and scored.

Diagnostics

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 5 Nov 2026 · Probed https://simorago.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=simorago.com CN=Amazon RSA 2048 M04,O=Amazon,C=US 6 Oct 2026 21 Apr 2027 RSA 2048 SHA256-RSA dd318e6e8bff79e558c3e4dc904a63d
SANs: simorago.com, www.simorago.com
CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 773124f2a952e3ed18a58bdb85d1bc0ce5f27
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of simorago.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
simorago.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=31536000
x-content-type-options nosniff
x-frame-options SAMEORIGIN
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://simorago.com/mcp Verified 200
http (plaintext) http://simorago.com/mcp HTTPS enforced 301 https://simorago.com/mcp
MCP tools · 7 exposed · ~1,421 tokens

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 →

Tool Tokens
check_coverage ~204

Check whether a country is covered, plan by plan: for example, does the Europe eSIM cover France or Turkey? Regional plans can leave countries out, so a destination's country list is not every plan's coverage. Returns, per plan, covered yes / no / not published, with name, validity and price in USD, and a one-line summary such as "Covered by 2 of 7 Europe plans". Leave destination out to find every destination that includes the country (its own page first, then regional plans).

NameTypeReqDescription
countrystringyesThe country to check: two-letter ISO code (FR) or its name in any site language (France, Francia, Frankreich).
destinationstring–Destination slug or name whose plans to check, for example europe. Leave out to check every destination.
localestring–Language for plan names, destination names and page links: en, es, de, fr, pt or he. Default en.

No output schema declared.

No examples provided.

get_checkout_link ~126

Get the simorago.com checkout page link for one plan, with purchasable (whether checkout is open now). Payment is made by the traveller on simorago.com in a browser; this tool does not buy anything. Use it when someone wants to buy a plan found with search_plans.

NameTypeReqDescription
localestring–Language for plan names, destination names and page links: en, es, de, fr, pt or he. Default en.
plan_idstringyesPlan id exactly as returned by search_plans (the id field of a plan).

No output schema declared.

No examples provided.

get_plan ~136

Get the full facts for one travel eSIM plan by its id: price in USD, data, validity, daily limit and throttled speed, hotspot / tethering rule, networks, covered and not covered countries, SMS, 5G, top-up, and whether checkout is open. Use it after search_plans when someone asks about a specific plan.

NameTypeReqDescription
localestring–Language for plan names, destination names and page links: en, es, de, fr, pt or he. Default en.
plan_idstringyesPlan id exactly as returned by search_plans (the id field of a plan).

No output schema declared.

No examples provided.

get_policies ~119

How to install and activate a travel eSIM (an emailed link to an install page with the QR code), whether a phone will work (it must be eSIM-capable and carrier-unlocked), refunds and cancellation (before the eSIM is installed, less a small fee), and payment checks. Use it for questions about installing or activating an eSIM, refunds, or phone compatibility.

NameTypeReqDescription
localestring–Language for plan names, destination names and page links: en, es, de, fr, pt or he. Default en.

No output schema declared.

No examples provided.

list_destinations ~125

List the countries and regions you can get a SimoraGo travel eSIM for right now, from the live catalogue, including the Europe and Global plans: for each, the number of plans, the lowest price in USD, the ISO codes of the countries it covers and its page link. Use it when someone asks which countries or destinations are available. For whether a given plan covers a country, use check_coverage.

NameTypeReqDescription
localestring–Language for plan names, destination names and page links: en, es, de, fr, pt or he. Default en.

No output schema declared.

No examples provided.

recommend_plan ~291

Recommend which travel eSIM to buy for a trip. Give the destination (country, region or city), any other countries on the same trip, the trip length and how the traveller uses data (light: maps and messages; normal: plus social media and browsing; heavy: video, video calls or hotspot). Estimates the data needed and returns up to 3 plans valid for the whole trip, each with a reason: best_fit (cheapest that covers the estimate), budget (cheaper, below the estimate) and roomier (more data). Each plan has its price in USD, data, daily cap, hotspot rule, networks and page link.

NameTypeReqDescription
also_countriesarray–Other countries on the same trip, by name or ISO code; only plans covering all of them are recommended.
destinationstringyesWhere the traveller is going: a country, region or city, by name or ISO code (Mexico, JP, Europe, Rome).
localestring–Language for plan names, destination names and page links: en, es, de, fr, pt or he. Default en.
trip_daysintegeryesTrip length in days (the whole trip for several countries).
usagestring–How the traveller uses data: light (maps, messages), normal (plus social media, browsing; default) or heavy (video, video calls, hotspot).

No output schema declared.

No examples provided.

search_plans ~420

Find the cheapest travel eSIM data plans for a trip: one country, a region, or several countries on the same trip (also_countries). Filter by trip length (trip_days), data needed (min_gb) and budget (max_price_usd); sort by price or price per GB. Each plan has its price in USD and price per GB, data (GB, or a daily high-speed allowance and the speed after it), validity in days, the hotspot / tethering rule, mobile networks, countries not covered and its simorago.com page. Use it to recommend, compare or price eSIMs for a trip, for what an unlimited plan's daily high-speed limit is and how slow it gets after it (throttled speed), or when someone asks how to get mobile data abroad without roaming charges.

NameTypeReqDescription
also_countriesarray–Other countries on the same trip, by name or ISO code. Only plans covering all of them are returned (Paris then Rome: destination France, also_countries ["Italy"]).
destinationstringyesWhere the traveller is going: a country, region or city, by name or ISO code (Japan, JP, Italy, Europe, Tokyo). A country without plans of its own returns the regional plans that cover it.
limitinteger–Most plans to return per destination. Default 10.
localestring–Language for plan names, destination names and page links: en, es, de, fr, pt or he. Default en.
max_price_usdnumber–Highest total price in US dollars.
min_gbnumber–Least data needed, in GB. Daily-allowance plans always match.
sortstring–price (default, cheapest first) or price_per_gb (lowest price per GB of high-speed data first).
trip_daysinteger–Length of the trip in days. Returns only plans valid for at least this many days, so the plan lasts the whole trip.

No output schema declared.

No examples provided.

Install

How do I install the SimoraGo travel eSIM plans MCP server?

SimoraGo travel eSIM plans is a hosted endpoint at https://simorago.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 · simorago.com

# add to Claude Code
claude mcp add --transport http com-simorago-esim 'https://simorago.com/mcp'
Common questions

What is the SimoraGo travel eSIM plans MCP server?

SimoraGo travel eSIM plans is an MCP server listed in the public MCP registry as com.simorago/esim. Compare travel eSIM plans for 100+ countries: price, price per GB, daily data cap, hotspot rule. This page covers its hosted endpoint (https://simorago.com/mcp).

Is the SimoraGo travel eSIM plans MCP server safe to use?

SimoraGo travel eSIM plans scores 74 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 SimoraGo travel eSIM plans MCP server expose?

SimoraGo travel eSIM plans exposes 7 tools: search_plans, recommend_plan, get_plan, check_coverage, list_destinations, and 2 more. Their descriptions and schemas cost roughly 1,421 tokens of context every time the server is loaded.

Does the SimoraGo travel eSIM plans MCP server require authentication?

No. We connected to SimoraGo travel eSIM plans without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the SimoraGo travel eSIM plans MCP server still maintained?

SimoraGo travel eSIM plans is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.