72hours security check vs @azure-devops/mcp
72hours security check lists no tools and runs remotely and @azure-devops/mcp lists no tools and runs locally.
| Fact | 72hours security checkio.github.maebsy/72hours | @azure-devops/mcpio.github.microsoft/azure-devops-mcp |
|---|---|---|
| Score | Not checked yet | Not checked yet |
| Status | Not checked yet | Not checked yet |
| Tools | 0 | 0 |
| Can write data | No tools listed | No tools listed |
| Runs | Remote | Local |
| Needs first | – | Node.js |
| Licence | Not stated | MIT |
| Latest version | 1.1.0 | 2.11.0 |
| Known advisories | Not checked yet | 0 |
| Works in | Claude Desktop, Claude Code, Cursor, VS Code, Devin Desktop, Zed, Cline, Continue, Goose, LM Studio, Gemini CLI, Codex, oterm, Agenvoy, Amp, AnythingLLM, Augment Code, Bob Shell, ECA, Kiro, Kiro CLI | Claude Desktop, Claude Code, Cursor, VS Code, Devin Desktop, Zed, Cline, Continue, Goose, LM Studio, Gemini CLI, Codex, mcp-client-cli, oterm, TUUI, BoltAI, Agenvoy, Amp, AnythingLLM, Augment Code, Bob Shell, ECA, Kiro, Kiro CLI |
| Downloads last week | Not known | Not known |
| Install | Install 72hours security check | Install @azure-devops/mcp |
Scores and status come with our own checks, which have not run on these servers yet. The rest is from the publishers' registry entries, package registries and advisory databases.
Compare 72hours security check with othersCompare @azure-devops/mcp with others