GenPark Git Commit Conventional Semantic Linter vs @azure-devops/mcp
GenPark Git Commit Conventional Semantic Linter lists no tools and @azure-devops/mcp lists no tools and runs locally.
| Fact | GenPark Git Commit Conventional Semantic Linterio.github.alphaparkinc/genpark-git-commit-conventional-semantic-linter-skill | @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 | Not known | Local |
| Needs first | – | Node.js |
| Licence | Not stated | MIT |
| Latest version | 1.0.1 | 2.11.0 |
| Known advisories | Not checked yet | 0 |
| Works in | No install config | 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 GenPark Git Commit Conventional Semantic Linter | 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 GenPark Git Commit Conventional Semantic Linter with othersCompare @azure-devops/mcp with others