Skills/PyPI/mcp-devops-onpremise

mcp-devops-onpremise@2.2.0

VERIFIED· not started

Publisher claims: "MCP server for Azure DevOps Server (formerly Team Foundation Server, TFS): repositories, pull requests, work items, and wikis. Not for Azure DevOps Services." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher zwitbaum · publishing for 184 daysInstalls 409Last detonated 3d ago
$claude mcp add mcp-devops-onpremise -- uvx mcp-devops-onpremise
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
DEVOPS_AUTH_DEBUGDEVOPS_PASSWORDDEVOPS_PATDEVOPS_TOKENConfiguration, not credentials: DEVOPS_API_URL, DEVOPS_USERNAME, MCP_HOST, MCP_PATH, MCP_PORT, MCP_TRANSPORT
Where it talks to
no vendor host named in the code
What the honeypot saw
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard. It asks for DEVOPS_AUTH_DEBUG, DEVOPS_PASSWORD, DEVOPS_PAT, DEVOPS_TOKEN and talks to its vendor. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.

$vet-skills run --net declared -- uvx mcp-devops-onpremise

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-11 and scored it 89/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.2sprocessdependency install exit 1 ·
0.2sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.2sprocessscript backend runs setup only
0.2sprocessno install scripts to re-run

Static findings

LOW
Unpinned dependency.github/workflows/publish-smithery.yml:18 · Unpinned dependencyrun: npm install -g smithery@latestFix: Pin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.
AST06
HIGH
Access to sensitive file pathssrc/mcp_devops/shared.py:12 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Load .env from repo root (no-op if file doesn't exist)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

Cost to the agent

Instructions loaded
≈1,234 tok
2 files · 53 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for mcp-devops-onpremise@2.2.0 as of 3d ago. This is the package itself, not its dependencies.