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.

Simvito eSIM

REMOTE · MCP.SIMVITO.COM · 2 COMPONENTS

Compare travel eSIM plans and each local network (4G/5G), check phone support, get payment links.

+4 this week 74 Trust /100

Last scanned (13 hours ago)

Scores higher than 61% 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 Security66
  • 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability74
  • 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 3189 tokens (~265/item across 12 items; 10 tools + 2 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 Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 98% of tool parameters carry a description.Partial
  • 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 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
What we tested

Checks we ran (12)

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

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

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.

  • 21 Nov 26 +1

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

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 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 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 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 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 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 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 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.

  • 9 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 8 Nov 26 68

    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://mcp.simvito.com/mcp?src=registry

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=simvito.com CN=WE1,O=Google Trust Services,C=US 7 Nov 2026 5 Feb 2027 ECDSA 256 ECDSA-SHA256 f261ae7e2dac5a1d13205c97c8ea87f6
SANs: simvito.com, mcp.simvito.com, *.mcp.simvito.com
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 mcp.simvito.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
simvito.com. DS published 2371 13 Verified
mcp.simvito.com. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.simvito.com/mcp?src=registry Verified 200
http (plaintext) http://mcp.simvito.com/mcp?src=registry Inconclusive 405
MCP tools · 10 exposed · ~2,389 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_device ~194

Check whether a phone supports eSIM, e.g. 'does my iPhone 13 support eSIM?'. Covers iPhone, Google Pixel and Samsung Galaxy from the manufacturers' official lists, including the exceptions for phones bought in mainland China, Hong Kong or Macao. Gives a verdict (supports_esim / no_esim); pass purchase_region when the user says where the phone was bought.

NameTypeReqDescription
localestring–Language of the conversation, as a simvito.com language code ('en', 'ja', 'zh-CN', 'es'…); names and links follow it. Defaults to 'en'.
modelstringyesPhone model, e.g. 'iPhone 13', 'Pixel 8', 'Galaxy S23'
purchase_regionstring–ISO code of the country/region where the phone was bought, e.g. 'CN', 'HK', 'US'
NameTypeReqDescription
appobject––
basisstring|nullyes–
brandstring|nullyes–
checked_onstringyes–
devices_pagestringyes–
exceptionsarrayyes–
matchesarrayyes–
not_if_bought_inarrayyes–
querystringyes–
region_exceptionarrayyes–
sourcesarrayyes–
statusstringyes–
verdictstringyes–
verdict_notestringyes–

No examples provided.

compare_networks ~273

Compare the local mobile networks for a destination side by side, for questions like 'which network is best in Thailand' or 'which eSIM has 5G in Tokyo': each operator the plans use, its best generation (4G/5G), how many plans use it and the cheapest one. For a multi-country plan, pass country to see that country's operators.

NameTypeReqDescription
countrystring–Only for multi-country destinations: one covered country (name or ISO code)
currencystring–The user's currency (ISO 4217) for prices: USD, EUR, GBP, HKD, CNY, SGD, JPY, AUD, NZD, CAD, BRL, IDR, MYR, PHP, THB, KRW, PLN, CHF, SEK, TWD, VND, TRY, SAR, AED, ILS. Defaults to USD.
destinationstringyesDestination slug from find_destination (e.g. 'japan', 'europe-33'), an ISO country code, or a country name in any language.
localestring–Language of the conversation, as a simvito.com language code ('en', 'ja', 'zh-CN', 'es'…); names and links follow it. Defaults to 'en'.
NameTypeReqDescription
countriesarrayyes–
destinationobjectyes–
notestringyes–
operatorsarrayyes–
urlstringyes–

No examples provided.

find_destination ~150

Find where a trip goes: a country, a region such as 'Europe' or 'Asia', or a multi-country plan, by name in any language, ISO code or misspelling (many cities and islands such as 'Tokyo' or 'Bali' work too). Returns destination slugs for the other tools; no prices.

NameTypeReqDescription
localestring–Language of the conversation, as a simvito.com language code ('en', 'ja', 'zh-CN', 'es'…); names and links follow it. Defaults to 'en'.
querystringyesCountry, territory or region name, e.g. 'Japan', '日本', 'JP', 'Europe'
NameTypeReqDescription
destinationsarrayyes–
multi_countryarrayyes–
notestring––
regionsarrayyes–

No examples provided.

get_buy_link ~288

Get the simvito.com checkout link for a plan from search_plans or plan_trip, with the price in the user's currency (total for the quantity) and the payment methods for that currency. The user signs in and pays on simvito.com; nothing is charged here.

NameTypeReqDescription
currencystring–The user's currency (ISO 4217) for prices: USD, EUR, GBP, HKD, CNY, SGD, JPY, AUD, NZD, CAD, BRL, IDR, MYR, PHP, THB, KRW, PLN, CHF, SEK, TWD, VND, TRY, SAR, AED, ILS. Defaults to USD.
destinationstring–Destination slug from find_destination (e.g. 'japan', 'europe-33'), an ISO country code, or a country name in any language.
localestring–Language of the conversation, as a simvito.com language code ('en', 'ja', 'zh-CN', 'es'…); names and links follow it. Defaults to 'en'.
plan_idstringyesplan_id returned by search_plans or plan_trip
quantityinteger–Number of eSIMs (one per traveller). Defaults to 1.
trip_daysinteger–Trip length in days, if known
NameTypeReqDescription
buy_urlstringyes–
code_included–yes–
destinationstringyes–
notestringyes–
payment_methodsarrayyes–
planobjectyes–
plan_urlstringyes–
quantitynumberyes–
totalobjectyes–

No examples provided.

get_checkout_options ~224

Languages, currencies and payment methods at simvito.com checkout. Pass the buyer's country or currency to get the default currency there and the payment methods that currency can be paid with (cards, Apple Pay, Google Pay, PayPal, local wallets and bank payments).

NameTypeReqDescription
countrystring–Buyer's country or region (ISO 3166-1 alpha-2, e.g. 'JP', 'DE')
currencystring–The user's currency (ISO 4217) for prices: USD, EUR, GBP, HKD, CNY, SGD, JPY, AUD, NZD, CAD, BRL, IDR, MYR, PHP, THB, KRW, PLN, CHF, SEK, TWD, VND, TRY, SAR, AED, ILS. Defaults to USD.
languagestring–Language of the conversation, as a simvito.com language code ('en', 'ja', 'zh-CN', 'es'…); names and links follow it. Defaults to 'en'.
NameTypeReqDescription
currenciesarrayyes–
currencystringyes–
default_currencystringyes–
languagesarrayyes–
local_methods_by_countryobject––
notestringyes–
payment_methods–yes–

No examples provided.

get_order_status ~143

After the user pays through start_checkout's links (e.g. they say 'paid' or 'is my eSIM ready?'): shows whether the payment arrived and the eSIM is ready, waiting up to about 25 seconds for it, with the eSIM, a link to install and manage it, and the Simvito app. Never returns installation codes.

NameTypeReqDescription
checkout_idstringyescheckout_id returned by start_checkout
localestring–Language of the conversation, as a simvito.com language code ('en', 'ja', 'zh-CN', 'es'…); names and links follow it. Defaults to 'en'.
NameTypeReqDescription
account_urlstringyes–
appobject––
checkout_idstringyes–
duplicate_payment–yes–
esimsarrayyes–
notestringyes–
order_display_idnumber|nullyes–
order_urlstringyes–
statusstringyes–
still_waitingbooleanyes–

No examples provided.

list_my_esims ~116

List the eSIMs in the user's connected Simvito account: destination, plan, status, whether installed, data left and expiry, with a link to manage each one (install, add data) on simvito.com. Requires connecting a Simvito account. Never returns installation codes.

NameTypeReqDescription
localestring–Language of the conversation, as a simvito.com language code ('en', 'ja', 'zh-CN', 'es'…); names and links follow it. Defaults to 'en'.
NameTypeReqDescription
account_urlstringyes–
appobjectyes–
esimsarrayyes–
notestring––

No examples provided.

plan_trip ~221

For a trip through several countries (e.g. Japan 7 days, then Korea 5 days), compare one regional plan that covers every stop with a separate plan for each country, using the cheapest plans that cover each stop's days at the daily data need.

NameTypeReqDescription
currencystring–The user's currency (ISO 4217) for prices: USD, EUR, GBP, HKD, CNY, SGD, JPY, AUD, NZD, CAD, BRL, IDR, MYR, PHP, THB, KRW, PLN, CHF, SEK, TWD, VND, TRY, SAR, AED, ILS. Defaults to USD.
data_gb_per_daynumber–Expected data use per day in GB; defaults to 1
localestring–Language of the conversation, as a simvito.com language code ('en', 'ja', 'zh-CN', 'es'…); names and links follow it. Defaults to 'en'.
stopsarrayyes–
NameTypeReqDescription
data_gb_per_daynumberyes–
data_gb_totalnumberyes–
notestringyes–
one_plan–yes–
one_plan_costs_more–yes–
other_regional_plansarrayyes–
savings_with_one_plan–yes–
separate_plansobjectyes–
total_daysnumberyes–

No examples provided.

search_plans ~324

Find travel eSIM data plans for one destination and trip length, e.g. 'eSIM for Japan, 7 days' or '10 GB for Thailand'. Up to 5 plans with price in the user's currency, data, validity, the local operators each plan uses with 4G/5G, what happens when the data runs out, hotspot and top-up support, and a link to each plan.

NameTypeReqDescription
currencystring–The user's currency (ISO 4217) for prices: USD, EUR, GBP, HKD, CNY, SGD, JPY, AUD, NZD, CAD, BRL, IDR, MYR, PHP, THB, KRW, PLN, CHF, SEK, TWD, VND, TRY, SAR, AED, ILS. Defaults to USD.
data_gbnumber–Total data needed for the whole trip in GB; omit if unsure
daysintegeryesTrip length in days
destinationstringyesDestination slug from find_destination (e.g. 'japan', 'europe-33'), an ISO country code, or a country name in any language.
localestring–Language of the conversation, as a simvito.com language code ('en', 'ja', 'zh-CN', 'es'…); names and links follow it. Defaults to 'en'.
plan_typestring–total = one data allowance for the trip; daily = allowance renews each day; unlimited. Defaults to any.
NameTypeReqDescription
destinationobjectyes–
more_plans_urlstringyes–
notestringyes–
plansarrayyes–
trip_daysnumberyes–

No examples provided.

start_checkout ~456

When the user decides to buy and their Simvito account is connected: places the order on their account and returns two payment links to give them exactly as returned, a secure payment page for cards, Apple Pay, Google Pay and local wallets, and PayPal (when available for this order), with the total, any discount and an order number. Nothing is charged until the user pays on one of those pages. Pass items for up to 5 different plans from search_plans or plan_trip (up to 10 eSIMs in all), or plan_id and quantity for one plan. If the account isn't connected, use get_buy_link instead.

NameTypeReqDescription
confirmationsarray–Codes from a previous confirmation_required result that the user explicitly agreed to after seeing each text. Never fill these in for the user.
currencystring–The user's currency (ISO 4217) for prices: USD, EUR, GBP, HKD, CNY, SGD, JPY, AUD, NZD, CAD, BRL, IDR, MYR, PHP, THB, KRW, PLN, CHF, SEK, TWD, VND, TRY, SAR, AED, ILS. Defaults to USD.
destinationstring–The destination search_plans returned with the plan(s); can also be given on each item.
devicestring–Where the user will open the payment link, if you know: 'phone' or 'computer'
expected_unit_amountnumber–With plan_id, only after price_changed: the new unit price the user accepted. Otherwise omit; the quoted price is used.
itemsarray–The plans to buy, each with its quantity.
localestring–Language of the conversation, as a simvito.com language code ('en', 'ja', 'zh-CN', 'es'…); names and links follow it. Defaults to 'en'.
plan_idstring–Shorthand for a single plan: plan_id returned by search_plans or plan_trip (instead of items)
quantityinteger–With plan_id: number of eSIMs (one per traveller). Defaults to 1.
NameTypeReqDescription
checkout_idstring––
coupon–––
expires_atstring|null––
itemsarrayyes–
linksobject––
list_total–––
notestringyes–
policiesobject––
price_changesarray––
quantitynumberyes–
requiredarray––
statusstringyes–
totalobject––

No examples provided.

Install

How do I install the Simvito eSIM MCP server?

Simvito eSIM is a hosted endpoint at https://mcp.simvito.com/mcp?src=registry, 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 · mcp.simvito.com

# add to Claude Code
claude mcp add --transport http com-simvito-esim 'https://mcp.simvito.com/mcp?src=registry'
Common questions

What is the Simvito eSIM MCP server?

Simvito eSIM is an MCP server listed in the public MCP registry as com.simvito/esim. Compare travel eSIM plans and each local network (4G/5G), check phone support, get payment links. This page covers its hosted endpoint (https://mcp.simvito.com/mcp?src=registry).

Is the Simvito eSIM MCP server safe to use?

Simvito eSIM 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 Simvito eSIM MCP server expose?

Simvito eSIM exposes 10 tools: find_destination, search_plans, compare_networks, plan_trip, check_device, and 5 more. Their descriptions and schemas cost roughly 2,389 tokens of context every time the server is loaded.

Does the Simvito eSIM MCP server require authentication?

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

Is the Simvito eSIM MCP server still maintained?

Simvito eSIM 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 Simvito eSIM MCP server?

VerifyMCP ran 12 checks on Simvito eSIM, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Simvito eSIM: HTTPS. 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.