Adf Graph MCP Server

adf-graph npm v1.10.1

Published by hurleysk — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server that builds a queryable dependency graph from ADF pipeline artifacts

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

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 − 4 = 96. 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:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

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

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 42

Each tool and what it can reach — statically extracted from the published source.

  • graph_deploy_readinessreads sensitive data
  • graph_add_environmentno sensitive capability
  • graph_add_overlayno sensitive capability
  • graph_cdc_analysisno sensitive capability
  • graph_cross_env_artifactno sensitive capability
  • graph_data_lineageno sensitive capability
  • graph_describe_entityno sensitive capability
  • graph_describe_integration_runtimeno sensitive capability
  • graph_describe_pipelineno sensitive capability
  • graph_describe_stored_procedureno sensitive capability
Show 32 more tools ↓
  • graph_describe_tableno sensitive capability
  • graph_describe_triggerno sensitive capability
  • graph_diff_environmentsno sensitive capability
  • graph_diff_pipelineno sensitive capability
  • graph_diff_stagingno sensitive capability
  • graph_entity_coverageno sensitive capability
  • graph_environment_configno sensitive capability
  • graph_exportno sensitive capability
  • graph_filter_chainno sensitive capability
  • graph_find_bad_columnsno sensitive capability
  • graph_find_consumersno sensitive capability
  • graph_find_orchestratorsno sensitive capability
  • graph_find_pathsno sensitive capability
  • graph_generate_scopeno sensitive capability
  • graph_ignore_null_values_auditno sensitive capability
  • graph_impact_analysisno sensitive capability
  • graph_list_environmentsno sensitive capability
  • graph_list_overlaysno sensitive capability
  • graph_parameter_traceno sensitive capability
  • graph_remove_environmentno sensitive capability
  • graph_remove_overlayno sensitive capability
  • graph_searchno sensitive capability
  • graph_sp_bodyno sensitive capability
  • graph_staging_dependenciesno sensitive capability
  • graph_staging_populationno sensitive capability
  • graph_statsno sensitive capability
  • graph_trace_connectionno sensitive capability
  • graph_trace_parametersno sensitive capability
  • graph_validateno sensitive capability
  • graph_validate_pipelineno sensitive capability
  • graph_validate_staging_columnsno sensitive capability
  • graph_validate_statuscodeno sensitive capability

What this scan could not see

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.

VersionScoreFindingsEngineScanned
v1.10.1 latest A 96/100 0 1.13.0 2026-09-09

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.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/adf-graph/badge.svg)](https://mcptrustchecker.com/registry/adf-graph)
HTML
<a href="https://mcptrustchecker.com/registry/adf-graph"><img src="https://mcptrustchecker.com/registry/adf-graph/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/adf-graph/badge.json via https://img.shields.io/endpoint?url=…

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 adf-graph --online

Use the free API → How scoring works

More in Developer Tools