Airflow MCP Server

MCP Server for Apache Airflow

MCP Servers Python Needs review MIT

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

OSSF Scorecard 3.0 / 10
Provenance None
Signed commits 79%
Last push 392d ago
Advisories None known
Compare Airflow MCP Server
Suggest a correction

In detail: Airflow MCP Server scores 27.4/100 (Grade D), ranked #1348 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.0/10; 79% of recent commits are signed; no published advisory affects its latest release (airflow-mcp-server); last pushed 2025-10-14. Every point is earned from checkable signals — never paid placement. How scoring works →

How Airflow MCP Server 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.

Active listing, but review is needed
  • [4.2.1] no meaningful activity in 12 months (last push 2025-10-14)

Chain of custody

Scanners check what the code says. This traces who ships Airflow MCP Server 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 Partly signed

    github.com/abhishekbhakat/airflow-mcp-server, MIT, last pushed 2025-10-14. 79% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

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

    • Code Review0
    • Branch Protection1
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 1
    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 0
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0
  3. Published packages Not linked

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: airflow-mcp-server 0.9.1. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

  • 2026-09-03 OSSF Scorecard: 3.0/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 Airflow MCP Server’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.

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 Airflow MCP Server compares in MCP Servers

  1. #768 Paypal MCP Server 29.0 +1.6
  2. #769 Crawleo MCP 28.8 +1.4
  3. #770 Airflow MCP Server 27.4 this agent
  4. #771 Fortnox MCP 27.1 −0.3
  5. #772 Hatago MCP Hub 26.8 −0.6

Bars show each HVTrust score; the tick marks Airflow MCP Server’s 27.4.

Where the 27.4 comes from

HVTrust dimensions vs the MCP Servers average

27.4 / 100 · 100.0% confidence

Airflow MCP Server MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.7 / 25
3.1 below avg 10.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.9 below avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
11.1 / 17
1.2 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
0 / 20
12.2 below avg 12.2
AdoptionLog-scaled stars · package downloads
7.1 / 20
in line with avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-15
Rank Moved
Rank dropped 104 spots (#1244 → #1348)
2026-10-15
HVTrust Changed
HVTrust down 10.0pts (37.6 → 27.6)
2026-10-14
Warning Issued
Warning: eligibility issues detected
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.0/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Refresh maintenance signals The repo was last pushed 392 days ago. Fresh activity helps separate stable projects from stale ones.
Review Flags
[4.2.1] no meaningful activity in 12 months (last push 2025-10-14)
Compare with another agent
View MCP Servers Report missing data
14.0
Activity sub-score · out of 100
#770

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

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
33
Forks
10
Last Push
2025-10-14
392 days ago
Commits (4 wk)
0
Downloads (7d)
352
pypi
HN mentions (30d)
—
Open Issues
2
Rank Change
=
was #1348

Analysis

Activity Inputs

14.0 / 100
StarsRepository reach
9.2 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
4.8 / 20

Common questions about Airflow MCP Server

Public trust evidence for Airflow MCP Server 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 Airflow MCP Server publish package provenance?
No published build provenance is currently detected for Airflow MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Airflow MCP Server have an OpenSSF Scorecard?
Airflow MCP Server 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 Airflow MCP Server actively maintained?
Stale. The repository has not been pushed to in 392 days. Consider whether the project is still being maintained.
What license does Airflow MCP Server use?
Airflow MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Airflow MCP Server's commits signed?
79% of the last 100 commits to Airflow MCP Server 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
Airflow MCP Server 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
medium confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
low confidence
Unknown
Package source metadata is missing or inconclusive
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 Airflow MCP Server'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
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Airflow MCP Server?

For maintainers

HVTrust scores Airflow MCP Server 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 22HVTrust 3Scorecard 1Delisted 1Listed 1MCP 1Surface 1Warning Issued 1
2026-10-15
Rank Moved
Rank dropped 104 spots (#1244 → #1348)
2026-10-15
HVTrust Changed
HVTrust down 10.0pts (37.6 → 27.6)
2026-10-14
Warning Issued
Warning: eligibility issues detected
2026-09-24
Rank Moved
Rank dropped 18 spots (#1189 → #1207)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 95 spots (#1284 → #1189)
2026-09-23
HVTrust Changed
HVTrust up 24.8pts (13.9 → 38.7)
2026-09-22
Newly Listed
First tracked at rank #1284
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-19
Rank Moved
Rank rose 22 spots (#1198 → #1176)
2026-09-09
Rank Moved
Rank dropped 12 spots (#1186 → #1198)
2026-09-08
Rank Moved
Rank dropped 14 spots (#1172 → #1186)
2026-09-07
Rank Moved
Rank dropped 14 spots (#1158 → #1172)
2026-09-06
Rank Moved
Rank dropped 14 spots (#1144 → #1158)
2026-09-05
Rank Moved
Rank dropped 32 spots (#1112 → #1144)
2026-09-04
Rank Moved
Rank dropped 21 spots (#1091 → #1112)
2026-09-03
Scorecard Added
OSSF Scorecard: 3.0/10
2026-09-03
Rank Moved
Rank rose 172 spots (#1263 → #1091)
2026-09-03
HVTrust Changed
HVTrust up 16.3pts (20.8 → 37.1)
2026-09-02
Rank Moved
Rank dropped 28 spots (#1235 → #1263)
2026-09-01
Rank Moved
Rank dropped 21 spots (#1214 → #1235)
2026-08-31
Rank Moved
Rank dropped 23 spots (#1191 → #1214)
2026-08-30
Rank Moved
Rank dropped 28 spots (#1163 → #1191)
2026-08-29
Rank Moved
Rank dropped 29 spots (#1134 → #1163)
2026-08-28
Rank Moved
Rank dropped 21 spots (#1113 → #1134)
2026-08-27
Rank Moved
Rank dropped 17 spots (#1096 → #1113)
2026-08-26
Rank Moved
Rank dropped 73 spots (#1023 → #1096)
2026-08-17
Rank Moved
Rank rose 12 spots (#1037 → #1025)
2026-08-16
Rank Moved
Rank dropped 31 spots (#1006 → #1037)
2026-08-13
Rank Moved
Rank dropped 12 spots (#992 → #1004)

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 27.4 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/airflow-mcp-server.svg)](https://hvtracker.net/agents/airflow-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/airflow-mcp-server"><img src="https://hvtracker.net/badge/airflow-mcp-server.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