Airflow Api MCP Server
mcp-airflow-api
PyPI
v3.6.7
Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
Model Context Protocol (MCP) server for Apache Airflow API integration. Provides comprehensive tools for managing Airflow clusters including service operations, configuration management, status monitoring, and request tracking.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 2 = 98. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 0
Tools 56
Each tool and what it can reach — statically extracted from the published source.
all_dag_event_summaryno sensitive capabilityall_dag_import_summaryno sensitive capabilitycreate_connectionno sensitive capabilitydag_calendarno sensitive capabilitydag_codeno sensitive capabilitydag_graphno sensitive capabilitydag_run_durationno sensitive capabilitydag_task_durationno sensitive capabilitydelete_connectionno sensitive capabilityfailed_dagsno sensitive capability
Show 46 more tools ↓
get_configno sensitive capabilityget_config_sectionno sensitive capabilityget_connectionno sensitive capabilityget_dagno sensitive capabilityget_dags_detailed_batchno sensitive capabilityget_datasetno sensitive capabilityget_dataset_eventsno sensitive capabilityget_event_logno sensitive capabilityget_healthno sensitive capabilityget_import_errorno sensitive capabilityget_poolno sensitive capabilityget_prompt_templateno sensitive capabilityget_providerno sensitive capabilityget_task_instance_detailsno sensitive capabilityget_task_instance_extra_linksno sensitive capabilityget_task_instance_logsno sensitive capabilityget_userno sensitive capabilityget_variableno sensitive capabilityget_versionno sensitive capabilityget_xcom_entryno sensitive capabilitylist_asset_eventsno sensitive capabilitylist_assetsno sensitive capabilitylist_config_sectionsno sensitive capabilitylist_connectionsno sensitive capabilitylist_dagsno sensitive capabilitylist_dataset_eventsno sensitive capabilitylist_datasetsno sensitive capabilitylist_event_logsno sensitive capabilitylist_import_errorsno sensitive capabilitylist_permissionsno sensitive capabilitylist_pluginsno sensitive capabilitylist_poolsno sensitive capabilitylist_providersno sensitive capabilitylist_rolesno sensitive capabilitylist_task_instances_allno sensitive capabilitylist_task_instances_batchno sensitive capabilitylist_tasksno sensitive capabilitylist_usersno sensitive capabilitylist_variablesno sensitive capabilitylist_xcom_entriesno sensitive capabilitypause_dagno sensitive capabilityrunning_dagsno sensitive capabilitysearch_config_optionsno sensitive capabilitytrigger_dagno sensitive capabilityunpause_dagno sensitive capabilityupdate_connectionno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (56 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v3.6.7 latest |
A 98/100 | 0 | 1.13.0 | 2026-08-25 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan mcp-airflow-api --online --registry pypiMore in Cloud & DevOps
Operator control CLI for AdGuard Home with an MCP adapter
interacting with Aliyun (Alibaba Cloud) services through This MCP server provides tools.
MCP server for the Aspro.Cloud REST API
MCP server for Atlassian Confluence and Jira Cloud APIs
AuroraCloud-first MCP server that exposes AuroraDocs workspace data to Claude Desktop and other AI agents
The official AWS Knowledge Base retrieval server using Bedrock Agent Runtime.