azure-devops-mcp-server (wuhuangjia/azure-devops-mcp-server) is an MCP server listed on the M8ven Trust Index. It scores 51 out of 100, grade D. It declares 13 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
51/100

azure-devops-mcp-server

Enables natural language interaction with Azure DevOps to manage work items, projects, and Git commit links via the REST API. It supports comprehensive operations including creating, searching, batch updating work items, and managing attachments.

→ wuhuangjia/azure-devops-mcp-server· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

wuhuangjia

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
⚠️
Known vulnerabilities in dependencies: 13 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
// tools this server exposes13 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

create_work_item

在 Azure DevOps 中建立新的 Work Item (例如 User Story, Bug, Task)。

get_work_item_details

根據 ID 取得 Azure DevOps Work Item 的詳細資訊。

update_work_item

更新現有 Azure DevOps Work Item 的欄位 (例如狀態、指派對象)。

search_work_items

搜尋 Azure DevOps Work Items。可依專案、類型、標題、ID、狀態等條件進行篩選。

list_projects

列出 Azure DevOps 組織中的所有專案。

get_project_details

根據專案 ID 或名稱取得 Azure DevOps 專案的詳細資訊。

link_commit_to_work_item

將 Git Commit 連結到 Azure DevOps Work Item。

list_work_item_attachments

獲取指定 Azure DevOps Work Item 的附件列表，包含下載 URL。

add_issue_comment

為現有的 Azure DevOps Work Item 添加評論。

link_parent_work_item

建立 Work Item 父子關聯（將 childId 設定 parentId 為父項）

delete_work_item

刪除指定的 Azure DevOps Work Item 並將其移至回收站。

get_work_items_batch

批次獲取多個 Azure DevOps Work Items（最多200個）。

batch_update_work_items

批次更新多個 Azure DevOps Work Items。可在單一請求中執行多個建立、更新或刪除操作。

// known CVEs in dependencies13 high5 medium12 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@0.6.0GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

highaxios@1.8.4GHSA-35jp-ww65-95wh

axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `config.proxy`

highaxios@1.8.4GHSA-3g43-6gmg-66jw

axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollution Gadget in Config Merge

highaxios@1.8.4GHSA-43fc-jf86-j433

Axios is Vulnerable to Denial of Service via __proto__ Key in mergeConfig

highaxios@1.8.4GHSA-4hjh-wcwx-xvwj

Axios is vulnerable to DoS attack through lack of data size check

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configAZURE_DEVOPS_ORG_URL
configAZURE_DEVOPS_PAT
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

13/13 tools missing one or more hints — create_work_item (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_work_item_details (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); update_work_item (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +10 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tests exist

No test files found

Add tests that exercise each declared tool.

Production dependencies are patched

0 critical, 13 high severity in production deps — @modelcontextprotocol/sdk@0.6.0 (high), axios@1.8.4 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/wuhuangjia/azure-devops-mcp-server?variant=verified)](https://m8ven.ai/mcp/wuhuangjia/azure-devops-mcp-server)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: a95e4b5bbe61558cc5404b6a7193a3728596ab25
code hash: 099e364a08e9129c50f10ee473ff92f2e5024e63d59e249386d3a89cce60e2b3
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client