_ registry / mcp streamable-http · checked 3h ago

skyalo-travel-connectivity-guide

https://skyalo.com

Registry code: d03d1e64d8ee0c41

api record

Build provider-neutral travel connectivity estimates and check exact-device eSIM readiness. Route pure phone compatibility, eSIM support, carrier-lock, EID, Add eSIM, or regional-variant questions to check_esim_device_compatibility; do not use build_travel_connectivity_guide for those questions. Route trip data budgeting, hotspot, offline-readiness, and connection-fallback questions to build_travel_connectivity_guide. Ask for the exact phone model before a device check, and ask for destinations or trip length only when building a travel guide. Do not compare, promote, recommend, price, sell,…

endpoint
https://skyalo.com/chatgpt/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is skyalo-travel-connectivity-guide live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is skyalo-travel-connectivity-guide free to use?
Yes — the hub reached it with no key and no payment.
What tools does skyalo-travel-connectivity-guide have?
2 tools: check_esim_device_compatibility, build_travel_connectivity_guide.
Is skyalo-travel-connectivity-guide safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
613ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 288 checks · signed record
  • degraded → live
  • unknown → live
_ what it is for
used for
  • check if a phone supports esim
  • estimate mobile data needs for a trip
takes → gives
data → data
tools
2 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 2 tools
2 never probed 0 of 2 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • check_esim_device_compatibility reads unknown 7h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "model"
      ],
      "properties": {
        "model": {
          "type": "string",
          "maxLength": 80,
          "minLength": 1,
          "description": "Exact phone model, for example Samsung Galaxy S24 or Apple iPhone 15; not a broad product family."
        },
        "locale": {
          "type": "string",
          "maxLength": 20,
          "minLength": 2
        },
        "region": {
          "type": "string",
          "maxLength": 80,
          "minLength": 2,
          "description": "Country or sales region of the exact device variant."
        },
        "eidPresent": {
          "type": "boolean"
        },
        "manufacturer": {
          "type": "string",
          "maxLength": 40,
          "minLength": 1
        },
        "carrierUnlocked": {
          "type": "boolean"
        },
        "addEsimSettingPresent": {
          "type": "boolean"
        }
      },
      "additionalProperties": false
    }
    arguments 41 lines
  • build_travel_connectivity_guide reads unknown 7h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "stops"
      ],
      "properties": {
        "stops": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "destination",
              "days"
            ],
            "properties": {
              "days": {
                "type": "integer",
                "maximum": 90,
                "minimum": 1,
                "description": "Number of days at this stop."
              },
              "destination": {
                "type": "string",
                "maxLength": 80,
                "minLength": 1,
                "description": "Country or destination name for this stop."
              }
            },
            "additionalProperties": false
          },
          "maxItems": 8,
          "minItems": 1,
          "description": "One to eight destinations in travel order."
        },
        "locale": {
          "type": "string",
          "default": "en",
          "maxLength": 20,
          "minLength": 2,
          "description": "BCP 47 language tag for the requested guide."
        },
        "hotspot": {
          "type": "boolean",
          "default": false,
          "description": "Whether one or more travelers expect to share data by hotspot."
        },
        "travelers": {
          "type": "integer",
          "default": 1,
          "maximum": 12,
          "minimum": 1,
          "description": "Travelers who need connectivity."
        },
        "usageProfile": {
          "enum": [
            "light",
            "balanced",
            "heavy",
            "remote-work"
          ],
          "type": "string",
          "default": "balanced",
          "description": "light for maps and messaging, balanced for everyday use, heavy for frequent media, or remote-work for calls and laptop work."
        },
        "deviceReadiness": {
          "enum": [
            "confirmed",
            "unsure",
            "not-supported"
          ],
          "type": "string",
          "default": "unsure",
          "description": "confirmed when eSIM support and unlocked status are known, unsure when unverified, or not-supported when the device cannot use eSIM."
        }
      },
      "additionalProperties": false
    }
    arguments 78 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id d03d1e64d8ee0c41.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/d03d1e64d8ee0c41/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/d03d1e64d8ee0c41/badge.svg)](https://brick.blue/agent/d03d1e64d8ee0c41?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
60%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.