updated 2026-11-10 04:07 UTC

Google Flights MCP (fli)

Repository

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 4.6 / 10
Provenance Attested
Signed commits 95%
Last push 51d ago
Advisories None known
Compare Google Flights MCP (fli)

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Google Flights MCP (fli) scores 76.6/100 (Grade B), ranked #244 of 1374 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 4.6/10; 95% of recent commits are signed; no published advisory affects its latest release (flights); last pushed 2026-09-20. Every point is earned from checkable signals — never paid placement. How scoring works →

How Google Flights MCP (fli) could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Google Flights MCP (fli) and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/punitarani/fli, MIT, last pushed 2026-09-20. 95% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.6/10 (scanned Nov 7, 2026). The checks that decide who can get a change released:

    • Code Review3
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 7
    CII-Best-Practices 0
    Code-Review 3
    Contributors 3
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked and attested

    • PyPI flights Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: flights 0.9.0. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-08-26 OSSF Scorecard: 3.7/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Google Flights MCP (fli)’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Google Flights MCP (fli) compares in MCP Servers

  1. #138 MCP Gsheets 76.9 +0.3
  2. #139 E Arveldaja MCP 76.8 +0.2
  3. #140 Google Flights MCP (fli) 76.6 this agent
  4. #141 Komodo MCP Server 76.5 −0.1
  5. #142 Activitypub MCP 76.4 −0.2

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

Where the 76.6 comes from

HVTrust dimensions vs the MCP Servers average

76.6 / 100 · 100.0% confidence

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

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
18.0 / 25
7.2 above avg 10.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.3 above avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
12.4 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
8.6 / 20
3.6 below avg 12.2
AdoptionLog-scaled stars · package downloads
13.6 / 20
6.0 above avg 7.6

Quick Trust Read

What Would Improve It
Improve maintenance to lift the weakest part of the trust profile.
Recent Changes
2026-10-21
Grade Changed
Trust grade A → B
2026-10-21
Rank Moved
Rank dropped 56 spots (#150 → #206)
2026-10-21
HVTrust Changed
HVTrust down 3.3pts (80.9 → 77.6)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.6/10. Tighten the weakest checks to improve public safety evidence.
Refresh maintenance signals The repo was last pushed 51 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent
View MCP Servers Report missing data
51.6
Activity sub-score · out of 100
#140
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B 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-11-10 04:07 UTC · Repo last pushed 51 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
3.5k
Forks
423
Last Push
2026-09-20
51 days ago
Commits (4 wk)
0
Downloads (7d)
6,284
pypi
HN mentions (30d)
—
Open Issues
14
Rank Change
▼2
was #242

Analysis

Activity Inputs

51.6 / 100
StarsRepository reach
21.3 / 30
FreshnessLast push recency
17.9 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
12.2 / 20

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 4.6/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?
Slowing down. Last push was 51 days ago — keep an eye on whether activity resumes.
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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 14HVTrust 5Score 3Grade 3Scorecard 1Surface 1Delisted 1Listed 1Provenance 1MCP 1
2026-10-21
Grade Changed
Trust grade A → B
2026-10-21
Rank Moved
Rank dropped 56 spots (#150 → #206)
2026-10-21
HVTrust Changed
HVTrust down 3.3pts (80.9 → 77.6)
2026-10-21
Activity Score Changed
Activity score down 10pts (64 → 54)
2026-10-20
Rank Moved
Rank dropped 45 spots (#105 → #150)
2026-10-20
HVTrust Changed
HVTrust down 3.2pts (84.1 → 80.9)
2026-10-20
Activity Score Changed
Activity score down 10pts (74 → 64)
2026-10-04
Rank Moved
Rank rose 30 spots (#113 → #83)
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)
GitHub → PyPI: flights

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 76.6 Grade B
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.4 · Raw JSON