C — Moderate risk signals Graded October 16, 2026Several concerns worth a closer look before you install.Based on public adoption and transparency signals as of October 16, 2026. Our opinion, not a code audit or security guarantee.
App connector · Developer tools
fli
Google Flights MCP, CLI and Python Library
Bottom line: Signal-based grade (3/7 points): well starred on GitHub, public source code. This reflects adoption and transparency, not a code audit.
- Popularity score
- 40/100
- Rank
- Not ranked: outside the 500 most popular tools
- GitHub stars
- 3.2k
What it does
fli is a Google Flights MCP connector that enables AI agents to search flights, check prices, and retrieve travel information programmatically. It provides CLI and Python library interfaces alongside the MCP server for flexible integration into agent workflows.
Who it’s for
Builders integrating flight search capabilities into AI agents and travel-focused applications. Executives evaluating flight data automation for booking systems or travel management tools.
Copy-paste setup
Check these steps against the project’s own instructions before running anything.
Verify against the repo README at https://github.com/punitarani/fli (opens external site) for current installation instructions. Likely approaches include installing via pip for the Python library or running the MCP server directly; Claude Desktop integration would require adding fli to mcpServers configuration with appropriate authentication details for Google Flights access.
Risks
- Credentials scope: Requires Google Flights authentication; unclear from available signals whether credentials are scoped minimally or grant broad access to user accounts
- Data exfiltration: Flight searches and price data transit through the connector; ensure logs and intermediate storage don't leak sensitive travel patterns or pricing data
- Prompt injection: User-supplied flight parameters (dates, routes, preferences) could be exploited if not properly sanitized before API calls
- Third-party dependency: Relies on Google Flights API stability and terms of service; changes to Google's policies could break the connector
- Maintenance risk: Moderate GitHub activity signals but limited npm adoption suggests smaller maintenance surface; security patches may lag
How to stay secure
Least-privilege permissions
- Use a dedicated Google account for the flight search tool that has no access to your personal email, files, or calendar—treat it like a separate work profile
- Check Google permissions regularly by visiting your Google Account settings and revoke any unnecessary access the app may have requested (like contacts or location data)
- Don't share the connector login with other tools or systems; keep flight search credentials isolated from your main business accounts
- Review API scopes with your IT team before deployment to confirm the connector only accesses flight data, not your broader Google account
Network isolation
- Run the connector on a separate network segment if possible (e.g., a dedicated VM or container), away from systems handling payment cards or sensitive employee data
- Block outbound traffic to non-essential destinations; whitelist only Google Flights API endpoints and required Google services
- Log all API calls to a secure, separate logging system so flight queries don't mix with general business logs that might be backed up broadly
- Disable clipboard/file sharing between the connector environment and your main workstations to prevent accidental data spillage
Monitoring
- Set alerts for unusual search patterns—spike in searches for competitor executives' travel, off-hours activity, or searches for restricted destinations
- Review API usage monthly for unexpected cost increases or frequency spikes that could indicate unauthorized access
- Audit who accesses the connector and what searches they perform; maintain a log of user IDs and timestamps
- Monitor for failed authentication attempts that repeat from unfamiliar IP addresses, which could signal attempted compromise
Red flags to watch for
- Unexpected price changes or search results that differ significantly from public-facing Google Flights—may indicate a compromised connector feeding manipulated data
- Slow or failed searches combined with data appearing in logs before it's displayed to users (sign of data interception)
- New permission requests when updating the connector; compare release notes against actual permission changes
- Gaps in update history (no patches for 6+ months) or abandonment of the GitHub repository—stop using it and migrate to an officially maintained tool
Alternatives
- Amadeus Flight Search API – enterprise-grade flight data with official SDK support
- Skyscanner API – broad flight coverage with mature documentation and active maintenance
- Kayak or Expedia affiliate APIs – established travel search integrations with commercial backing
- Custom web scraping solutions – higher effort but avoids API dependencies (comes with legal/ToS risks)