Skip to content
FlightPowers logo

FlightPowers MCP server

Which servers in the official MCP registry are FlightPowers's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-13

← Back to FlightPowers

Whose server it is
  • Registry namecom.flightpowers/bookingverified in the MCP registry

The registry name sits under flightpowers.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-13
  • Stateanswerschecked 2026-10-13
  • Tools3
  • Server calls itselfbooking-hotels-mcp
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-13 the server answered initialize and tools/list without a sign-in. First answer in 124 ms.

Tools it offers3 tools · read 2026-10-13
  • search_hotels

    FlightPowers hotel search: live Booking.com availability and nightly prices for a destination and date range. Input: a free-text destination the way a person would say it ("Rome", "Tokyo Shibuya"), plus check-in and check-out dates…

  • find_hotel_by_name

    FlightPowers single-property lookup: live Booking.com availability and pricing for one named property. Input: the hotel name a person would type (adding the city helps when a chain has many properties) plus check-in and check-out dates…

  • compare_hotel_rates

    FlightPowers cross-source comparison: prices one stay on every source you have a key for. Input: a free-text destination the way a person would say it ("Rome", "Tokyo Shibuya"), check-in and check-out dates, and how many adults. Returns…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "booking": {
      "type": "http",
      "url": "https://hotels.flightpowers.com/mcp"
    }
  }
}
Other servers listed as FlightPowers's
  • com.flightpowers/google-flightsanswers, 2 toolsverified in the MCP registry

OpenAPI spec

7 paths, read 2026-10-13. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.