Skyalo Travel Connectivity Guide
REMOTE · SKYALO.COM
Estimate mobile-data needs and build a provider-neutral connectivity checklist for any trip.
Available components
Last scanned (16 hours ago)
Scores higher than 71% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Productivity and Notes
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 Security74
- 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability42
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1276 tokens (~79/item across 16 items; 4 tools + 12 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 68% of tool parameters carry a description.Partial
- 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
- Supports UI / widget rendering.Pass
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
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 0
- “build_travel_connectivity_guide” reworded the description of “locale” cosmetic
- “search_skyalo_esim_plans” reworded the description of “locale” cosmetic
2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 13 Nov 26 0
- Resource “skyalo-esim-device-readiness-widget” now points somewhere else: ui://widget/skyalo-device-readiness-v2-bridge.html → ui://widget/skyalo-device-check-v2-2.html security
- Resource “skyalo-travel-connectivity-guide-widget” now points somewhere else: ui://widget/skyalo-travel-connectivity-guide.html → ui://widget/skyalo-trip-planner-v2-2.html security
- The server rewrote its instructions, which are the text every model session reads security
- Tool coverage: 62% → 68% ▲ functional
- Schema quality: fail → pass ▲ functional
- New resource “legacy-ui://widget/skyalo-device-readiness-v2-1-1.html” functional
- New resource “legacy-ui://widget/skyalo-device-readiness-v2-1-2.html” functional
- New resource “legacy-ui://widget/skyalo-device-readiness-v2-bridge.html” functional
- New resource “legacy-ui://widget/skyalo-plan-discovery-v2-1-1.html” functional
- New resource “legacy-ui://widget/skyalo-plan-discovery-v2-1-2.html” functional
- New resource “legacy-ui://widget/skyalo-plan-discovery-v2-1.html” functional
- New resource “legacy-ui://widget/skyalo-travel-connectivity-guide-v2-1-1.html” functional
- New resource “legacy-ui://widget/skyalo-travel-connectivity-guide-v2-1-2.html” functional
- New resource “legacy-ui://widget/skyalo-travel-connectivity-guide.html” functional
- New resource “skyalo-plan-discovery-widget-v2-1” functional
- Server version: 2.0.0 → 2.1.0 functional
- New tool “prepare_skyalo_purchase_handoff” functional
- New tool “search_skyalo_esim_plans” functional
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- Stability: pass → 0.97 functional
- 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
- 28 Sept 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
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://skyalo.com/chatgpt/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=skyalo.com | CN=WE1,O=Google Trust Services,C=US | 13 Nov 2026 | 11 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 7fc69c170ea299720e0e6b5dd46d738d |
| SANs: skyalo.com, *.skyalo.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 insecure
Validation of skyalo.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| skyalo.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
|---|---|
| x-content-type-options | nosniff |
| permissions-policy | browsing-topics=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://skyalo.com/chatgpt/mcp | Verified | 200 | |
| http (plaintext) | http://skyalo.com/chatgpt/mcp | HTTPS enforced | 301 | https://skyalo.com/chatgpt/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 →
build_travel_connectivity_guide Build a travel connectivity guide ~229
Creates a free, provider-neutral mobile-data estimate and readiness checklist for a travel route. Use it for trip data budgeting, hotspot planning, offline readiness, and connection fallback advice. Do not use it for a pure phone eSIM compatibility question; use check_esim_device_compatibility instead. It does not browse, compare, promote, recommend, price, sell, or link to products, plans, carriers, or connectivity services.
| Name | Type | Req | Description |
|---|---|---|---|
| deviceReadiness | string | – | confirmed when eSIM support and unlocked status are known, unsure when unverified, or not-supported when the device cannot use eSIM. |
| hotspot | boolean | – | Whether one or more travelers expect to share data by hotspot. |
| locale | string | – | BCP 47 language override; otherwise use the ChatGPT locale. |
| stops | array | yes | One to eight destinations in travel order. |
| travelers | integer | – | Travelers who need connectivity. |
| usageProfile | string | – | light for maps and messaging, balanced for everyday use, heavy for frequent media, or remote-work for calls and laptop work. |
| Name | Type | Req | Description |
|---|---|---|---|
| limitations | array | yes | – |
| questionsToConfirm | array | yes | – |
| readinessChecklist | array | yes | – |
| riskSignals | array | yes | – |
| safeFallbacks | array | yes | – |
| status | string | yes | – |
| stops | array | yes | – |
| summary | object | yes | – |
No examples provided.
check_esim_device_compatibility Check an exact phone's eSIM readiness ~193
Use this tool whenever the user asks whether a phone supports eSIM or is ready for a travel eSIM. Check an exact phone model against Skyalo's manufacturer-sourced compatibility catalog, including regional variants, carrier locks, EID, and Add eSIM settings. Do not call build_travel_connectivity_guide for a pure device question. Unknown never means incompatible. This tool does not search, compare, recommend, price, sell, or link to connectivity plans.
| Name | Type | Req | Description |
|---|---|---|---|
| addEsimSettingPresent | boolean | – | – |
| carrierUnlocked | boolean | – | – |
| eidPresent | boolean | – | – |
| locale | string | – | – |
| manufacturer | string | – | – |
| model | string | yes | Exact phone model, for example Samsung Galaxy S24 or Apple iPhone 15; not a broad product family. |
| region | string | – | Country or sales region of the exact device variant. |
| Name | Type | Req | Description |
|---|---|---|---|
| catalogStatus | string | – | – |
| checks | object | – | – |
| device | – | – | – |
| guidance | array | – | – |
| locale | string | – | – |
| reason | string | – | – |
| source | string | yes | – |
| status | string | yes | – |
| suggestions | array | – | – |
No examples provided.
prepare_skyalo_purchase_handoff Open a selected Skyalo plan for purchase ~224
Prepare an external Skyalo product-page handoff only after the user explicitly selects an exact planId returned by search_skyalo_esim_plans and asks to buy it. Re-read current Skyalo inventory, match that exact planId, and return one allowlisted product-page URL. The purchase, authentication, order creation, payment, delivery, activation, installation, wallet, balance, and top-up occur outside ChatGPT. Never call this tool from a browsing or comparison request alone.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | The same country or region used for the plan search. |
| locale | string | – | – |
| planId | string | yes | Exact planId returned by search_skyalo_esim_plans and explicitly selected by the user. |
| planType | string | – | The same plan-type filter used for the preceding plan search. |
| requestedDataGb | number | – | The same data filter used for the preceding plan search, when present. |
| requestedDurationDays | integer | – | The same duration filter used for the preceding plan search, when present. |
| Name | Type | Req | Description |
|---|---|---|---|
| destination | – | – | – |
| externalCheckout | boolean | – | – |
| filters | object | – | – |
| freshness | string | – | – |
| lastUpdated | string|null | – | – |
| limitations | array | – | – |
| locale | string | – | – |
| plans | array | – | – |
| purchaseHandoffAvailable | boolean | – | – |
| query | string | – | – |
| reason | string | – | – |
| requestedCurrency | string | – | – |
| source | string | yes | – |
| status | string | yes | – |
| suggestions | array | – | – |
| supportedCurrencies | array | – | – |
No examples provided.
search_skyalo_esim_plans Search current Skyalo eSIM plans ~264
Search current first-party Skyalo travel eSIM inventory for a country or region. Use only when the user explicitly asks for a Skyalo plan or current eSIM plan options. Returns factual data allowance, validity, availability, and USD price from Skyalo's backend. This is not a comparison of all providers and must not be described as best or cheapest across the market. Search results never include a purchase action. If the user later selects an exact displayed planId and explicitly asks to buy it, use prepare_skyalo_purchase_handoff.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | ISO 4217 currency. This release exposes authoritative USD prices only. |
| destination | string | yes | Country name, ISO country code, localized destination name, common alias, or supported Skyalo region. |
| destinationType | string | – | Use auto unless the user explicitly distinguishes a country from a region. |
| hotspot | boolean | – | – |
| locale | string | – | BCP 47 language override; otherwise use the ChatGPT locale. |
| planType | string | – | – |
| requestedDataGb | number | – | Requested or estimated total data in GB. |
| requestedDurationDays | integer | – | Trip length or minimum desired plan validity in days. |
| travelers | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| destination | – | – | – |
| externalCheckout | boolean | – | – |
| filters | object | – | – |
| freshness | string | – | – |
| lastUpdated | string|null | – | – |
| limitations | array | – | – |
| locale | string | – | – |
| plans | array | – | – |
| purchaseHandoffAvailable | boolean | – | – |
| query | string | – | – |
| reason | string | – | – |
| requestedCurrency | string | – | – |
| source | string | yes | – |
| status | string | yes | – |
| suggestions | array | – | – |
| supportedCurrencies | array | – | – |
No examples provided.
How do I install the Skyalo Travel Connectivity Guide MCP server?
Skyalo Travel Connectivity Guide is a hosted endpoint at https://skyalo.com/chatgpt/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 · skyalo.com
claude mcp add --transport http com-skyalo-travel-connectivity-guide 'https://skyalo.com/chatgpt/mcp'
What is the Skyalo Travel Connectivity Guide MCP server?
Skyalo Travel Connectivity Guide is an MCP server listed in the public MCP registry as com.skyalo/travel-connectivity-guide. Estimate mobile-data needs and build a provider-neutral connectivity checklist for any trip. This page covers its hosted endpoint (https://skyalo.com/chatgpt/mcp).
Is the Skyalo Travel Connectivity Guide MCP server safe to use?
Skyalo Travel Connectivity Guide 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 Skyalo Travel Connectivity Guide MCP server expose?
Skyalo Travel Connectivity Guide exposes 4 tools: prepare_skyalo_purchase_handoff, build_travel_connectivity_guide, search_skyalo_esim_plans, check_esim_device_compatibility. Their descriptions and schemas cost roughly 910 tokens of context every time the server is loaded.
Does the Skyalo Travel Connectivity Guide MCP server require authentication?
No. We connected to Skyalo Travel Connectivity Guide without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Skyalo Travel Connectivity Guide MCP server still maintained?
Skyalo Travel Connectivity Guide 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 Skyalo Travel Connectivity Guide MCP server?
VerifyMCP ran 14 checks on Skyalo Travel Connectivity Guide, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 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.