Azure Devops Mcp Onprem MCP Server

@burcusg/azure-devops-mcp-onprem npm v1.5.0

Published by @burcusg — 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 for on-premises Azure DevOps Server (TFS). Covers Work Items, Git, TFVC (shelvesets, changesets, labels), Pipelines, Wiki, and Test Plans. Bridges Claude, GitHub Copilot, Cursor, Antigravity, and other AI assistants.

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 1

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([tfvc_browse]) co-exist with external-action tools ([create_pull_request]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [tfvc_browse] → sinks [create_pull_request]

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow tfvc_browse → create_pull_request

Tools 50

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

  • create_pull_requestnetwork egress
  • tfvc_browseingests untrusted input
  • add_pull_request_commentno sensitive capability
  • add_test_cases_to_suiteno sensitive capability
  • add_work_item_commentno sensitive capability
  • compare_branchesno sensitive capability
  • create_work_itemno sensitive capability
  • get_buildno sensitive capability
  • get_commit_changesno sensitive capability
  • get_current_userno sensitive capability
Show 40 more tools ↓
  • get_file_contentno sensitive capability
  • get_my_sprint_itemsno sensitive capability
  • get_pull_requestno sensitive capability
  • get_pull_request_commentsno sensitive capability
  • get_test_planno sensitive capability
  • get_test_resultsno sensitive capability
  • get_wiki_pageno sensitive capability
  • get_work_itemno sensitive capability
  • get_work_item_changesetsno sensitive capability
  • get_work_item_commentsno sensitive capability
  • get_work_item_commitsno sensitive capability
  • get_work_item_historyno sensitive capability
  • get_work_item_statisticsno sensitive capability
  • link_work_itemsno sensitive capability
  • list_branchesno sensitive capability
  • list_build_definitionsno sensitive capability
  • list_buildsno sensitive capability
  • list_commitsno sensitive capability
  • list_pull_requestsno sensitive capability
  • list_releasesno sensitive capability
  • list_repositoriesno sensitive capability
  • list_test_casesno sensitive capability
  • list_test_plansno sensitive capability
  • list_test_runsno sensitive capability
  • list_test_suitesno sensitive capability
  • list_wiki_pagesno sensitive capability
  • list_wikisno sensitive capability
  • query_work_itemsno sensitive capability
  • queue_buildno sensitive capability
  • search_work_items_by_tagno sensitive capability
  • tfvc_get_changesetno sensitive capability
  • tfvc_get_changeset_changesno sensitive capability
  • tfvc_get_fileno sensitive capability
  • tfvc_get_shelvesetno sensitive capability
  • tfvc_get_shelveset_fileno sensitive capability
  • tfvc_list_branchesno sensitive capability
  • tfvc_list_changesetsno sensitive capability
  • tfvc_list_labelsno sensitive capability
  • tfvc_list_shelvesetsno sensitive capability
  • update_work_itemno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

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.5.0 latest A 96/100 1 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/burcusg-azure-devops-mcp-onprem/badge.svg)](https://mcptrustchecker.com/registry/burcusg-azure-devops-mcp-onprem)
HTML
<a href="https://mcptrustchecker.com/registry/burcusg-azure-devops-mcp-onprem"><img src="https://mcptrustchecker.com/registry/burcusg-azure-devops-mcp-onprem/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/burcusg-azure-devops-mcp-onprem/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 @burcusg/azure-devops-mcp-onprem --online

Use the free API → How scoring works

More in Developer Tools