Is Azure DevOps (ADO) safe to use?

Azure DevOps (ADO) has an HVTrust score of 67.0/100 (Grade B), ranked #400 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Azure DevOps (ADO)?

Azure DevOps (ADO) scores 67.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 2.0k GitHub stars and is categorized under MCP Servers.

Azure DevOps (ADO)

microsoft/azure-devops-mcp

The MCP server for Azure DevOps, bringing the power of Azure DevOps directly to your agents.

MCP Servers TypeScript Listed MIT

Is Azure DevOps (ADO) safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 7.2 / 10

Provenance None

Signed commits 100%

Last push yesterday

Compare Azure DevOps (ADO)

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Azure DevOps (ADO) scores 67.0/100 (Grade B), ranked #400 of 1325 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 7.2/10; 100% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →

How Azure DevOps (ADO) compares in MCP Servers

#237 Codex Control Plane MCP 67.2 +0.2
#238 Sauce Api MCP 67.1 +0.1
#239 Azure DevOps (ADO) 67.0 this agent
#240 MCP Server for WinDbg Crash Analysis 67.0 ±0
#241 E18e MCP 67.0 ±0

Bars show each HVTrust score; the tick marks Azure DevOps (ADO)’s 67.0.

Where the 67.0 comes from

HVTrust dimensions vs the MCP Servers average

67.0 / 100 · 100.0% confidence

Azure DevOps (ADO) MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

14.0 / 25

3.7 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

14.6 / 17

2.4 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

17.7 / 20

5.6 above avg 12.1

AdoptionLog-scaled stars · package downloads

7.9 / 20

0.7 above avg 7.2

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade C → B

2026-09-23

Rank Moved

Rank dropped 66 spots (#329 → #395)

Maintainer Checklist

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Compare with another agent Get email alerts for Azure DevOps (ADO) View MCP Servers Report missing data

76.0

Activity sub-score · out of 100

#239

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 C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

2.0k

Forks

653

Last Push

2026-09-25

yesterday

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #399

Analysis

Activity Inputs

76.0 / 100

StarsRepository reach

19.8 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

18.1 / 25

CommunityFork signal

13.1 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

7.2 / 10

OpenSSF Scorecard · scanned Sep 24, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 6

CI-Tests 9

CII-Best-Practices 0

Code-Review 10

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 8

SAST 9

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Common questions about Azure DevOps (ADO)

Azure DevOps (ADO) has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Azure DevOps (ADO) publish package provenance?

No published build provenance is currently detected for Azure DevOps (ADO). This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Azure DevOps (ADO) have an OpenSSF Scorecard?

Azure DevOps (ADO) has an OpenSSF Scorecard score of 7.2/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 Azure DevOps (ADO) actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Azure DevOps (ADO) use?

Azure DevOps (ADO) ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Azure DevOps (ADO)'s commits signed?

100% of the last 100 commits to Azure DevOps (ADO) 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

Azure DevOps (ADO) 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

N/A

No package source configured

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 Azure DevOps (ADO)'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

Maintain Azure DevOps (ADO)?

For maintainers

HVTrust scores Azure DevOps (ADO) 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

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade C → B

2026-09-23

Rank Moved

Rank dropped 66 spots (#329 → #395)

2026-09-23

HVTrust Changed

HVTrust up 15.3pts (51.7 → 67.0)

2026-09-22

Newly Listed

First tracked at rank #329

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-10

Rank Moved

Rank rose 10 spots (#384 → #374)

2026-09-07

Rank Moved

Rank dropped 23 spots (#352 → #375)

2026-09-06

Rank Moved

Rank dropped 16 spots (#336 → #352)

2026-09-05

Rank Moved

Rank dropped 66 spots (#270 → #336)

2026-09-03

Rank Moved

Rank dropped 20 spots (#242 → #262)

2026-09-01

Rank Moved

Rank dropped 11 spots (#232 → #243)

2026-08-31

Rank Moved

Rank dropped 18 spots (#214 → #232)

2026-08-29

Rank Moved

Rank dropped 12 spots (#207 → #219)

2026-08-26

Scorecard Added

OSSF Scorecard: 7.6/10

2026-08-26

Grade Changed

Trust grade D → B

2026-08-26

Rank Moved

Rank rose 614 spots (#814 → #200)

2026-08-26

HVTrust Changed

HVTrust up 40.8pts (27.0 → 67.8)

2026-08-16

Rank Moved

Rank dropped 16 spots (#804 → #820)

2026-08-13

Rank Moved

Rank dropped 10 spots (#790 → #800)

2026-08-10

Rank Moved

Rank dropped 44 spots (#754 → #798)

2026-08-08

Newly Listed

First tracked at rank #750

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/azure-devops-ado.svg)](https://hvtracker.net/agents/azure-devops-ado)
            
HTML:
            <a href="https://hvtracker.net/agents/azure-devops-ado"><img src="https://hvtracker.net/badge/azure-devops-ado.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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