Google Flights MCP (fli)

Google Flights MCP, CLI and Python Library

MCP Servers Python Listed MIT

Is Google Flights MCP (fli) safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 3.7 / 10
Provenance Attested
Signed commits 95%
Last push 6d ago
Compare Google Flights MCP (fli)
Suggest a correction

In detail: Google Flights MCP (fli) scores 83.5/100 (Grade A), ranked #106 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 3.7/10; 95% of recent commits are signed; last pushed 2026-09-20. Every point is earned from checkable signals — never paid placement. How scoring works →

How Google Flights MCP (fli) compares in MCP Servers

  1. #41 Better Email MCP 83.6 +0.1
  2. #42 Reversecore MCP 83.6 +0.1
  3. #43 Google Flights MCP (fli) 83.5 this agent
  4. #44 Finopsmcp 83.4 −0.1
  5. #45 Markdown Vault MCP 83.4 −0.1

Bars show each HVTrust score; the tick marks Google Flights MCP (fli)’s 83.5.

Where the 83.5 comes from

HVTrust dimensions vs the MCP Servers average

83.5 / 100 · 100.0% confidence

Google Flights MCP (fli) MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
16.9 / 25
6.6 above avg 10.3
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.6 above avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
11.6 / 17
0.6 below avg 12.2
Maintenance60% last-push freshness · 40% commit activity
17.8 / 20
5.7 above avg 12.1
AdoptionLog-scaled stars · package downloads
13.2 / 20
6.0 above avg 7.2

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → A
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.7/10. Tighten the weakest checks to improve public safety evidence.
76.8
Activity sub-score · out of 100
#43

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-26 06:32 UTC · Repo last pushed 6 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
3.2k
Forks
397
Last Push
2026-09-20
6 days ago
Commits (4 wk)
35
Downloads (7d)
3,876
pypi
HN mentions (30d)
—
Open Issues
11
Rank Change
▼2
was #104

Analysis

Activity Inputs

76.8 / 100
StarsRepository reach
21.0 / 30
FreshnessLast push recency
24.2 / 25
ActivityRecent commits
19.4 / 25
CommunityFork signal
12.1 / 20

Supply Chain Trust

Package Provenance
Verified
pypi attestation
OSSF Scorecard
3.7 / 10
OpenSSF Scorecard · scanned Sep 10, 2026 (refresh pending)
Signed Commits
95%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 10
CII-Best-Practices 0
Code-Review 0
Contributors 3
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 0
Packaging 10
Pinned-Dependencies 0
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 0

Common questions about Google Flights MCP (fli)

Public supply-chain signals for Google Flights MCP (fli) are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Google Flights MCP (fli) carries less obvious unverified-evidence risk than projects with thin signals.
Does Google Flights MCP (fli) publish package provenance?
Yes. Google Flights MCP (fli)'s package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Google Flights MCP (fli) have an OpenSSF Scorecard?
Google Flights MCP (fli) has an OpenSSF Scorecard score of 3.7/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Google Flights MCP (fli) actively maintained?
Actively maintained. The repository was pushed to within the last 6 day(s).
What license does Google Flights MCP (fli) use?
Google Flights MCP (fli) ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Google Flights MCP (fli)'s commits signed?
95% of the last 100 commits to Google Flights MCP (fli) are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Google Flights MCP (fli) appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Google Flights MCP (fli)'s runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-03
Tool Surface Changed
Detected tool/plugin surface changed: declared → none

Maintain Google Flights MCP (fli)?

For maintainers

HVTrust scores Google Flights MCP (fli) from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Reputation Timeline

Signal history
Rank 12HVTrust 3Listed 2Grade 2Scorecard 1Surface 1Score 1Delisted 1Provenance 1MCP 1
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → A
2026-09-23
Rank Moved
Rank rose 653 spots (#752 → #99)
2026-09-23
HVTrust Changed
HVTrust up 53.7pts (30.0 → 83.7)
2026-09-22
Newly Listed
First tracked at rank #752
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Grade Changed
Trust grade B → A
2026-09-20
Rank Moved
Rank rose 161 spots (#256 → #95)
2026-09-20
HVTrust Changed
HVTrust up 10.4pts (73.5 → 83.9)
2026-09-20
Activity Score Changed
Activity score up 28pts (50 → 78)
2026-09-11
Rank Moved
Rank dropped 20 spots (#222 → #242)
2026-09-07
Rank Moved
Rank dropped 18 spots (#198 → #216)
2026-09-05
Rank Moved
Rank dropped 54 spots (#142 → #196)
2026-09-03
Tool Surface Changed
Detected tool/plugin surface changed: declared → none
2026-08-31
Rank Moved
Rank dropped 17 spots (#109 → #126)
2026-08-26
Scorecard Added
OSSF Scorecard: 3.7/10
2026-08-26
Rank Moved
Rank rose 70 spots (#167 → #97)
2026-08-26
HVTrust Changed
HVTrust up 7.6pts (68.7 → 76.3)
2026-08-24
Rank Moved
Rank dropped 10 spots (#154 → #164)
2026-08-22
Rank Moved
Rank rose 10 spots (#162 → #152)
2026-08-19
Rank Moved
Rank dropped 11 spots (#146 → #157)
2026-08-13
Rank Moved
Rank dropped 10 spots (#135 → #145)
2026-08-12
Rank Moved
Rank rose 10 spots (#145 → #135)
2026-08-10
Newly Listed
First tracked at rank #144

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 83.5 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/google-flights-mcp-fli.svg)](https://hvtracker.net/agents/google-flights-mcp-fli)
HTML:
<a href="https://hvtracker.net/agents/google-flights-mcp-fli"><img src="https://hvtracker.net/badge/google-flights-mcp-fli.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON