Skyalo Travel Connectivity Guide
REMOTE · SKYALO.COM · SCANNED SEP 24
Estimate mobile-data needs and build a provider-neutral connectivity checklist for any trip.
Available components
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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 Usability40
- 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
- Context-footprint check failed: tool/resource definitions use about 575 tokens (~143/item across 4 items; 2 tools + 2 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 62% 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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'
{
"mcpServers": {
"com-skyalo-travel-connectivity-guide": {
"url": "https://skyalo.com/chatgpt/mcp"
}
}
} {
"servers": {
"com-skyalo-travel-connectivity-guide": {
"type": "http",
"url": "https://skyalo.com/chatgpt/mcp"
}
}
} [mcp_servers.com-skyalo-travel-connectivity-guide] url = "https://skyalo.com/chatgpt/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-skyalo-travel-connectivity-guide": {
"type": "remote",
"url": "https://skyalo.com/chatgpt/mcp",
"enabled": true
}
}
} openclaw mcp add com-skyalo-travel-connectivity-guide --url 'https://skyalo.com/chatgpt/mcp' --transport streamable-http
mcp_servers:
com-skyalo-travel-connectivity-guide:
url: "https://skyalo.com/chatgpt/mcp" {
"McpServers": {
"com-skyalo-travel-connectivity-guide": {
"Transport": "http",
"Url": "https://skyalo.com/chatgpt/mcp"
}
}
} assistant mcp add com-skyalo-travel-connectivity-guide -t streamable-http -u 'https://skyalo.com/chatgpt/mcp'
{
"mcpServers": {
"com-skyalo-travel-connectivity-guide": {
"type": "http",
"url": "https://skyalo.com/chatgpt/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 4 Sept 26 −1
- Resource “skyalo-esim-device-readiness-widget” now points somewhere else: ui://widget/skyalo-v2-device-readiness.html → ui://widget/skyalo-device-readiness-v2-bridge.html security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “build_travel_connectivity_guide” rewrote its description, which is the text the model reads security
- Tool “check_esim_device_compatibility” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- “check_esim_device_compatibility” reworded the description of “model” cosmetic
- Tool “check_esim_device_compatibility” changed its title: Check eSIM device compatibility → Check an exact phone's eSIM readiness cosmetic
- 27 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool coverage: 100% → 62% ▼ functional
- Schema quality: 130 → 107 ▲ functional
- New resource “skyalo-esim-device-readiness-widget” functional
- Server version: 1.0.0 → 2.0.0 functional
- New tool “check_esim_device_compatibility” functional
- 26 Aug 26 79
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 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
- 31 Jul 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
- 30 Jul 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
- 27 Jul 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 24 Sept 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 | 15 Sept 2026 | 14 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 85db03f343f34dc813ada0d659ac7084 |
| 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. | present | 19718 | 13 | Verified |
| skyalo.com. | absent | 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 ~226
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 tag for the requested guide. |
| 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 | – | – |
| reason | string | – | – |
| source | string | yes | – |
| status | string | yes | – |
| suggestions | array | – | – |
No examples provided.
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 2 tools: build_travel_connectivity_guide, check_esim_device_compatibility. Their descriptions and schemas cost roughly 419 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 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.