Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/burcusipahioglu/azure-devops-mcp-onpremInstalling this writes the configuration, not the program: `node` runs a file from the repository, so clone it first and make the path in the command match where you put it.
Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/burcusipahioglu/azure-devops-mcp-onprem/azure-devops)<a href="https://agentmods.dev/mcp/burcusipahioglu/azure-devops-mcp-onprem/azure-devops"><img src="https://agentmods.dev/badge/mcp/burcusipahioglu/azure-devops-mcp-onprem/azure-devops/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/burcusipahioglu/azure-devops-mcp-onprem/azure-devops"><img src="https://agentmods.dev/badge/mcp/burcusipahioglu/azure-devops-mcp-onprem/azure-devops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
azure-devops scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"azure-devops": {
"type": "stdio",
"command": "node",
"args": [
"dist/index.js"
],
"env": {
"AZURE_DEVOPS_ENV_FILE": "C:\\Users\\you\\.azure-devops-mcp.env"
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 12 lines scan A 9c15a1ee5e9c
azure-devops is an MCP server published in the GitHub repository burcusipahioglu/azure-devops-mcp-onprem (16 stars, last pushed 3mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
easy8-mcp
Connect AI assistants to Easy8 — read and update projects, issues, and comments. Remote server at {easy8_host}.
atlassian
MCP server "atlassian" as configured in devobsessed/code-captain. Runs locally from the @atlassian/mcp-atlassian npm package. Needs 3 environment variables to run.
imagine-mcp
MCP server for image/video understanding & generation (Gemini/OpenAI/Grok). Runs locally from the imagine-mcp Python package. Needs 4 environment variables to run.
recall
Open-source agent-memory MCP server. recall.works. Runs locally from the ai-recallworks Python package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
component-explorer
MCP server "component-explorer" as configured in microsoft/vscode. Launched with npm exec --no -- component-explorer mcp -p ./test/componentFixtures/component-ex.