# Inbox eSIM (remote · inboxesim.com)

Travel eSIMs for 200+ countries: find plans with USD prices and buy one, paid by MPP (Stripe).

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

## Components

- remote · `inboxesim.com`: 78/100 (this document), [markdown](https://verifymcp.io/servers/com-inboxesim-esim/inboxesim.md), [page](https://verifymcp.io/servers/com-inboxesim-esim/inboxesim)

## Channel facts

- Endpoint: `https://inboxesim.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

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

- **Endpoint Security**: 83/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 is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1130 tokens (~188/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Inbox eSIM MCP server?

Inbox eSIM is a hosted endpoint at https://inboxesim.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.

### Claude

```bash
claude mcp add --transport http com-inboxesim-esim 'https://inboxesim.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-inboxesim-esim": {
      "url": "https://inboxesim.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-inboxesim-esim": {
      "type": "http",
      "url": "https://inboxesim.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-inboxesim-esim]
url = "https://inboxesim.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-inboxesim-esim --url 'https://inboxesim.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-inboxesim-esim:
    url: "https://inboxesim.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-inboxesim-esim": {
      "Transport": "http",
      "Url": "https://inboxesim.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-inboxesim-esim -t streamable-http -u 'https://inboxesim.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-inboxesim-esim": {
      "type": "http",
      "url": "https://inboxesim.com/mcp"
    }
  }
}
```

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-06 (score 78, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-05 (score 78, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 906 → 1130
- [functional] New tool “compare_esim_prices”

### 2026-11-02 (score 77, +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-10-31 (score 76, +1)

- [security] Tool “buy_esim” rewrote its description, which is the text the model reads
- [security] Tool “make_esim_cart” rewrote its description, which is the text the model reads

### 2026-10-29 (score 75, +2)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional improvement] Schema quality: 240 → 180
- [functional improvement] Stability: unverified → 0.03
- [functional] New tool “check_esim_device”
- [functional] New tool “get_order_status”
- [functional] New tool “make_esim_cart”

### 2026-10-28 (score 73)

First indexed and scored.

## MCP tools (6)

### `find_esim_plans` (~137 tokens)

Find travel eSIM plans

Lists Inbox eSIM data plans for a destination (country, city, region such as Europe, or 'global'), cheapest first, with plan_id, data in GB, validity in days and price in USD. Data only, no phone number; works on unlocked eSIM phones.

Input parameters:

- `destination` (string, required): Where the customer travels, e.g. 'Japan', 'USA', 'Europe', 'Bangkok'.
- `min_data_gb` (number): Optional: only plans with at least this much data.
- `min_days` (integer): Optional: only plans valid for at least this many days (the trip length).

Output parameters:

- `note` (string)
- `plans` (array)

### `compare_esim_prices` (~197 tokens)

Compare eSIM prices across brands

Compares travel eSIM prices for one country across every brand Inbox eSIM reads (about 50), cheapest first, for a size and a trip length. Read only. Each brand's cheapest plan that covers the request, with its price, the date that price was read, whether it needs an app or account, and its page. Inbox eSIM runs the comparison and also sells eSIMs: its row is marked is_ours and keeps its real position, because the order is by price only.

Input parameters:

- `data_gb` (number): Optional: at least this much data. Default 5.
- `destination` (string, required): One country, e.g. 'Japan', 'USA', 'Bangkok'.
- `min_days` (integer): Optional: valid for at least this many days. Default 30 (7 for unlimited).
- `unlimited` (boolean): Optional: unlimited or daily plans instead of a data size.

Output parameters:

- `asked` (object)
- `brands_read` (integer)
- `brands_with_a_match` (integer)
- `comparison_page` (string)
- `destination` (string)
- `note` (string)
- `plans` (array)

### `buy_esim` (~227 tokens)

Buy a travel eSIM

Starts the purchase of one eSIM plan for the customer and returns a payment link. Pay it with the Machine Payments Protocol (HTTP 402, Stripe shared payment token) to complete the order. Before calling, confirm the plan, the price and the email with the customer, and get their agreement to the terms: By buying, the customer asks for the eSIM to be sent at once and accepts the terms (https://inboxesim.com/terms): the 14-day right to withdraw ends once the eSIM is installed. An eSIM that was never installed or used can be refunded within 30 days from its order page, less the payment fee (no card fee within 14 days in the EU and UK).

Input parameters:

- `customer_agreed_to_terms` (boolean, required): true only if the customer accepted the terms quoted in this tool's description.
- `customer_email` (string, required): Where the QR code and install link are sent.
- `plan_id` (string, required): A plan_id from find_esim_plans, e.g. 'japan-5gb-30d'.

Output parameters:

- `amount_usd` (string)
- `browser_fallback` (string)
- `how_to_pay` (string)
- `message` (string)
- `page_url` (string)
- `payment_link` (string): POST here and answer the HTTP 402 challenge.
- `plan` (object)
- `status` (string)

### `make_esim_cart` (~149 tokens)

One payment for several eSIMs

For a trip to several countries (or several phones): turns 2 to 6 plan_ids from find_esim_plans into one cart link. The customer opens it, checks the eSIMs and pays once on Stripe; each eSIM comes in its own QR email and can be refunded on its own if never installed. 3 or more eSIMs in one cart are 5% off. Nothing is bought until the customer pays on the page.

Input parameters:

- `plan_ids` (array, required): plan_ids from find_esim_plans, one per eSIM, e.g. ['japan-5gb-30d', 'south-korea-3gb-30d'].

Output parameters:

- `cart_url` (string): Give this link to the customer: they pay for every eSIM in it at once.
- `note` (string)
- `plans` (array)
- `total_usd` (string): What the cart page charges, with the 5% off that 3+ eSIMs get on most plans. A partner code may lower it on the page.

### `check_esim_device` (~88 tokens)

Check a phone for eSIM

Says whether a phone model is likely to take an eSIM (likely, unlikely or check), from the model name, with how to be sure on the phone itself. Call it before buy_esim when the customer is unsure.

Input parameters:

- `device` (string, required): The phone or tablet model, e.g. 'iPhone 13', 'Galaxy S23', 'Pixel 7a'.

Output parameters:

- `device` (string)
- `how_to_check` (string)
- `reason` (string)
- `verdict` (string)

### `get_order_status` (~114 tokens)

Get an eSIM order's status

Where an Inbox eSIM order is (awaiting_payment, preparing, ready_to_install, installed, in_use, ended, refunded, cancelled, with_support), with data used, the end date and the order page. Needs the order number and the email it was bought with.

Input parameters:

- `customer_email` (string, required): The email the order was bought with.
- `order_id` (string, required): The order number, e.g. 'ISJPAH2PXG2C' (in the paid response and the email).

Output parameters:

- `data_total_gb` (number)
- `data_used_gb` (number)
- `note` (string)
- `order_id` (string)
- `order_url` (string)
- `place` (string)
- `plan` (string)
- `status` (string)
- `top_up_of` (string)
- `valid_until` (string)

## Diagnostics

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

## Score history

- 2026-11-06: 78
- 2026-11-05: 78
- 2026-11-04: 77
- 2026-11-03: 77
- 2026-11-02: 77
- 2026-11-01: 76
- 2026-10-31: 76
- 2026-10-30: 75
- 2026-10-29: 75
- 2026-10-28: 73

## Common questions

### What is the Inbox eSIM MCP server?

Inbox eSIM is an MCP server listed in the public MCP registry as com.inboxesim/esim. Travel eSIMs for 200+ countries: find plans with USD prices and buy one, paid by MPP (Stripe). This page covers its hosted endpoint (https://inboxesim.com/mcp).

### Is the Inbox eSIM MCP server safe to use?

Inbox eSIM scores 78 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 Inbox eSIM MCP server expose?

Inbox eSIM exposes 6 tools: find_esim_plans, compare_esim_prices, buy_esim, make_esim_cart, check_esim_device, get_order_status. Their descriptions and schemas cost roughly 912 tokens of context every time the server is loaded.

### Does the Inbox eSIM MCP server require authentication?

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

### Is the Inbox eSIM MCP server still maintained?

Inbox eSIM is still listed as active in the MCP registry. We last reached this channel on 6 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 Inbox eSIM MCP server?

VerifyMCP ran 13 checks on Inbox eSIM, 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.

## Links

- Remote endpoint: https://inboxesim.com/mcp
- Website: https://inboxesim.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-inboxesim-esim/inboxesim.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-inboxesim-esim/inboxesim/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-inboxesim-esim/inboxesim.json
- HTML version of this page: https://verifymcp.io/servers/com-inboxesim-esim/inboxesim