# Simvito eSIM (remote · mcp.simvito.com)

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

- Trust score: 74/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.simvito.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-simvito-esim/mcp.md), [page](https://verifymcp.io/servers/com-simvito-esim/mcp)
- npm · `simvito-mcp`: 38/100, [markdown](https://verifymcp.io/servers/com-simvito-esim/simvito-mcp.md), [page](https://verifymcp.io/servers/com-simvito-esim/simvito-mcp)

## Channel facts

- Endpoint: `https://mcp.simvito.com/mcp?src=registry`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.4`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 98% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## 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.

### Claude

```bash
claude mcp add --transport http com-simvito-esim 'https://mcp.simvito.com/mcp?src=registry'
```

### Cursor

```json
{
  "mcpServers": {
    "com-simvito-esim": {
      "url": "https://mcp.simvito.com/mcp?src=registry"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-simvito-esim": {
      "type": "http",
      "url": "https://mcp.simvito.com/mcp?src=registry"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-simvito-esim]
url = "https://mcp.simvito.com/mcp?src=registry"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-simvito-esim": {
      "type": "remote",
      "url": "https://mcp.simvito.com/mcp?src=registry",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-simvito-esim --url 'https://mcp.simvito.com/mcp?src=registry' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-simvito-esim:
    url: "https://mcp.simvito.com/mcp?src=registry"
```

### Netclaw

```json
{
  "McpServers": {
    "com-simvito-esim": {
      "Transport": "http",
      "Url": "https://mcp.simvito.com/mcp?src=registry"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-simvito-esim -t streamable-http -u 'https://mcp.simvito.com/mcp?src=registry'
```

### Other

```json
{
  "mcpServers": {
    "com-simvito-esim": {
      "type": "http",
      "url": "https://mcp.simvito.com/mcp?src=registry"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 74, +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.

### 2026-11-19 (score 73, +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.

### 2026-11-17 (score 72, +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.

### 2026-11-15 (score 71, +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.

### 2026-11-13 (score 70, +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.

### 2026-11-10 (score 69, +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.

### 2026-11-09 (score 68, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-08 (score 68)

First indexed and scored.

## MCP tools (10)

### `find_destination` (~150 tokens)

Find a destination

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.

Input parameters:

- `locale` (string): Language of the conversation, as a simvito.com language code ('en', 'ja', 'zh-CN', 'es'…); names and links follow it. Defaults to 'en'.
- `query` (string, required): Country, territory or region name, e.g. 'Japan', '日本', 'JP', 'Europe'

Output parameters:

- `destinations` (array)
- `multi_country` (array)
- `note` (string)
- `regions` (array)

### `search_plans` (~324 tokens)

Search eSIM plans

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.

Input parameters:

- `currency` (string): 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` (number): Total data needed for the whole trip in GB; omit if unsure
- `days` (integer, required): Trip length in days
- `destination` (string, required): Destination slug from find_destination (e.g. 'japan', 'europe-33'), an ISO country code, or a country name in any language.
- `locale` (string): Language of the conversation, as a simvito.com language code ('en', 'ja', 'zh-CN', 'es'…); names and links follow it. Defaults to 'en'.
- `plan_type` (string): total = one data allowance for the trip; daily = allowance renews each day; unlimited. Defaults to any.

Output parameters:

- `destination` (object)
- `more_plans_url` (string)
- `note` (string)
- `plans` (array)
- `trip_days` (number)

### `compare_networks` (~273 tokens)

Compare networks

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.

Input parameters:

- `country` (string): Only for multi-country destinations: one covered country (name or ISO code)
- `currency` (string): 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.
- `destination` (string, required): Destination slug from find_destination (e.g. 'japan', 'europe-33'), an ISO country code, or a country name in any language.
- `locale` (string): Language of the conversation, as a simvito.com language code ('en', 'ja', 'zh-CN', 'es'…); names and links follow it. Defaults to 'en'.

Output parameters:

- `countries` (array)
- `destination` (object)
- `note` (string)
- `operators` (array)
- `url` (string)

### `plan_trip` (~221 tokens)

Plan a multi-country trip

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.

Input parameters:

- `currency` (string): 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_day` (number): Expected data use per day in GB; defaults to 1
- `locale` (string): Language of the conversation, as a simvito.com language code ('en', 'ja', 'zh-CN', 'es'…); names and links follow it. Defaults to 'en'.
- `stops` (array, required)

Output parameters:

- `data_gb_per_day` (number)
- `data_gb_total` (number)
- `note` (string)
- `one_plan`
- `one_plan_costs_more`
- `other_regional_plans` (array)
- `savings_with_one_plan`
- `separate_plans` (object)
- `total_days` (number)

### `check_device` (~194 tokens)

Check phone eSIM support

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.

Input parameters:

- `locale` (string): Language of the conversation, as a simvito.com language code ('en', 'ja', 'zh-CN', 'es'…); names and links follow it. Defaults to 'en'.
- `model` (string, required): Phone model, e.g. 'iPhone 13', 'Pixel 8', 'Galaxy S23'
- `purchase_region` (string): ISO code of the country/region where the phone was bought, e.g. 'CN', 'HK', 'US'

Output parameters:

- `app` (object)
- `basis` (string|null)
- `brand` (string|null)
- `checked_on` (string)
- `devices_page` (string)
- `exceptions` (array)
- `matches` (array)
- `not_if_bought_in` (array)
- `query` (string)
- `region_exception` (array)
- `sources` (array)
- `status` (string)
- `verdict` (string)
- `verdict_note` (string)

### `get_buy_link` (~288 tokens)

Get a purchase link

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.

Input parameters:

- `currency` (string): 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.
- `destination` (string): Destination slug from find_destination (e.g. 'japan', 'europe-33'), an ISO country code, or a country name in any language.
- `locale` (string): Language of the conversation, as a simvito.com language code ('en', 'ja', 'zh-CN', 'es'…); names and links follow it. Defaults to 'en'.
- `plan_id` (string, required): plan_id returned by search_plans or plan_trip
- `quantity` (integer): Number of eSIMs (one per traveller). Defaults to 1.
- `trip_days` (integer): Trip length in days, if known

Output parameters:

- `buy_url` (string)
- `code_included`
- `destination` (string)
- `note` (string)
- `payment_methods` (array)
- `plan` (object)
- `plan_url` (string)
- `quantity` (number)
- `total` (object)

### `list_my_esims` (~116 tokens)

List my eSIMs

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.

Input parameters:

- `locale` (string): Language of the conversation, as a simvito.com language code ('en', 'ja', 'zh-CN', 'es'…); names and links follow it. Defaults to 'en'.

Output parameters:

- `account_url` (string)
- `app` (object)
- `esims` (array)
- `note` (string)

### `get_checkout_options` (~224 tokens)

Checkout options: languages, currencies, payment methods

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).

Input parameters:

- `country` (string): Buyer's country or region (ISO 3166-1 alpha-2, e.g. 'JP', 'DE')
- `currency` (string): 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.
- `language` (string): Language of the conversation, as a simvito.com language code ('en', 'ja', 'zh-CN', 'es'…); names and links follow it. Defaults to 'en'.

Output parameters:

- `currencies` (array)
- `currency` (string)
- `default_currency` (string)
- `languages` (array)
- `local_methods_by_country` (object)
- `note` (string)
- `payment_methods`

### `start_checkout` (~456 tokens)

Get payment links

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.

Input parameters:

- `confirmations` (array): Codes from a previous confirmation_required result that the user explicitly agreed to after seeing each text. Never fill these in for the user.
- `currency` (string): 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.
- `destination` (string): The destination search_plans returned with the plan(s); can also be given on each item.
- `device` (string): Where the user will open the payment link, if you know: 'phone' or 'computer'
- `expected_unit_amount` (number): With plan_id, only after price_changed: the new unit price the user accepted. Otherwise omit; the quoted price is used.
- `items` (array): The plans to buy, each with its quantity.
- `locale` (string): Language of the conversation, as a simvito.com language code ('en', 'ja', 'zh-CN', 'es'…); names and links follow it. Defaults to 'en'.
- `plan_id` (string): Shorthand for a single plan: plan_id returned by search_plans or plan_trip (instead of items)
- `quantity` (integer): With plan_id: number of eSIMs (one per traveller). Defaults to 1.

Output parameters:

- `checkout_id` (string)
- `coupon`
- `expires_at` (string|null)
- `items` (array)
- `links` (object)
- `list_total`
- `note` (string)
- `policies` (object)
- `price_changes` (array)
- `quantity` (number)
- `required` (array)
- `status` (string)
- `total` (object)

### `get_order_status` (~143 tokens)

Check an order

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.

Input parameters:

- `checkout_id` (string, required): checkout_id returned by start_checkout
- `locale` (string): Language of the conversation, as a simvito.com language code ('en', 'ja', 'zh-CN', 'es'…); names and links follow it. Defaults to 'en'.

Output parameters:

- `account_url` (string)
- `app` (object)
- `checkout_id` (string)
- `duplicate_payment`
- `esims` (array)
- `note` (string)
- `order_display_id` (number|null)
- `order_url` (string)
- `status` (string)
- `still_waiting` (boolean)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-simvito-esim/mcp#diagnostics

## Score history

- 2026-11-21: 74
- 2026-11-20: 73
- 2026-11-19: 73
- 2026-11-18: 72
- 2026-11-17: 72
- 2026-11-16: 71
- 2026-11-15: 71
- 2026-11-14: 70
- 2026-11-13: 70
- 2026-11-12: 69
- 2026-11-11: 69
- 2026-11-10: 69
- 2026-11-09: 68
- 2026-11-08: 68

## 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.

## Links

- Remote endpoint: https://mcp.simvito.com/mcp?src=registry
- Repository: https://github.com/SimvitoTeam/simvito-mcp
- Website: https://simvito.com/ai/
- Changelog RSS feed: https://verifymcp.io/servers/com-simvito-esim/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-simvito-esim/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-simvito-esim/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-simvito-esim/mcp
