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.

SimFuse eSIM Storefront

REMOTE · SIMFUSE.APP

Travel eSIMs for 200+ countries. Browse plans, price a multi-country trip, and open a checkout.

Available components

+3 this week 79 Trust /100

Last scanned (23 hours ago)

Scores higher than 74% of remote servers

Reachable. Last reached 21 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 Security83
  • 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 4777 tokens (~318/item across 15 items; 15 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 Management47
  • Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 16 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 7 Nov 26 73

    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 21 Nov 2026 · Probed https://simfuse.app/agentic/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=simfuse.app CN=WE1,O=Google Trust Services,C=US 19 Nov 2026 17 Feb 2027 ECDSA 256 ECDSA-SHA256 5f773b05cfe59360134a38d3088ba7cb
SANs: simfuse.app, go.simfuse.app, *.go.simfuse.app
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of simfuse.app. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
simfuse.app. DS published 2371 13 Verified
simfuse.app. Verified address RRset verified with the apex keys
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; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy same-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://simfuse.app/agentic/mcp Verified 200
http (plaintext) http://simfuse.app/agentic/mcp HTTPS enforced 301 https://simfuse.app/agentic/mcp
MCP tools · 15 exposed · ~3,734 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
build-plan ~459

Build an eSIM plan to the traveller's liking for one destination: how much data, for how many days, optionally which network it runs on and whether calls and texts are bundled. Returns the one real plan that matches, with its id and live price, never a made-up combination: a shape nobody sells is snapped to the nearest one that is, one axis at a time, and every change is spelled out in `adjustments` so you can read it back. Use it when the traveller knows what they want ("10 GB on Docomo for two weeks"); use plan-trip when they want a recommendation or the trip has several countries. To buy, pass `plan.id` to get-checkout-link when a person is paying, or to create-checkout-session when you are. Read-only: it reserves nothing and charges nothing.

NameTypeReqDescription
country_codestringyesISO 3166-1 alpha-2 code of the destination, e.g. "JP". Look it up with list-destinations rather than guessing.
currencystring–Optional. ISO 4217 three-letter code the price is quoted in, e.g. "USD", "EUR", "GBP". Defaults to EUR. An unknown code falls back to EUR rather than failing.
data_mbintegeryesData allowance wanted, in megabytes: 1 GB is 1024 MB, so 5 GB is 5120. Pass 0 for an unlimited plan. Snapped to the nearest size sold when no plan has exactly this size.
networkstring–Optional. The mobile network the plan should run on, by carrier name as `options.networks` lists them, e.g. "NTT Docomo" or "au". Matching is case-insensitive and a single carrier of a multi-network…
validity_daysintegeryesHow many days the plan should stay valid, 1 to 365. Snapped to the nearest length sold for the chosen size.
voiceboolean–Optional. True to require a plan that bundles calls and texts. Defaults to false, data only. If no such plan exists the answer is data only and says so.
NameTypeReqDescription
adjustmentsarrayyesEvery way the built plan differs from what was asked, one sentence each, written to be read to the traveller. Empty when the plan matches the request exactly.
builtobject|nullyesThe specification of the plan actually built, after any adjustment. Null when nothing was found.
foundbooleanyesTrue when a plan was built. False when the destination sells nothing at all, in which case `plan` is null.
optionsobjectyesWhat else could be asked for, so a follow-up question can be answered without another call.
planobject|nullyesThe plan built: the same shape get-plan returns. Its `id` is what you buy with. Null when nothing was found.
requestedobjectyesThe specification exactly as it was asked for.

No examples provided.

check-coverage ~132

Answer "does this eSIM plan work in X?" for one destination, as a yes or no rather than a country list. Takes a plan id and a destination (a country name or two-letter code). Reports whether the destination is covered, and separately whether it is explicitly excluded from an otherwise regional plan. Use get-plan-coverage when you need the full list of countries instead.

NameTypeReqDescription
destinationstringyesThe country to check: a name ("Japan") or a two-letter code ("JP").
plan_idstringyesThe plan id (a ULID) as returned by list-plans.
NameTypeReqDescription
coverage_typestringyes"country", "region" or "global".
coveredbooleanyesWhether this plan works at that destination.
destinationobjectyes–
excludedbooleanyesWhether the destination is explicitly carved OUT of an otherwise regional plan. A different fact from simply not being included, and the only one of the two that means "do not buy this for that trip"…
is_worldwidebooleanyesWhether the plan is sold as worldwide.
notestringyesThe answer in a sentence, including what to do next when it is a no.
plan_idstringyesThe plan that was checked.
plan_namestringyesIts name, e.g. "Europe 10GB".
region_labelstring|nullyesReadable scope of a regional plan, e.g. "Europe". Null for a country plan.
total_countriesintegeryesHow many countries the plan covers in total.

No examples provided.

check-esim-usage ~167

How much data an eSIM has used and how much is left, for one eSIM on a paid order. Identified by the order id and the email that bought it, plus the ICCID from get-order-status or get-esim-activation. Allowances are in megabytes. Readings are served from a cache refreshed every couple of minutes: checked_at says when the reading was taken. An unlimited plan reports its full-speed allowance for the current period rather than a total.

NameTypeReqDescription
emailstringyesThe email address the order was bought with.
iccidstringyesThe ICCID of the eSIM to read, as returned by get-order-status.
order_idstringyesThe order id from the buyer's confirmation email or order page.
NameTypeReqDescription
activated_atstring|nullyesWhen the eSIM first connected, ISO 8601. Null before activation.
checked_atstring|nullyesWhen this reading was TAKEN, ISO 8601. Readings come from a cache refreshed every couple of minutes, so do not present the number as live.
data_remaining_mbinteger|nullyesMegabytes left. NULL on an unmetered plan, which does not mean zero: it means the supplier reports no allowance to count down.
data_total_mbinteger|nullyesSize of the current bundle in megabytes, reflecting any top-ups. Null on an unmetered plan.
data_used_mbinteger|nullyesMegabytes used on the current bundle; 1 GB is 1024 MB.
expires_atstring|nullyesWhen the plan lapses, ISO 8601. Null when the supplier reports none.
iccidstringyesThe eSIM this reading belongs to.
is_unlimitedbooleanyesWhether the plan is sold as unlimited. Almost none are uncapped: see the period fields for what that actually means here.
percentage_remainingnumber|nullyesShare of the bundle left, 0-100. Null on the same terms.
percentage_usednumber|nullyesShare of the bundle spent, 0-100. Null on an unmetered plan, where there is no total to be a share of.
period_high_speed_mbinteger|nullyesSize of that period allowance, so the figure above can be read as "945 MB of 3 GB left today".
period_reduced_speed_kbpsinteger|nullyesSpeed the plan throttles to once the period allowance is spent. NULL means the data STOPS instead, which is a different thing to tell a traveller.
period_remaining_mbinteger|nullyesFull-speed data left in the CURRENT reset period, for a plan whose allowance refills (say 3 GB a day). Null when the plan has no reset period. Deliberately separate from data_remaining_mb, which desc…
period_resetstring|nullyesHow often it refills: "daily", "weekly" or "monthly". Null when it does not.
statusstring|nullyeseSIM state at the time of the reading, e.g. "active".

No examples provided.

create-checkout-session ~342

Open a checkout session for one or more eSIM plans at frozen prices, using the plan ids that plan-trip, list-plans or get-plan returned. Use it once the traveller has chosen what to buy. It CHARGES NOTHING and reserves no stock: it prices the basket, freezes those prices until the session's price_locked_until, and hands back the session plus a bearer agent key. Payment, completion and cancellation happen afterwards over the SimFuse agentic HTTP API with that key, as the session's `note` explains, and the eSIM is delivered by email once payment settles. Each call opens a NEW session and mints a NEW key, so call it once per basket rather than retrying it to re-read one.

NameTypeReqDescription
agent_namestring–Optional. Name of the assistant or app opening the session, e.g. "Claude". Recorded on the agent key so we can tell integrations apart. Defaults to "mcp-client".
buyer_emailstring–Optional but strongly recommended. The traveller's email address, where the eSIM and its installation details are sent once payment settles. Ask for it rather than inventing one.
currencystring–Optional. ISO 4217 three-letter code to price the session in, e.g. "USD", "EUR", "GBP". Defaults to EUR. Every amount in the answer is minor units (cents) of this currency.
itemsarrayyesWhat to buy: one entry per plan, 1 to 50 entries. Pass the whole basket in one call, e.g. [{"id":"01JVQ...","quantity":1}].
NameTypeReqDescription
agent_keystringyesThe bearer key for every follow-up call on this session, shown ONCE and never again. Send it as "Authorization: Bearer <key>". It is a credential: use it, do not read it out to the traveller.
apiobjectyesThe HTTP endpoints for this session, all taking the agent_key as a bearer token.
notestringyesHow to use the key and how long the prices hold. Worth following literally.
sessionobjectyesThe priced checkout session, in the same shape the agentic HTTP API returns it.

No examples provided.

get-checkout-link ~214

Get the page where a person buys one specific eSIM plan, for an assistant to hand them a link. The page sells exactly this plan with Apple Pay, Google Pay and card, takes the email at payment, and sends the eSIM there. Nothing is charged or reserved by this call and the buyer needs no account. Use this whenever a PERSON is going to pay. Use create-checkout-session instead when the agent is settling the purchase itself, or for more than one plan or unit.

NameTypeReqDescription
currencystring–Three-letter currency code for the price quoted back to you (e.g. "USD", "EUR"). Defaults to EUR. The page itself prices in the buyer's own currency.
plan_idstringyesThe plan id (a ULID) as returned by list-plans, get-plan or plan-trip.
sourcestring–The name of the assistant or app sending the buyer, recorded as the campaign source on the link (e.g. "claude"). Optional.
NameTypeReqDescription
notestringyesWhat the buyer will see on that page, in words you can repeat to them.
planobjectyes–
urlstringyesThe page to give the buyer. Opens the plan with Apple Pay, Google Pay and card on it. Safe to show to a person.

No examples provided.

get-destination-info ~151

Details for one destination: its name and codes, region, how many eSIM plans are sold there, the cheapest and most expensive, the smallest and largest data bundles, and its storefront page. Takes a country name ("Japan") or two-letter code ("JP"). Use this to describe a destination before pulling its full plan ladder with list-plans. Whether a plan can be topped up varies by plan and is reported by list-plans, not here.

NameTypeReqDescription
currencystring–Three-letter currency code for the prices (e.g. "USD", "EUR"). Defaults to EUR.
destinationstringyesThe destination: a country name ("Japan") or a two-letter code ("JP").
NameTypeReqDescription
currencystringyesISO 4217 code every amount below is quoted in, e.g. "EUR".
iso2stringyesISO 3166-1 alpha-2 code, e.g. "JP". This is the code list-plans and plan-trip take.
iso3stringyesISO 3166-1 alpha-3 code, e.g. "JPN".
linksobjectyes–
namestringyesEnglish country name, e.g. "Japan".
notestringyesHow to read the numbers above, and what to call next.
plansobjectyes–
regionstring|nullyesThe region this country is filed under, e.g. "Asia". Null when it is filed under none.

No examples provided.

get-esim-activation ~152

Fetch the installable eSIM(s) for a paid order: the QR code image, the LPA activation string, the SM-DP+ address and activation code for manual entry, one-tap install links for iPhone and Android, and a hosted install page to send the buyer. Identified by the order id together with the email that bought it. Returns an empty esims list while provisioning is still in flight, which normally clears within a minute of payment.

NameTypeReqDescription
emailstringyesThe email address the order was bought with. Required: the order id alone does not identify a buyer.
order_idstringyesThe order id from the buyer's confirmation email or order page.
NameTypeReqDescription
esimsarrayyesEvery eSIM on this order. EMPTY while provisioning is still in flight.
notestringyesHow to get the profile onto the traveller's phone.
order_idstringyesThe order, echoed back.
statusstringyesOrder state, e.g. "completed".

No examples provided.

get-order-status ~156

Check an eSIM order after payment: whether it completed and whether its eSIMs have been provisioned yet. Identified by the order id together with the email that bought it, both of which are on the buyer's confirmation email. Provisioning usually finishes within a minute of payment, so an order that is paid but lists no eSIMs yet is normal: check again shortly. Once an eSIM is listed, use get-esim-activation to fetch its QR code and install details.

NameTypeReqDescription
emailstringyesThe email address the order was bought with. Required: the order id alone does not identify a buyer.
order_idstringyesThe order id from the buyer's confirmation email or order page.
NameTypeReqDescription
esimsarrayyesEvery eSIM provisioned on this order. EMPTY while provisioning is still in flight, which is normal for the first minute after payment and never means the order failed.
notestringyesWhat to do next, given the list above.
order_idstringyesThe order, echoed back.
placed_atstring|nullyesWhen the order was created, ISO 8601. Null on the rare row that has no timestamp.
statusstringyesOrder state, e.g. "completed" or "pending". "completed" is about the eSIM having provisioned, not about the money.

No examples provided.

get-plan ~242

Read everything about one eSIM plan by its id: data allowance, how long it stays valid, what happens after a fair-use cap, whether hotspot and top-ups are supported, the network it runs on, and the retail price in the currency you ask for. Use it to answer a specific question about a plan already found with list-plans or plan-trip, and before buying, to confirm the plan really matches what the traveller asked for. Ask get-plan-coverage instead when the question is which countries it works in. Read-only: it reserves nothing and charges nothing.

NameTypeReqDescription
currencystring–Optional. ISO 4217 three-letter code the price is quoted in, e.g. "USD", "EUR", "GBP". Defaults to EUR. An unknown code falls back to EUR rather than failing.
plan_idstringyesThe plan id: a 26-character ULID as returned by list-plans or plan-trip, e.g. "01JVQ2S6D4X8N0RMB7YQZ5K3TA". Slugs and supplier codes are not accepted, and an id must never be invented.
NameTypeReqDescription
carrierobject|nullyesThe mobile network this plan runs on, when we can name it. Null when we cannot.
countryobject|nullyesThe one country this plan is filed under. Null for a regional or worldwide plan.
coverage_countintegeryesHow many countries coverage_countries holds.
coverage_countriesarrayyesEvery country the plan works in.
coverage_typestringyesScope of the plan: one country, a region, or worldwide.
currencystring|nullyesISO 4217 code retail_price_cents is quoted in, e.g. "EUR".
data_amount_mbintegeryesData allowance in megabytes (1 GB is 1024 MB). 0 on an unlimited plan, where data_usage_policy carries the real terms.
data_restriction_typestringyesWhether the allowance is capped ("limited") or unmetered ("unlimited").
data_usage_policyobject|nullyesWhat the plan really gives you. Null when the supplier has never published its terms, which is different from having no limits.
excluded_countintegeryesHow many countries excluded_countries holds.
excluded_countriesarrayyesCountries in this plan's own region that it does NOT cover. Always empty for a country plan and for a worldwide one.
hotspot_usage_policyobject|nullyesWhat the plan lets you do with a hotspot. Null when the terms were never established, which is different from being allowed.
idstringyesThe plan id (a 26-character ULID). Pass it to get-plan, get-plan-coverage or create-checkout-session. Never invent one.
is_worldwidebooleanyesTrue when the plan is sold as a worldwide bundle.
linksobjectyesWhere a person buys this plan on simfuse.app.
namestringyesPlan name as a traveller sees it, e.g. "Spain 5GB".
networkstring|nullyesThe network name as plain text, or null when unknown.
network_generationstring|nullyesThe network generation the plan is sold as, exactly as stated for it. Null means not stated, which is not the same as any generation; say "not stated" rather than assuming.
network_typestringyesDeprecated two-valued form: "5G" for a 5G plan, "LTE" for everything else including plans whose generation was never stated. Read network_generation.
operatorsarrayyesNetwork operators the plan roams on, as a list. Empty when none are published.
regionstring|nullyesRaw region value for a regional plan, e.g. "Europe". Null for a country plan.
region_labelstring|nullyesThe region formatted for a person to read. Null for a country plan.
retail_price_centsinteger|nullyesRetail price in minor units (cents) of `currency`, so 1250 in EUR is 12.50 EUR. This is what a buyer pays for one eSIM.
retail_prices_centsobject–Prices in other currencies, keyed by ISO 4217 code, in minor units. Only the multi-currency surfaces (the catalog export) carry one, so it is absent here: read retail_price_cents and currency instead.
supports_tetheringboolean|nullyesWhether hotspot or tethering is allowed. Null means no supplier has declared it, which is not the same as "no".
supports_topupbooleanyesWhether more data can be bought for the same eSIM once it runs low.
typestringyesWhat the plan sells: data only, or data plus a bundled voice and SMS allowance.
validity_daysintegeryesHow many days the plan stays valid once it activates.

No examples provided.

get-plan-coverage ~165

List every country one eSIM plan works in, plus any country of its own region that it leaves out. Use it to answer "does this plan also cover Austria?" for a regional or worldwide plan, where the plan name says a region and the traveller needs the actual list. For a single-country plan the answer is that one country. Ask get-plan instead for the data allowance, validity or price. Read-only.

NameTypeReqDescription
plan_idstringyesThe plan id: a 26-character ULID as returned by list-plans or plan-trip, e.g. "01JVQ2S6D4X8N0RMB7YQZ5K3TA". Slugs and supplier codes are not accepted, and an id must never be invented.
NameTypeReqDescription
countriesarrayyesEvery country the plan works in. Match on iso2 to answer "does this cover X?".
coverage_typestringyesScope of the plan: one country, a region, or worldwide.
excluded_countriesarrayyesCountries in the plan's own region that it does not cover. Always empty for a country plan and for a worldwide one.
is_worldwidebooleanyesTrue when the plan is sold as a worldwide bundle.
region_labelstring|nullyesThe plan's region written for a person, e.g. "Europe". Null for a country plan.
totalintegeryesHow many countries the plan covers.
total_excludedintegeryesHow many countries of the plan's own region it does NOT cover.

No examples provided.

list-destinations ~243

Find the countries SimFuse sells eSIMs for, with the cheapest plan price ("from" price) for each in the currency you ask for. Start here when someone names a place: it turns "Portugal" into the two-letter country code the other tools take, and shows what that destination starts at. For one destination, follow it with list-plans; for a trip covering two or more countries, use plan-trip instead. Read-only, and it answers from the SimFuse catalog alone.

NameTypeReqDescription
currencystring–Optional. ISO 4217 three-letter code the "from" prices are quoted in, e.g. "USD", "EUR", "GBP". Defaults to EUR. An unknown code falls back to EUR rather than failing.
limitinteger–Optional. Maximum destinations to return, 1 to 300. Defaults to 300, which is the whole list.
searchstring–Optional. Match destinations by name, ISO 3166-1 alpha-2 or alpha-3 code, case-insensitively. A partial name works: "port" matches Portugal. Omit to list every destination.
NameTypeReqDescription
currencystringyesISO 4217 code every from_price_cents below is quoted in, e.g. "EUR".
destinationsarrayyesThe matching destinations. Empty when nothing matched.
returnedintegeryesHow many destinations are in this response.
totalintegeryesHow many destinations matched, before `limit` was applied.

No examples provided.

list-plans ~544

Show the eSIM plans on sale for one country or region, or search the whole catalog, narrowing by data allowance, validity and price. Use destination with a country code from list-destinations, or region with a slug from list-regions; never both. Use it when the traveller wants to compare what is available or find a plan inside a budget. Prices are live retail prices in the currency you ask for. For a trip covering two or more countries, use plan-trip first: it compares one plan for the whole route against one plan per country and picks the cheapest complete answer. Pass a plan id from here to get-plan, get-plan-coverage or create-checkout-session. Read-only, and it answers from the SimFuse catalog alone.

NameTypeReqDescription
currencystring–Optional. ISO 4217 three-letter code prices are quoted and filtered in, e.g. "USD", "EUR", "GBP". Defaults to EUR. An unknown code falls back to EUR rather than failing.
destinationstring–Optional. ISO 3166-1 alpha-2 destination country code, e.g. "US", "GB", "DE". Look it up with list-destinations rather than guessing. Cannot be combined with region. Omit both destination and region…
limitinteger–Optional. Maximum plans to return, 1 to 100. Defaults to 25.
max_data_amount_mbinteger–Optional. Only plans with at most this much data, in megabytes.
max_price_centsinteger–Optional. Only plans at or below this retail price, in minor units (cents) of `currency`: 2500 is 25.00.
max_validity_daysinteger–Optional. Only plans valid for at most this many days.
min_data_amount_mbinteger–Optional. Only plans with at least this much data, in MEGABYTES: 1 GB is 1024, 10 GB is 10240.
min_price_centsinteger–Optional. Only plans at or above this retail price, in minor units (cents) of `currency`: 500 is 5.00.
min_validity_daysinteger–Optional. Only plans valid for at least this many days, e.g. 14 for a two-week trip.
regionstring–Optional. Canonical region slug, e.g. "europe", "southeast-asia" or "global", to search that regional shelf. Cannot be combined with destination. Unknown regions return no plans.
NameTypeReqDescription
currencystringyesISO 4217 code every price below is quoted in, e.g. "EUR".
matchedintegeryesHow many plans matched the filters, before `limit` was applied.
plansarrayyesThe matching plans. Empty when nothing matched.
returnedintegeryesHow many plans are in this response.
truncated_by_candidate_capbooleanyesTrue when a catalog-wide search hit its internal candidate cap, so there are further matches this call could not see. Narrow it with a destination or a tighter data or validity filter rather than ass…

No examples provided.

list-regions ~205

Discover available eSIM regions, including worldwide scopes, with their canonical slugs, display names, member countries and starting prices. Only published regions with active displayed regional plans are listed. Pass a returned region slug to list-plans as region, not destination. Country membership describes the region, not a promise that every plan covers every member: check get-plan-coverage for a specific plan. Read-only; no account or key is needed.

NameTypeReqDescription
currencystring–Optional. ISO 4217 code for starting prices, e.g. "EUR" or "USD". Defaults to EUR; unknown codes fall back to the base currency.
limitinteger–Optional. Maximum regions to return, 1 to 300. Defaults to 300. total reports the match count before this limit.
searchstring–Optional. Case-insensitive partial match on the canonical region slug or display name, e.g. "asia". Omit to list all available regions.
NameTypeReqDescription
currencystringyesISO 4217 code for all starting prices.
regionsarrayyesAvailable regions in storefront order. Empty when nothing matches.
returnedintegeryesNumber of regions in this response.
totalintegeryesMatching regions before applying limit.

No examples provided.

list-topup-options ~200

Data top-ups that can be added to an eSIM the buyer already has, narrowed to what its network will actually accept. Identified by the order id and the email that bought it, plus the ICCID. Read-only: a top-up is bought in the SimFuse app, not through this server, and the response carries the link that opens this eSIM there. Do not pass these package ids to create-checkout-session, which would buy a separate new eSIM rather than add data to this one.

NameTypeReqDescription
currencystring–Three-letter currency code for the prices (e.g. "USD", "EUR"). Defaults to EUR.
emailstringyesThe email address the order was bought with.
iccidstringyesThe ICCID of the eSIM to top up, as returned by get-order-status.
order_idstringyesThe order id from the buyer's confirmation email or order page.
NameTypeReqDescription
currencystringyesISO 4217 code every price below is quoted in, e.g. "EUR".
iccidstringyesThe eSIM these options apply to.
optionsarrayyesTop-ups the eSIM's own network will accept against this profile. EMPTY means it cannot be topped up at all, and more data means a new eSIM.
purchaseobjectyes–

No examples provided.

plan-trip ~362

Answer "which eSIM should I buy for this trip?". Give it the stops, a country code and the days spent in each, and it compares one plan covering the whole route against one plan per country against a mix of the two, on live prices, then flags the cheapest option that covers everything and explains the choice in a sentence you can quote. It also estimates the data each stop needs, names any country SimFuse cannot cover, and returns package ids that go straight into create-checkout-session. Use it whenever a trip has two or more countries, and for a single country when the traveller wants a recommendation rather than a list. Read-only: nothing is reserved and nothing is charged, and the totals are today's catalog prices, not a quote held for later.

NameTypeReqDescription
currencystring–Optional. ISO 4217 three-letter code every price is quoted in, e.g. "USD", "EUR", "GBP". Defaults to EUR. An unknown code falls back to EUR rather than failing.
startstring–Optional. Departure date as YYYY-MM-DD, e.g. "2026-04-18". Only used to date the stops in the answer; it does not change prices. Defaults to today.
stopsarrayyesThe trip, one entry per country, in travel order. 1 to 12 stops, e.g. [{"country":"JP","days":7},{"country":"KR","days":5}].
usagestring–Optional. Trip-wide data usage for stops that do not set their own: "light" (about 300 MB a day), "regular" (about 800 MB a day) or "heavy" (about 2 GB a day). Defaults to "regular".
NameTypeReqDescription
checkoutobjectyesHow to act on the recommendation.
contractstringyesVersion of this answer's shape. "1" today; it only changes when an existing field changes meaning.
currencystringyesISO 4217 code every amount below is quoted in, e.g. "EUR".
optionsarrayyesEvery way of buying the trip that we could price, cheapest-first within each strategy. Empty when nothing we sell covers it.
planner_urlstringyesThe same trip on the SimFuse website, for a person who wants to finish it themselves.
reasonstringyesOne sentence explaining the recommendation, written to be quoted to the traveller verbatim.
recommendationstring|nullyesWhich strategy won: one plan for the whole route, one plan per country, or a mix. Null when nothing we sell covers the trip.
tripobjectyesThe trip as it was understood, which is worth reading back to the traveller.
warningsarrayyesTrip-level caveats: a country SimFuse does not sell, or a gap the recommended option leaves. Say these out loud rather than dropping them.

No examples provided.

Install

How do I install the SimFuse eSIM Storefront MCP server?

SimFuse eSIM Storefront is a hosted endpoint at https://simfuse.app/agentic/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 · simfuse.app

# add to Claude Code
claude mcp add --transport http app-simfuse-esim-storefront 'https://simfuse.app/agentic/mcp'
Common questions

What is the SimFuse eSIM Storefront MCP server?

SimFuse eSIM Storefront is an MCP server listed in the public MCP registry as app.simfuse/esim-storefront. Travel eSIMs for 200+ countries. Browse plans, price a multi-country trip, and open a checkout. This page covers its hosted endpoint (https://simfuse.app/agentic/mcp).

Is the SimFuse eSIM Storefront MCP server safe to use?

SimFuse eSIM Storefront scores 79 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 SimFuse eSIM Storefront MCP server expose?

SimFuse eSIM Storefront exposes 15 tools: plan-trip, list-destinations, list-regions, get-destination-info, list-plans, and 10 more. Their descriptions and schemas cost roughly 3,734 tokens of context every time the server is loaded.

Does the SimFuse eSIM Storefront MCP server require authentication?

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

Is the SimFuse eSIM Storefront MCP server still maintained?

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

What did VerifyMCP test on the SimFuse eSIM Storefront MCP server?

VerifyMCP ran 13 checks on SimFuse eSIM Storefront, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.