_ registry / mcp http-sse · checked 4h ago

seatwifi

https://mcp.seatwifi.com

Registry code: 66b9d4f5704d0da3

api record

SeatWiFi tracks in-flight WiFi: which provider (Starlink, Viasat, Gogo, Panasonic, Amazon Leo) is fitted to which aircraft, whether it is free, how fast it is, and how far each airline's Starlink rollout has progressed.

Use these tools whenever someone asks about internet, WiFi, connectivity, streaming, or working online on a specific flight, airline, aircraft type, or tail number — including "will I have WiFi on my flight", "is Starlink on this route", and "which airline has the best WiFi".

endpoint
https://mcp.seatwifi.com/mcp
protocol
http-sse ·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 seatwifi live?
Yes — it answered the hub's last check (checked 4h ago). It answered 99% of checks over the last 30 days.
Is seatwifi free to use?
Yes — the hub reached it with no key and no payment.
What tools does seatwifi have?
9 tools: get_airline_wifi, search_wifi, get_tail_info, get_wifi_facts, get_flight_wifi, open_seatwifi, get_rollouts, list_airlines, ….
Is seatwifi 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
99.1%

90 days 99.5%· all time 99.5%

latency
152ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 373 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
maps travel & places travel & transport
used for
  • check if a flight has wifi
  • get airline wifi providers
  • get starlink rollout status
  • get in-flight wifi speeds
takes → gives
text → data
tools
8 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

_ what it can do 9 tools
4 open 5 never probed 4 of 9 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.

  • open_seatwifi open 26h ago

    Opens the SeatWiFi home view: search, Starlink and satellite rollouts, and every tracked airline. Takes no arguments.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • get_rollouts reads open 4h ago

    Starlink and satellite WiFi rollout progress per aircraft type: status (complete, in_progress, planned, announced), fleet percentage, and expected completion. Omit airline_code for every tracked airline.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "airline_code": {
      "type": "string",
      "description": "Optional IATA airline code to filter rollouts, e.g. \"UA\""
    }
  },
  "additionalProperties": false
}
    arguments 11 lines
  • list_airlines reads open 4h ago

    Every airline SeatWiFi tracks, with its WiFi providers. Large response — use search_wifi or get_airline_wifi when you know which airline you want.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • get_speed_stats reads open 4h ago

    Crowd-sourced in-flight WiFi speed reports: average download/upload Mbps, latency, and a per-provider breakdown. Use for "is the WiFi fast enough" questions. Pass a flight_number or an airline_code, not both.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "airline_code": {
      "type": "string",
      "description": "IATA airline code, e.g. \"UA\""
    },
    "flight_number": {
      "type": "string",
      "description": "IATA flight number, e.g. \"UA123\""
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • get_airline_wifi reads unknown 26h ago

    WiFi providers an airline uses fleet-wide, plus a fleet summary and whether WiFi is free. Use when the question is about the airline rather than one flight.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "airline_code"
  ],
  "properties": {
    "airline_code": {
      "type": "string",
      "description": "IATA airline code, e.g. \"UA\" for United, \"DL\" for Delta"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • search_wifi reads unknown 13h ago

    Free-text search across airlines and flights when you only have a name or partial term. Use a specific tool instead when you already have a flight number, airline code, or tail number.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "Search query, e.g. \"United\" or \"UA123\""
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • get_tail_info reads unknown 13h ago

    WiFi provider history for one aircraft by tail number, including crowd-sourced reports and fleet assignment. Use when the exact airframe is known.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "tail_number"
  ],
  "properties": {
    "tail_number": {
      "type": "string",
      "description": "Aircraft registration / tail number, e.g. \"N12345\""
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • get_wifi_facts reads unknown 13h ago

    Best answer for "will this flight have WiFi". Predicts the WiFi provider for a flight number on a given date, with probability, the tail number expected to operate it, aircraft type, and the airline fleet fallback. Prefer this over get_flight_wifi.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "flight_number"
  ],
  "properties": {
    "date": {
      "type": "string",
      "description": "Flight date in YYYY-MM-DD format. Defaults to today."
    },
    "flight_number": {
      "type": "string",
      "description": "IATA flight number, e.g. \"UA123\""
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • get_flight_wifi reads unknown 26h ago

    Shorter WiFi lookup for a flight number: provider, confidence, airline, aircraft, and Starlink status. Use get_wifi_facts instead when you need the date, tail number, or reasoning.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "flight_number"
  ],
  "properties": {
    "flight_number": {
      "type": "string",
      "description": "IATA flight number, e.g. \"UA123\" or \"DL456\""
    }
  },
  "additionalProperties": false
}
    arguments 14 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 66b9d4f5704d0da3.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/66b9d4f5704d0da3/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/66b9d4f5704d0da3/badge.svg)](https://brick.blue/agent/66b9d4f5704d0da3?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
100%

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.