Azure DevOps (slorenzot) MCP Server
@slorenzot/mcp-azure
npm
v2.8.0
Published by @slorenzot — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
Azure DevOps server with robust error handling, .mcp.json support, and concurrent attachment handling.
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 − 5 = 95. 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:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
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
Tools 39
Each tool and what it can reach — statically extracted from the published source.
ado_create_pull_requestnetwork egressado_create_pull_request_threadnetwork egressado_abandon_pull_requestno sensitive capabilityado_add_attachmentno sensitive capabilityado_add_commentno sensitive capabilityado_add_pull_request_reviewerno sensitive capabilityado_add_work_item_linkno sensitive capabilityado_approve_pull_requestno sensitive capabilityado_complete_pull_requestno sensitive capabilityado_configureno sensitive capability
Show 29 more tools ↓
ado_create_work_itemno sensitive capabilityado_delete_attachmentno sensitive capabilityado_delete_work_itemno sensitive capabilityado_get_attachmentsno sensitive capabilityado_get_commentsno sensitive capabilityado_get_pull_requestno sensitive capabilityado_get_pull_request_commitsno sensitive capabilityado_get_pull_request_reviewersno sensitive capabilityado_get_pull_request_threadsno sensitive capabilityado_get_pull_request_work_itemsno sensitive capabilityado_get_repositoryno sensitive capabilityado_get_work_itemno sensitive capabilityado_get_work_item_type_fieldsno sensitive capabilityado_list_areasno sensitive capabilityado_list_branchesno sensitive capabilityado_list_iterationsno sensitive capabilityado_list_pull_requestsno sensitive capabilityado_list_repositoriesno sensitive capabilityado_query_areano sensitive capabilityado_query_sprintno sensitive capabilityado_query_wiqlno sensitive capabilityado_reject_pull_requestno sensitive capabilityado_remove_work_item_linkno sensitive capabilityado_reply_to_pull_request_threadno sensitive capabilityado_search_usersno sensitive capabilityado_update_pull_requestno sensitive capabilityado_update_pull_request_thread_statusno sensitive capabilityado_update_work_itemno sensitive capabilityado_upload_attachmentno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (39 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v2.8.0 latest |
A 95/100 | 0 | 1.13.0 | 2026-08-25 |
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.
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 @slorenzot/mcp-azure --onlineOther implementations of Azure DevOps 3
Independent packages implementing the same tool, scanned with the same engine. Compare all 4 side by side →
[](https://smithery.ai/server/@Streen9/azure-mcp)
Azure MCP Server - Model Context Protocol implementation for Azure
Security scan results for the Azure (npm) MCP server.
More in Cloud & DevOps
Operator control CLI for AdGuard Home with an MCP adapter
interacting with Aliyun (Alibaba Cloud) services through This MCP server provides tools.
MCP server for the Aspro.Cloud REST API
MCP server for Atlassian Confluence and Jira Cloud APIs
AuroraCloud-first MCP server that exposes AuroraDocs workspace data to Claude Desktop and other AI agents
The official AWS Knowledge Base retrieval server using Bedrock Agent Runtime.