Estimate mobile-data needs and build a provider-neutral connectivity checklist for any trip.
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://skyalo.com/chatgpt/mcp2 tools · 452msbuild_travel_connectivity_guideCreates 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 inst…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 inst…
| Parameter | Type | Description |
|---|---|---|
| stops* | array | 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. |
| hotspot | boolean | Whether one or more travelers expect to share data by hotspot. |
| deviceReadiness | string | confirmed when eSIM support and unlocked status are known, unsure when unverified, or not-supported when the device cannot use eSIM. |
| locale | string | BCP 47 language tag for the requested guide. |
check_esim_device_compatibilityUse 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_gui…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_gui…
| Parameter | Type | Description |
|---|---|---|
| manufacturer | string | — |
| model* | string | 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. |
| carrierUnlocked | boolean | — |
| eidPresent | boolean | — |
| addEsimSettingPresent | boolean | — |
| locale | string | — |
2 of 2 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Estimate mobile-data needs and build a provider-neutral connectivity checklist for any trip.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.