variotrip route eSIM configurator
REMOTE · VARIOTRIP.COM
One travel eSIM for up to 8 countries: live quotes by route, GB, days and networks, plus a buy link.
Available components
Last scanned (21 hours ago)
Scores higher than 88% of remote servers
Reachable. Last reached 21 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 (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3051 tokens (~305/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 Management93
- Stability observed for 28 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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_networks” rewrote its description, which is the text the model reads security
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 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 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
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://variotrip.com/wp-json/variotrip/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=variotrip.com | CN=YE2,O=Let's Encrypt,C=US | 18 Oct 2026 | 16 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 50da9c4b5a95c4c140a55554e498618880e |
| SANs: *.variotrip.com, variotrip.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of variotrip.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| variotrip.com. | DS published | 2371 | 13 | Verified |
| variotrip.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://variotrip.com/wp-json/variotrip/mcp | Verified | 200 | |
| http (plaintext) | http://variotrip.com/wp-json/variotrip/mcp | HTTPS enforced | 301 | https://variotrip.com/wp-json/variotrip/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 →
get_networks Networks of a country ~203
The mobile networks the customer can tick for one country (operator name, 4G/5G) with the price of a reference one-country route with that network switched on (1 GB · 7 days; the networks of the country that are not dearer come with it), so you can say which network is the cheapest and what the others add.
| 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. |
| currency | string | – | Optional ISO 4217 override for prices. |
| destination | string | yes | Country in ANY language or its ISO code, e.g. "Japan", "Japon", "jp". Map a city to its country first. |
| language | string | – | ISO language of the conversation, e.g. en, de, ja. Localizes country names and sets the language/currency of links and prices. |
No output schema declared.
No examples provided.
get_shop_facts Shop facts ~155
What variotrip is and how it works, in the shop’s own words: one mobile-data eSIM for the whole route, one shared data pool, the trip length, ranges, delivery, payment, hotspot, activation, top-ups (data, days or a country), router activation, e-mails, support. Use for any question that is not a price.
| 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 names and sets the language/currency of links and prices. |
No output schema declared.
No examples provided.
list_destinations List destinations ~147
Every country variotrip can put on a route, with the number of selectable networks and the starting price of a one-country route (1 GB · 7 days · cheapest network). Use to check coverage or to see which countries of a trip are available.
| 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. |
| currency | string | – | Optional ISO 4217 override for prices. |
| language | string | – | ISO language of the conversation, e.g. en, de, ja. Localizes country names and sets the language/currency of links and prices. |
No output schema declared.
No examples provided.
price_grid Price grid for a route ~245
The same route priced for several trip lengths (days, max 8) and several pool sizes (gb, max 6), in one call — e.g. to compare with other providers or to find the best fit. Same server prices as quote_route; each cell has its own buy_url.
| 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. |
| currency | string | – | Optional ISO 4217 override for prices. |
| days | array | yes | Up to 8 trip lengths, e.g. [7,14,21,30]. |
| gb | array | – | Optional: up to 6 pool sizes for the whole route in whole GB, e.g. [5,10,20]. Omit = sized for normal use from each trip length. |
| language | string | – | ISO language of the conversation, e.g. en, de, ja. Localizes country names and sets the language/currency of links and prices. |
| route | array | yes | The countries of the trip in any order (1–8, each once). |
No output schema declared.
No examples provided.
quote_route Quote a route ~304
Use while the customer is still deciding — "how much is …?": the exact price of ONE eSIM for the whole route — the countries in any order (1–8) with their networks, ONE data pool in GB for all of them and the trip length — the server price the customer would pay. A single country is a route of one. Quote it as returned, never compute, add up or scale it yourself. The result carries a buy_url for reference; 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. |
| currency | string | – | Optional ISO 4217 override for prices. |
| days | integer | yes | Trip length in days (1–90) for the whole route, counted from the first connection anywhere on the route. |
| gb | integer | – | The data pool for the WHOLE route in whole GB (1–100), shared by every country. Omit = sized for normal use (1.5 GB × days). Not sure? Call recommend_config. |
| language | string | – | ISO language of the conversation, e.g. en, de, ja. Localizes country names and sets the language/currency of links and prices. |
| route | array | yes | The countries of the trip in any order (1–8, each once). |
| Name | Type | Req | Description |
|---|---|---|---|
| activation_trigger | string | – | first_connection (anywhere on the route) |
| buy_url | string | – | The route builder pre-set to exactly this route. Use verbatim. |
| countries | integer | – | – |
| currency | string | – | – |
| data_gb | integer | – | ONE data pool for every country on the route (whole GB), used wherever the customer is. |
| days | integer | – | Trip length, counted from the first connection anywhere on the route. |
| hotspot | boolean | – | – |
| not_available | array | – | Requested countries variotrip cannot add (left out of the quote). |
| note | string | – | Present when something about the request had to be adjusted — read it to the customer. |
| price | number | – | FULL price of this route in currency — the amount paid. Not per day, per GB or per country. |
| price_basis | string | – | – |
| price_is_final | boolean | – | – |
| route | array | – | The countries on the eSIM in any order with the networks of each. |
| topup | object | – | How the customer adds data, days or a country later (not through the tools). |
No examples provided.
recommend_config Recommend a route ~351
Use when the customer describes a trip instead of a size: the countries (with the days in each, when known) and how they use data (usage light / normal / heavy, or gb_per_day). Sizes the shared pool from the trip length and returns three server-quoted routes — exact, comfortable (×1.5) and generous (×2) — each with the pool in GB, the full price, a one-line reason and its buy_url, plus an optional budget check. Same prices as quote_route.
| 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 for the whole route in the quoted currency; options above it are marked. |
| currency | string | – | Optional ISO 4217 override for prices. |
| days | integer | – | Trip length in days (1–90). Give days, or days_in_country on the countries (then the trip length is their sum). With neither, the call fails with invalid_argument asking for days. |
| 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 names and sets the language/currency of links and prices. |
| route | array | yes | The countries of the trip in any order (1–8, each once). |
| usage | string | – | light ≈ 0.5 GB/day, normal ≈ 1.5 GB/day (default), heavy ≈ 4 GB/day. |
No output schema declared.
No examples provided.
start_checkout Start secure checkout ~335
Use only once the customer has decided to buy ("I'll take it", "how do I buy?"): the checkout handoff for one route (same input as quote_route). Returns the buy_url to give the customer, the final price and a ready-to-send checkout block (next_step, payment_methods, delivery) — on the page the route builder shows exactly this route; they press the buy button (buy_button, e.g. "Get it" in English) and pay 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_route.
| 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. |
| currency | string | – | Optional ISO 4217 override for prices. |
| days | integer | yes | Trip length in days (1–90) for the whole route, counted from the first connection anywhere on the route. |
| gb | integer | – | The data pool for the WHOLE route in whole GB (1–100), shared by every country. Omit = sized for normal use (1.5 GB × days). Not sure? Call recommend_config. |
| language | string | – | ISO language of the conversation, e.g. en, de, ja. Localizes country names and sets the language/currency of links and prices. |
| route | array | yes | The countries of the trip in any order (1–8, each once). |
| Name | Type | Req | Description |
|---|---|---|---|
| activation_trigger | string | – | first_connection (anywhere on the route) |
| 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 route builder pre-set to exactly this route. Use verbatim. |
| countries | integer | – | – |
| currency | string | yes | – |
| data_gb | integer | – | ONE data pool for every country on the route (whole GB), used wherever the customer is. |
| days | integer | – | Trip length, counted from the first connection anywhere on the route. |
| 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 it", pay. |
| not_available | array | – | Requested countries variotrip cannot add (left out of the quote). |
| 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 this route in currency — the amount paid. Not per day, per GB or per country. |
| price_basis | string | – | – |
| price_is_final | boolean | – | – |
| route | array | – | The countries on the eSIM in any order with the networks of each. |
| topup | object | – | How the customer adds data, days or a country later (not through the tools). |
No examples provided.
How do I install the variotrip route eSIM configurator MCP server?
variotrip route eSIM configurator is a hosted endpoint at https://variotrip.com/wp-json/variotrip/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 · variotrip.com
claude mcp add --transport http com-variotrip-esim-catalog 'https://variotrip.com/wp-json/variotrip/mcp'
What is the variotrip route eSIM configurator MCP server?
variotrip route eSIM configurator is an MCP server listed in the public MCP registry as com.variotrip/esim-catalog. One travel eSIM for up to 8 countries: live quotes by route, GB, days and networks, plus a buy link. This page covers its hosted endpoint (https://variotrip.com/wp-json/variotrip/mcp).
Is the variotrip route eSIM configurator MCP server safe to use?
variotrip route eSIM configurator scores 86 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 variotrip route eSIM configurator MCP server expose?
variotrip route eSIM configurator exposes 7 tools: get_shop_facts, list_destinations, get_networks, quote_route, recommend_config, and 2 more. Their descriptions and schemas cost roughly 1,740 tokens of context every time the server is loaded.
Does the variotrip route eSIM configurator MCP server require authentication?
No. We connected to variotrip route eSIM configurator without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the variotrip route eSIM configurator MCP server still maintained?
variotrip route eSIM configurator 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 variotrip route eSIM configurator MCP server?
VerifyMCP ran 13 checks on variotrip route eSIM configurator, 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.