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

D
Caution
55/100

mcp-server-azure-devops

An MCP server for Azure DevOps

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 VerifiedSandbox 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

Tiberriver256

Source: github_topic · also listed on mcp.so, ModelScope, github_code, github_repo_search

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 →

Install from

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: 14 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.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
// tools this server exposes46 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.

list_organizations

List all Azure DevOps organizations accessible to the current authentication

list_pipelines

List pipelines in a project

get_pipeline

Get details of a specific pipeline

list_pipeline_runs

List recent runs for a pipeline

get_pipeline_run

Get details for a specific pipeline run

download_pipeline_artifact

Download a file from a pipeline run artifact and return its textual content

pipeline_timeline

Retrieve the timeline of stages and jobs for a pipeline run, to reduce the amount of data returned, you can filter by state and result

get_pipeline_log

Retrieve a specific pipeline log using the timeline log identifier

trigger_pipeline

Trigger a pipeline run

list_projects

List all projects in an organization

get_project

Get details of a specific project

get_project_details

Get comprehensive details of a project including process, work item types, and teams

create_pull_request

Create a new pull request, including reviewers, linked work items, and optional tags

get_pull_request

Get a pull request by ID (no repositoryId required; best for Azure DevOps Server where PR IDs are project-scoped)

list_pull_requests

List pull requests in a repository

get_pull_request_comments

Get comments from a specific pull request

add_pull_request_comment

Add a comment to a pull request (repositoryId optional; derived from pullRequestId when omitted)

update_pull_request

Update an existing pull request with new properties, manage reviewers and work items, and add or remove tags

get_pull_request_changes

Get the files changed in a pull request, their unified diffs, source/target branch names, and the status of policy evaluations

get_pull_request_checks
update_pull_request_thread_status

Update the status of a comment thread in a pull request (repositoryId optional; derived from pullRequestId when omitted)

get_repository

Get details of a specific repository

get_repository_details

Get detailed information about a repository including statistics and refs

list_repositories

List repositories in a project

get_file_content

Get content of a file or directory from a repository

get_all_repositories_tree

Displays a hierarchical tree view of files and directories across multiple Azure DevOps repositories within a project, based on their default branches

get_repository_tree

Displays a hierarchical tree view of files and directories within a single repository starting from an optional path

create_branch

Create a new branch from an existing one

create_commit
list_commits

List recent commits on a branch including file-level diff content for each commit

search_code

Search for code across repositories in a project

search_wiki

Search for content across wiki pages in a project

search_work_items

Search for work items across projects in Azure DevOps

get_me

Get details of the authenticated user (id, displayName, email)

get_wikis

Get details of wikis in a project

get_wiki_page

Get the content of a wiki page

create_wiki

Create a new wiki in the project

update_wiki_page

Update content of a wiki page

list_wiki_pages

List pages within an Azure DevOps wiki

create_wiki_page

Create a new page in a wiki. If the page already exists at the specified path, it will be updated.

list_work_items

List work items in a project

get_work_item

Get details of a specific work item

create_work_item

Create a new work item

update_work_item

Update an existing work item

manage_work_item_link

Add or remove links between work items

get_work_item_comments

Get comments and discussion history for a specific work item

// known CVEs in dependencies14 high5 medium11 low

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

high@modelcontextprotocol/sdk@1.6.0GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

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

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

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

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

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

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

highaxios@1.8.3GHSA-43fc-jf86-j433

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

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_API_VERSIONAPI version to use No Latest
configAZURE_DEVOPS_AUTH_METHOD"": "azure-identity",
configAZURE_DEVOPS_DEFAULT_PROJECT"": "your-project-name"
configAZURE_DEVOPS_ORG_URL"": "https://dev.azure.com/your-organization",
configAZURE_DEVOPS_PAT"": "<YOUR_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

46/46 tools missing one or more hints — list_organizations (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_pipelines (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_pipeline (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +43 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.

Tool test coverage

Only 0/46 tools referenced in tests (0%)

Write tests that reference each tool by name so every tool has at least one test.

Secrets not written to files

1 secret value written to files

Avoid persisting secrets to disk. Keep them in memory or your secret manager.

Secrets not logged

1 secret value sent to console.log

Redact or omit secret values from log output.

Production dependencies are patched

0 critical, 14 high severity in production deps — @modelcontextprotocol/sdk@1.6.0 (high), @modelcontextprotocol/sdk@1.6.0 (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 6 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/tiberriver256/mcp-server-azure-devops?variant=verified)](https://m8ven.ai/mcp/tiberriver256/mcp-server-azure-devops)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: c43b97ccf3ba224e3291992319410adc099bc96c
code hash: d9dc333e6e42ae89d21d5da048fee6a26ff98f437af53668824c6cb4f1e681da
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