mt28a2P2qLHUNvO vs azure-devops-mcp — Trust Score Comparison
Side-by-side trust comparison of mt28a2P2qLHUNvO and azure-devops-mcp. Scores based on security, compliance, maintenance, popularity, and ecosystem signals.
Detailed Metric Comparison
| Metric | mt28a2P2qLHUNvO | azure-devops-mcp |
|---|---|---|
| Trust Score | 50.6/100 | 89.1/100 |
| Grade | D | A |
| Stars | 0 | 1,291 |
| Category | uncategorized | devops |
| Security | N/A | 1 |
| Compliance | 100 | 100 |
| Maintenance | N/A | 1 |
| Documentation | N/A | 1 |
| EU AI Act Risk | N/A | minimal |
| Verified | No | Yes |
Verdict
azure-devops-mcp leads with a trust score of 89.1/100 compared to mt28a2P2qLHUNvO's 50.6/100 (a 38.5-point difference). Both agents should be evaluated based on your specific requirements.
Detailed Analysis
Security
Security scores measure dependency vulnerabilities, CVE exposure, and security practices. mt28a2P2qLHUNvO scores N/A and azure-devops-mcp scores 1 on this dimension.
Maintenance & Activity
Activity scores reflect how actively each project is maintained. mt28a2P2qLHUNvO: N/A, azure-devops-mcp: 1.
Documentation
Documentation quality is evaluated based on README, API docs, and example coverage. mt28a2P2qLHUNvO: N/A, azure-devops-mcp: 1.
Community & Adoption
mt28a2P2qLHUNvO has 0 GitHub stars while azure-devops-mcp has 1,291. azure-devops-mcp has significantly broader community adoption, which typically means more Stack Overflow answers, more third-party tutorials, and faster ecosystem development.
When to Choose Each Tool
Choose mt28a2P2qLHUNvO if you need:
- Consider if it better fits your specific use case
Choose azure-devops-mcp if you need:
- Higher overall trust score — more reliable for production use
- Stronger security profile with fewer known vulnerabilities
- More actively maintained with faster release cadence
- Larger community (1,291 vs 0 stars)
- Better documentation for faster onboarding
Switching from mt28a2P2qLHUNvO to azure-devops-mcp (or vice versa)
When migrating between mt28a2P2qLHUNvO and azure-devops-mcp, consider these factors:
- API Compatibility: mt28a2P2qLHUNvO (uncategorized) and azure-devops-mcp (devops) serve different categories, so migration may require significant refactoring.
- Security Review: Run a security audit after migration. Check the mt28a2P2qLHUNvO safety report and azure-devops-mcp safety report for known issues.
- Testing: Ensure your test suite covers all integration points before switching in production.
- Community Support: mt28a2P2qLHUNvO has 0 stars and azure-devops-mcp has 1,291. Larger communities typically mean better Stack Overflow answers and migration guides.
Related Pages
Frequently Asked Questions
Related Comparisons
Last updated: 2026-04-10 | Data refreshed weekly
Disclaimer: Nerq trust scores are automated assessments based on publicly available signals. They are not endorsements or guarantees. Always conduct your own due diligence.