worldwide eSIM — one eSIM for the whole world
REMOTE · WORLDWIDEESIM.COM
One travel eSIM for 98 countries: live quotes by continent and GB, country check and a buy link.
Available components
Last scanned (15 hours ago)
Scores higher than 69% of remote servers
Reachable. Last reached 5 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 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 (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3170 tokens (~317/item across 10 items; 7 tools + 3 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 Management27
- Stability observed for 8 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 (29% 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 5 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.
- 4 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 3 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.
- 1 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.
- 31 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_shop_facts” rewrote its description, which is the text the model reads security
- Tool “quote_esim” rewrote its description, which is the text the model reads security
- 30 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “start_checkout” rewrote its description, which is the text the model reads security
- 29 Oct 26 0
- Stability: unverified → 0.03 ▲ 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 5 Nov 2026 · Probed https://worldwideesim.com/wp-json/worldwideesim/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=worldwideesim.com | CN=WE1,O=Google Trust Services,C=US | 12 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | da6356f1c832b8530e0577c3270aa2bf |
| SANs: worldwideesim.com, *.worldwideesim.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 worldwideesim.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| worldwideesim.com. | DS published | 2371 | 13 | Verified |
| worldwideesim.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; preload |
| content-security-policy | default-src 'none'; base-uri 'self'; object-src 'none'; frame-ancestors 'self'; form-action 'self' https://www.paypal.com https://hooks.stripe.com; script-src 'self' 'unsafe-inline' https://js.stripe.com https://m.stripe.network https://*.stripe.com https://*.googletagmanager.com https://*.google-analytics.com https://analytics.google.com https://region1.analytics.google.com https://*.doubleclick.net https://*.googleadservices.com https://www.gstatic.com https://apis.google.com https://pay.google.com https://static.cloudflareinsights.com https://challenges.cloudflare.com; script-src-elem 'self' 'unsafe-inline' https://js.stripe.com https://m.stripe.network https://*.stripe.com https://*.googletagmanager.com https://*.google-analytics.com https://analytics.google.com https://region1.analytics.google.com https://*.doubleclick.net https://*.googleadservices.com https://www.gstatic.com https://apis.google.com https://pay.google.com https://static.cloudflareinsights.com https://challenges.cloudflare.com; style-src |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), camera=(), microphone=(), payment=(self "https://js.stripe.com") |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://worldwideesim.com/wp-json/worldwideesim/mcp | Verified | 200 | |
| http (plaintext) | http://worldwideesim.com/wp-json/worldwideesim/mcp | HTTPS enforced | 301 | https://worldwideesim.com/wp-json/worldwideesim/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 →
check_country Is a country included? ~259
Is one country included? Pass its name in any language or its ISO-2 code (map a city to its country first). Returns included true/false, the continent, the mobile networks (operator names + 5G flag) and the cheapest coverage choice that includes it (its continent alone) with the server price and buy_url, plus the whole world at the same size for comparison.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | – | Optional language-region bucket the customer shops in, e.g. en-gb, de-de (sets currency and link locale). Defaults from language. |
| country | string | yes | Country in ANY language or its ISO code, e.g. "Japan", "Japon", "jp". |
| currency | string | – | Optional ISO 4217 override for prices. |
| gb | integer | – | The data pool in GB, ONE pool for every included country: 3, 5, 10 (more: 20, 30, 50, 100). Omit = 3 GB. Not sure? Call recommend_config. |
| language | string | – | ISO language of the conversation, e.g. en, de, ja. Localizes country and continent names and sets the language/currency of links and prices. |
No output schema declared.
No examples provided.
get_shop_facts Shop facts ~170
What worldwide eSIM is and how it works, in the shop’s own words: one mobile-data eSIM for the whole world or chosen continents, one data pool, validity (until the data is used up, up to 90 days from the first connection), recharge, delivery, installation, devices, payment, refunds, My eSIM, e-mails, support. Use for any question that is not a price or a country.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | – | Optional language-region bucket the customer shops in, e.g. en-gb, de-de (sets currency and link locale). Defaults from language. |
| language | string | – | ISO language of the conversation, e.g. en, de, ja. Localizes country and continent names and sets the language/currency of links and prices. |
No output schema declared.
No examples provided.
list_coverage List coverage ~229
The five continents with their number of countries and the starting price of each (the smallest data size for that continent alone) plus the whole world. Pass continent to list its countries (continent "world" lists every country); include_networks adds the operator names and a 5G flag per country. Use to show where the eSIM works.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | – | Optional language-region bucket the customer shops in, e.g. en-gb, de-de (sets currency and link locale). Defaults from language. |
| continent | string | – | Optional: list the countries of this continent (eu, as, am, af, oc) or of the whole world ("world"). |
| currency | string | – | Optional ISO 4217 override for prices. |
| include_networks | boolean | – | Optional: with continent, add the mobile networks (operator name + 5G flag) of each country. |
| language | string | – | ISO language of the conversation, e.g. en, de, ja. Localizes country and continent names and sets the language/currency of links and prices. |
No output schema declared.
No examples provided.
price_grid Price grid ~286
Every data size (or the sizes asked for) for one coverage choice in one call, each with the server price and its own buy_url; with compare_continents also the whole world against each single continent — to show what a smaller coverage saves. Same server prices as quote_esim.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | – | Optional language-region bucket the customer shops in, e.g. en-gb, de-de (sets currency and link locale). Defaults from language. |
| compare_continents | boolean | – | Optional: also price the whole world and each continent alone. |
| continents | array | – | Continents to cover: eu (Europe), as (Asia & Middle East), am (Americas), af (Africa), oc (Oceania). Omit = the whole world (all five). Fewer continents can lower the price. A country is not a contin… |
| currency | string | – | Optional ISO 4217 override for prices. |
| gb | array | – | Optional: the sizes to price. Omit = every size (3, 5, 10, 20, 30, 50, 100). |
| language | string | – | ISO language of the conversation, e.g. en, de, ja. Localizes country and continent names and sets the language/currency of links and prices. |
No output schema declared.
No examples provided.
quote_esim Quote the eSIM ~332
Use while the customer is still deciding — "how much is …?": the exact server price of ONE worldwide eSIM for the chosen continents (default: the whole world) and data size — the amount the customer would pay — with the number of countries, the validity (until the data is used up, up to 90 days), hotspot, the recharge options and prices, and a buy_url for reference. Quote the price as returned; never compute or scale it. When the customer says they want to buy, call start_checkout.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | – | Optional language-region bucket the customer shops in, e.g. en-gb, de-de (sets currency and link locale). Defaults from language. |
| continents | array | – | Continents to cover: eu (Europe), as (Asia & Middle East), am (Americas), af (Africa), oc (Oceania). Omit = the whole world (all five). Fewer continents can lower the price. A country is not a contin… |
| currency | string | – | Optional ISO 4217 override for prices. |
| gb | integer | – | The data pool in GB, ONE pool for every included country: 3, 5, 10 (more: 20, 30, 50, 100). Omit = 3 GB. Not sure? Call recommend_config. |
| language | string | – | ISO language of the conversation, e.g. en, de, ja. Localizes country and continent names and sets the language/currency of links and prices. |
| Name | Type | Req | Description |
|---|---|---|---|
| buy_url | string | – | The shop page preset to exactly this choice. Use verbatim. |
| continents_unmatched | array | – | Requested values that are not a continent (left out of the quote). |
| countries | integer | – | Number of countries included. |
| coverage | object | – | The chosen continents. |
| coverage_url | string | – | Every included country and network by continent. |
| currency | string | – | – |
| data_gb | integer | – | ONE data pool for every included country (not per day, not per country). |
| data_only | boolean | – | true: no phone number, no SMS. |
| hotspot | boolean | – | – |
| note | string | – | Present when something about the request had to be adjusted — read it to the customer. |
| price | number | – | FULL price of exactly this choice in currency — the amount paid. Not per GB, per day or per country. |
| price_basis | string | – | – |
| price_is_final | boolean | – | – |
| topup | object | – | How the customer recharges later (+1, +3 or +10 GB, renews the validity), with the server recharge prices for this coverage when available. |
| valid_days_max | integer | – | – |
| validity | string | – | "until the data is used up, up to 90 days" — say it this way. |
| validity_starts | string | – | The days start at the first connection to a network, not at purchase or installation. |
No examples provided.
recommend_config Recommend for a trip ~396
Use when the customer names the countries of a trip instead of continents and a size: returns the smallest set of continents that covers every named country (countries that are not included come back in not_covered), a suggested data size from the days and usage (light ≈ 0.5 GB/day, normal ≈ 1.5, heavy ≈ 4; rounded up to the next size) and server quotes for that size and one size down and up, each with its buy_url, plus the whole world at the suggested size. Same prices as quote_esim.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | – | Optional language-region bucket the customer shops in, e.g. en-gb, de-de (sets currency and link locale). Defaults from language. |
| budget | number | – | Optional budget in the quoted currency; options above it are marked. |
| countries | array | yes | The countries of the trip, names in any language or ISO-2 codes, e.g. ["Japan", "Thailand", "Australia"]. Map cities to their countries first. |
| currency | string | – | Optional ISO 4217 override for prices. |
| days | integer | – | Optional: days the customer will use mobile data. Without days the size follows the usage alone (light 3 / normal 5 / heavy 10 GB). |
| gb_per_day | number | – | Optional: the customer's own estimate in GB per day (wins over usage). |
| language | string | – | ISO language of the conversation, e.g. en, de, ja. Localizes country and continent names and sets the language/currency of links and prices. |
| usage | string | – | light ≈ 0.5 GB/day (messaging, maps, mail), normal ≈ 1.5 GB/day (default; social media, music, some video), heavy ≈ 4 GB/day (video streaming, video calls, hotspot for a laptop). |
No output schema declared.
No examples provided.
start_checkout Start secure checkout ~372
Use only once the customer has decided to buy ("I'll take it", "how do I buy?"): the checkout handoff for one choice (same input as quote_esim). Returns the buy_url to give the customer, the final price and a ready-to-send checkout block (next_step, payment_methods, delivery) — the shop page opens preset to exactly this coverage and size; the customer presses the buy button (buy_button in the result, e.g. "Get your eSIM" in English) and pays securely. No account needed; the eSIM is delivered on screen and by e-mail right after payment. No in-chat order tracking, no discount codes. For prices while the customer is still comparing, use quote_esim.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | – | Optional language-region bucket the customer shops in, e.g. en-gb, de-de (sets currency and link locale). Defaults from language. |
| continents | array | – | Continents to cover: eu (Europe), as (Asia & Middle East), am (Americas), af (Africa), oc (Oceania). Omit = the whole world (all five). Fewer continents can lower the price. A country is not a contin… |
| currency | string | – | Optional ISO 4217 override for prices. |
| gb | integer | – | The data pool in GB, ONE pool for every included country: 3, 5, 10 (more: 20, 30, 50, 100). Omit = 3 GB. Not sure? Call recommend_config. |
| language | string | – | ISO language of the conversation, e.g. en, de, ja. Localizes country and continent names and sets the language/currency of links and prices. |
| Name | Type | Req | Description |
|---|---|---|---|
| buy_button | string | – | The label of the buy button on the page, in the language of the customer: name it exactly so. |
| buy_url | string | yes | The shop page preset to exactly this choice. Use verbatim. |
| continents_unmatched | array | – | Requested values that are not a continent (left out of the quote). |
| countries | integer | – | Number of countries included. |
| coverage | object | – | The chosen continents. |
| coverage_url | string | – | Every included country and network by continent. |
| currency | string | yes | – |
| data_gb | integer | – | ONE data pool for every included country (not per day, not per country). |
| data_only | boolean | – | true: no phone number, no SMS. |
| delivery | string | – | How and when the eSIM arrives. |
| hotspot | boolean | – | – |
| message | string | – | A ready-to-send line for the customer. |
| next_step | string | yes | What the customer does now: open buy_url, press "Get your eSIM", pay. |
| note | string | – | Present when something about the request had to be adjusted — read it to the customer. |
| payment_methods | array | – | – |
| price | number | yes | FULL price of exactly this choice in currency — the amount paid. Not per GB, per day or per country. |
| price_basis | string | – | – |
| price_is_final | boolean | – | – |
| topup | object | – | How the customer recharges later (+1, +3 or +10 GB, renews the validity), with the server recharge prices for this coverage when available. |
| valid_days_max | integer | – | – |
| validity | string | – | "until the data is used up, up to 90 days" — say it this way. |
| validity_starts | string | – | The days start at the first connection to a network, not at purchase or installation. |
No examples provided.
How do I install the worldwide eSIM — one eSIM for the whole world MCP server?
worldwide eSIM — one eSIM for the whole world is a hosted endpoint at https://worldwideesim.com/wp-json/worldwideesim/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 · worldwideesim.com
claude mcp add --transport http com-worldwideesim-esim-catalog 'https://worldwideesim.com/wp-json/worldwideesim/mcp'
What is the worldwide eSIM — one eSIM for the whole world MCP server?
worldwide eSIM — one eSIM for the whole world is an MCP server listed in the public MCP registry as com.worldwideesim/esim-catalog. One travel eSIM for 98 countries: live quotes by continent and GB, country check and a buy link. This page covers its hosted endpoint (https://worldwideesim.com/wp-json/worldwideesim/mcp).
Is the worldwide eSIM — one eSIM for the whole world MCP server safe to use?
worldwide eSIM — one eSIM for the whole world scores 77 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 worldwide eSIM — one eSIM for the whole world MCP server expose?
worldwide eSIM — one eSIM for the whole world exposes 7 tools: get_shop_facts, list_coverage, check_country, quote_esim, price_grid, and 2 more. Their descriptions and schemas cost roughly 2,044 tokens of context every time the server is loaded.
Does the worldwide eSIM — one eSIM for the whole world MCP server require authentication?
No. We connected to worldwide eSIM — one eSIM for the whole world without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the worldwide eSIM — one eSIM for the whole world MCP server still maintained?
worldwide eSIM — one eSIM for the whole world is still listed as active in the MCP registry. We last reached this channel on 5 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 worldwide eSIM — one eSIM for the whole world MCP server?
VerifyMCP ran 13 checks on worldwide eSIM — one eSIM for the whole world, 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.