Fr24api MCP

Official Flightradar24 API MCP

MCP Servers TypeScript Listed MIT

Is Fr24api MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.0 / 10
Provenance Attested
Signed commits 56%
Last push 247d ago
Compare Fr24api MCP
Suggest a correction

In detail: Fr24api MCP scores 54.7/100 (Grade C), ranked #794 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.0/10; 56% of recent commits are signed; last pushed 2026-01-22. Every point is earned from checkable signals — never paid placement. How scoring works →

How Fr24api MCP compares in MCP Servers

  1. #440 Vaaya 54.8 +0.1
  2. #441 Gmc MCP 54.8 +0.1
  3. #442 Fr24api MCP 54.7 this agent
  4. #443 Happy Platform MCP 54.6 −0.1
  5. #444 Ris MCP Ts 54.6 −0.1

Bars show each HVTrust score; the tick marks Fr24api MCP’s 54.7.

Where the 54.7 comes from

HVTrust dimensions vs the MCP Servers average

54.7 / 100 · 100.0% confidence

Fr24api MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
14.1 / 25
3.8 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.1 / 17
1.1 below avg 12.2
Maintenance60% last-push freshness · 40% commit activity
0 / 20
12.1 below avg 12.1
AdoptionLog-scaled stars · package downloads
6.5 / 20
0.7 below avg 7.2

Quick Trust Read

What Would Improve It
Improve maintenance 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 → C
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.0/10. Tighten the weakest checks to improve public safety evidence.
Refresh maintenance signals The repo was last pushed 247 days ago. Fresh activity helps separate stable projects from stale ones.
11.5
Activity sub-score · out of 100
#442

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C 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 247 days ago — may be stale

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
27
Forks
3
Last Push
2026-01-22
247 days ago
Commits (4 wk)
0
Downloads (7d)
201
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
▲7
was #801

Analysis

Activity Inputs

11.5 / 100
StarsRepository reach
8.7 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
2.8 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
3.0 / 10
OpenSSF Scorecard · scanned Sep 18, 2026
Signed Commits
56%
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 0
Fuzzing 0
License 10
Maintained 0
Packaging 10
Pinned-Dependencies 2
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 0

Common questions about Fr24api MCP

Public trust evidence for Fr24api MCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Fr24api MCP publish package provenance?
Yes. Fr24api MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Fr24api MCP have an OpenSSF Scorecard?
Fr24api MCP has an OpenSSF Scorecard score of 3.0/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 Fr24api MCP actively maintained?
Stale. The repository has not been pushed to in 247 days. Consider whether the project is still being maintained.
What license does Fr24api MCP use?
Fr24api MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Fr24api MCP's commits signed?
56% of the last 100 commits to Fr24api MCP 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
Fr24api MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
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 Fr24api MCP'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

Maintain Fr24api MCP?

For maintainers

HVTrust scores Fr24api MCP 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 19HVTrust 3Listed 2Grade 2Scorecard 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 → C
2026-09-23
Rank Moved
Rank rose 480 spots (#1287 → #807)
2026-09-23
HVTrust Changed
HVTrust up 40.6pts (13.7 → 54.3)
2026-09-22
Newly Listed
First tracked at rank #1287
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-11
Rank Moved
Rank dropped 19 spots (#785 → #804)
2026-09-09
Rank Moved
Rank dropped 10 spots (#778 → #788)
2026-09-08
Grade Changed
Trust grade D → C
2026-09-08
Rank Moved
Rank rose 413 spots (#1191 → #778)
2026-09-08
HVTrust Changed
HVTrust up 18.1pts (36.1 → 54.2)
2026-09-07
Rank Moved
Rank dropped 16 spots (#1175 → #1191)
2026-09-06
Rank Moved
Rank dropped 13 spots (#1162 → #1175)
2026-09-05
Rank Moved
Rank dropped 33 spots (#1129 → #1162)
2026-09-04
Rank Moved
Rank dropped 19 spots (#1110 → #1129)
2026-09-03
Rank Moved
Rank dropped 50 spots (#1060 → #1110)
2026-09-02
Rank Moved
Rank dropped 44 spots (#1016 → #1060)
2026-09-01
Rank Moved
Rank dropped 42 spots (#974 → #1016)
2026-08-31
Rank Moved
Rank dropped 31 spots (#943 → #974)
2026-08-30
Rank Moved
Rank dropped 46 spots (#897 → #943)
2026-08-29
Scorecard Added
OSSF Scorecard: 3.0/10
2026-08-29
Rank Moved
Rank rose 28 spots (#925 → #897)
2026-08-29
HVTrust Changed
HVTrust up 4.3pts (31.8 → 36.1)
2026-08-28
Rank Moved
Rank dropped 33 spots (#892 → #925)
2026-08-27
Rank Moved
Rank dropped 29 spots (#863 → #892)
2026-08-26
Rank Moved
Rank dropped 111 spots (#752 → #863)
2026-08-16
Rank Moved
Rank dropped 15 spots (#743 → #758)
2026-08-10
Rank Moved
Rank dropped 39 spots (#705 → #744)
2026-08-08
Newly Listed
First tracked at rank #707

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 54.7 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/fr24api-mcp.svg)](https://hvtracker.net/agents/fr24api-mcp)
HTML:
<a href="https://hvtracker.net/agents/fr24api-mcp"><img src="https://hvtracker.net/badge/fr24api-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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