Inbox eSIM
REMOTE · INBOXESIM.COM
Travel eSIMs for 200+ countries: find plans with USD prices and buy one, paid by MPP (Stripe).
Available components
Last scanned (8 hours ago)
Scores higher than 73% of remote servers
Reachable. Last reached 6 Nov 2026.
Category E-commerce
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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
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 →
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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 906 → 1130 ▼ functional
- New tool “compare_esim_prices” functional
- 2 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.
- 31 Oct 26 +1
- 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 security
- 29 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 240 → 180 ▲ functional
- Stability: unverified → 0.03 ▲ functional
- New tool “check_esim_device” functional
- New tool “get_order_status” functional
- New tool “make_esim_cart” functional
- 28 Oct 26 73
First indexed and scored.
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 6 Nov 2026 · Probed https://inboxesim.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=inboxesim.com | CN=WE1,O=Google Trust Services,C=US | 16 Oct 2026 | 14 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 2d7bdc2cb3c700540e0b8407a47c2d41 |
| SANs: inboxesim.com, *.inboxesim.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 inboxesim.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| inboxesim.com. | DS published | 2371 | 13 | Verified |
| inboxesim.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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://static.cloudflareinsights.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https:; font-src 'self'; connect-src 'self' https://cloudflareinsights.com; object-src 'none'; frame-ancestors 'self'; base-uri 'self'; form-action 'self' https://checkout.stripe.com; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://inboxesim.com/mcp | Verified | 200 | |
| http (plaintext) | http://inboxesim.com/mcp | HTTPS enforced | 301 | https://inboxesim.com/mcp |
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 →
buy_esim Buy a travel eSIM ~227
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).
| Name | Type | Req | Description |
|---|---|---|---|
| customer_agreed_to_terms | boolean | yes | true only if the customer accepted the terms quoted in this tool's description. |
| customer_email | string | yes | Where the QR code and install link are sent. |
| plan_id | string | yes | A plan_id from find_esim_plans, e.g. 'japan-5gb-30d'. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| status | string | yes | – |
No examples provided.
check_esim_device Check a phone for eSIM ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | yes | The phone or tablet model, e.g. 'iPhone 13', 'Galaxy S23', 'Pixel 7a'. |
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | yes | – |
| how_to_check | string | yes | – |
| reason | string | yes | – |
| verdict | string | yes | – |
No examples provided.
compare_esim_prices Compare eSIM prices across brands ~197
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.
| Name | Type | Req | Description |
|---|---|---|---|
| data_gb | number | – | Optional: at least this much data. Default 5. |
| destination | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| asked | object | – | – |
| brands_read | integer | – | – |
| brands_with_a_match | integer | – | – |
| comparison_page | string | yes | – |
| destination | string | yes | – |
| note | string | yes | – |
| plans | array | yes | – |
No examples provided.
find_esim_plans Find travel eSIM plans ~137
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.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | 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). |
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | – | – |
| plans | array | yes | – |
No examples provided.
get_order_status Get an eSIM order's status ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_email | string | yes | The email the order was bought with. |
| order_id | string | yes | The order number, e.g. 'ISJPAH2PXG2C' (in the paid response and the email). |
| Name | Type | Req | Description |
|---|---|---|---|
| data_total_gb | number | – | – |
| data_used_gb | number | – | – |
| note | string | – | – |
| order_id | string | yes | – |
| order_url | string | yes | – |
| place | string | yes | – |
| plan | string | yes | – |
| status | string | yes | – |
| top_up_of | string | – | – |
| valid_until | string | – | – |
No examples provided.
make_esim_cart One payment for several eSIMs ~149
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.
| Name | Type | Req | Description |
|---|---|---|---|
| plan_ids | array | yes | plan_ids from find_esim_plans, one per eSIM, e.g. ['japan-5gb-30d', 'south-korea-3gb-30d']. |
| Name | Type | Req | Description |
|---|---|---|---|
| cart_url | string | yes | Give this link to the customer: they pay for every eSIM in it at once. |
| note | string | – | – |
| plans | array | yes | – |
| total_usd | string | yes | 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. |
No examples provided.
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.
remote · inboxesim.com
claude mcp add --transport http com-inboxesim-esim 'https://inboxesim.com/mcp'
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.