All servers / Travel / Variflight
Variflight
Flight data and status.
Tested by ConnectATDScore 86 out of 100. Tested 2026-11-17 on package version 1.1.0. Package: @variflight-ai/variflight-mcp
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 16 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (18.4 seconds including download)
- Tools offered: 9
- Last published: 2026-09-26
- Weekly downloads (npm): 2,344
- License: ISC · Direct dependencies: 3
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
searchFlightsByDepArr8 of 8 parameters describedSearch direct flights by departure and arrival location plus date. Use depcity and arrcity when the user specifies cities such as BJS or SHA. Use dep and arr when the user specifies exact airports such as PEK or PVG. Provide one departure field and one arrival field, and do not mix city and airport codes for the same side. All codes must be valid IATA 3-letter codes. Date must be in YYYY-MM-DD format. For today's date, use getTodayDate instead of hardcoding.
searchFlightsByNumber4 of 4 parameters describedSearch a flight by flight number and date. The flight number must include the airline code, for example MU2157 or CZ3969. dep and arr are optional and should only be provided when the exact airports are known. Date must be in YYYY-MM-DD format. For today's date, use getTodayDate instead of hardcoding.
getFlightTransferInfo6 of 6 parameters describedSearch connecting flight options between a departure city and an arrival city on a specific date. Use city IATA 3-letter codes such as BJS, SHA, or LAX. This tool is for transfer or connection itineraries between cities, not for airport weather, airport facilities, or realtime tracking. Date must be in YYYY-MM-DD format. For today's date, use getTodayDate instead of hardcoding.
flightHappinessIndex4 of 4 parameters describedUse this tool when the user wants comfort-focused details for a known flight, such as punctuality, aircraft type, cabin configuration, seat comfort, meals, entertainment, or other onboard experience details. This tool works best when a specific flight number and date are already known. Do not use it for fare search, itinerary recommendation, or raw price comparison.
getRealtimeLocationByAnum1 of 1 parameter describedGet realtime flight location by aircraft registration number, also called tail number, such as B2021 or B2022. Use this only when the aircraft registration number is known. If the registration number is unknown, first try to find the flight through searchFlightsByNumber and then use the aircraft registration number from that result.
getTodayDate1 of 1 parameter describedGet today's date in local timezone (YYYY-MM-DD format). Use this tool whenever you need today's date - NEVER hardcode dates.
getFutureWeatherByAirport1 of 1 parameter describedGet the 3-day airport weather forecast for today, tomorrow, and the day after tomorrow by airport IATA 3-letter code, such as PEK, SHA, CAN, or HFE.
searchFlightItineraries3 of 3 parameters describedUse this tool when the user wants a concise recommended itinerary summary in natural language. It returns a text-style result that summarizes how many sale flights match, the overall lowest price, the shortest duration, and several recommended options. Use city IATA 3-letter codes only. If the user instead needs structured raw flight pricing data with each flight and cabin price, use getFlightPriceByCities.
getFlightPriceByCities3 of 3 parameters describedUse this tool when the user needs structured raw pricing data. It returns sale flights between two cities as a list of flights, and each flight contains cabin entries with prices. This is better than searchFlightItineraries when the caller needs per-flight, per-cabin price details instead of a natural-language recommendation summary. All city codes must be valid IATA 3-letter codes (e.g. BJS for Beijing, SHA for Shanghai, CAN for Guangzhou, HFE for Hefei).
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.