Azure DevOps (tiberriver256) MCP Server
@tiberriver256/mcp-server-azure-devops
npm
v0.1.46
Source verified
Published by tiberriver256 — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
Reference MCP server for interacting with Azure DevOps.
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 − 6 = 94. 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 |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
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 2
high Shell/command execution in server code (dist/server.spec.e2e.js)MTC-SRC-002
In the server's implementation (`dist/server.spec.e2e.js:8`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: lient/stdio.js"); const child_process_1 = require("child_process"); const path_1 = require("path"); const dotenv_1 = __i
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/server.spec.e2e.js
high Shell/command execution in server code (dist/setup-env.spec.unit.js)MTC-SRC-002
In the server's implementation (`dist/setup-env.spec.unit.js:6`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: require("path"); const child_process_1 = require("child_process"); describe('setup_env.sh', () => { it('writes PAT
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/setup-env.spec.unit.js
Tools 5
Each tool and what it can reach — statically extracted from the published source.
Branch Contentno sensitive capabilityCommit Contentno sensitive capabilityPull Request Contentno sensitive capabilityRepository Contentno sensitive capabilityTag Contentno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (5 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 |
|---|---|---|---|---|
v0.1.46 latest |
A 94/100 | 2 | 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 @tiberriver256/mcp-server-azure-devops --onlineOther implementations of Azure DevOps 16
Independent packages implementing the same tool, scanned with the same engine. Compare all 17 side by side →
MCP server for Azure DevOps Server 2022 / TFS - READ-ONLY access to builds, work items, releases, git, pipelines, and test results
MCP server for interacting with Azure DevOps
MCP server for interacting with Azure DevOps
MCP server for Azure DevOps integration with wikis, test plans, and work items
MCP server for Azure DevOps agent and queue management
MCP server for Azure DevOps Work Item Tracking integration
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.