Loading the registry…
A Model Context Protocol (MCP) server for Azure DevOps integration. Create work items, pull requests, and manage Azure DevOps workflows through AI assistants.
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
2 critical findings reported by cisco-skill-scanner, agent-audit-kit. The composite score alone does not reflect this — read the per-scanner reports below.
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- ado-mcp-server
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
5 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v1.4.0
0 findings · 0.5s
v2.0.11
16 findings · 6.2s
v0.3.74
8 findings · 0.7s
v0.1.0
10 findings · 3.0s
v0.1.0
0 findings · 3.0s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 1.7s
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 20, 2026 | Scan Halted | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicable | rejected |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
Out of 34 findings across every scanner that examined this package. None of the 2 findings rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 16 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
The model could have called any of these a false positive and did not.
10 opt.nerlo-rules.nerlo-js-secret-to-network-egress
Files: /repo/server.js · reported by nerlo-behavioral
2 AAK-OAUTH-3P-001
Files: package.json, requirements.txt · reported by agent-audit-kit
1 AAK-ANTHROPIC-SDK-001
Files: server.js · reported by agent-audit-kit
1 AAK-DNS-REBIND-002
Files: package.json · reported by agent-audit-kit
1 AAK-MCP-STDIO-CMD-INJ-002
Files: server.js · reported by agent-audit-kit
1 AAK-SUPPLY-004
Files: package.json · reported by agent-audit-kit
1 COMMAND_INJECTION_JS_CHILD_PROCESS
Files: /repo/server.js · reported by cisco-skill-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
14 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: AAK-SEC-MD-001, DATA_EXFIL_JS_NETWORK, DATA_EXFIL_JS_FS_ACCESS and 1 more · Files: SECURITY.md, /repo/server.js, /repo/SKILL.md · reported by agent-audit-kit, cisco-skill-scanner
1 The model did not answer for these findings.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION · Files: /repo/SKILL.md · reported by cisco-skill-scanner
1 The model gave no reason we were willing to publish, and a verdict without one is not usable evidence.
Rules: AAK-MCP-SSRF-001 · Files: server.js · reported by agent-audit-kit
Critical command injection and secret exfiltration risks
The artifact exhibits critical command injection vulnerabilities in `server.js`, allowing for shell execution. It also has multiple high-severity findings indicating potential secret exfiltration to external networks from `server.js`. Further high-severity findings suggest credential access risks related to an SDK and potential DNS rebinding.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.