git-mcp-server vs mcp-opennutrition — Trust Score Comparison
Side-by-side trust comparison of git-mcp-server and mcp-opennutrition. Scores based on security, compliance, maintenance, popularity, and ecosystem signals.
Detailed Metric Comparison
| Metric | git-mcp-server | mcp-opennutrition |
|---|---|---|
| Trust Score | 89.0/100 | 62.0/100 |
| Grade | A | C |
| Stars | 185 | 154 |
| Category | infrastructure | infrastructure |
| Security | 0 | 0 |
| Compliance | 100 | 79 |
| Maintenance | 1 | 0 |
| Documentation | 1 | 0 |
| EU AI Act Risk | N/A | minimal |
| Verified | Yes | No |
Verdict
git-mcp-server leads with a trust score of 89.0/100 compared to mcp-opennutrition's 62.0/100 (a 27.0-point difference). git-mcp-server scores higher on compliance (100 vs 79), maintenance (1 vs 0). Both agents should be evaluated based on your specific requirements.
Detailed Analysis
Security
git-mcp-server leads on security with a score of 0/100 compared to mcp-opennutrition's 0/100. This score reflects dependency vulnerability analysis, known CVE exposure, and security best practices. A higher security score means fewer known vulnerabilities and better security hygiene in the codebase.
Maintenance & Activity
git-mcp-server demonstrates stronger maintenance activity (1/100 vs 0/100). This metric captures commit frequency, issue response times, and release cadence. Actively maintained tools receive faster security patches and are less likely to accumulate technical debt.
Documentation
git-mcp-server has better documentation (1/100 vs 0/100). Good documentation reduces onboarding time and helps teams adopt the tool safely. This score evaluates README completeness, API documentation, code examples, and tutorial availability.
Community & Adoption
git-mcp-server has 185 GitHub stars while mcp-opennutrition has 154. Both tools have comparable community sizes, suggesting similar levels of ecosystem support and third-party resources.
When to Choose Each Tool
Choose git-mcp-server if you need:
- Higher overall trust score — more reliable for production use
- More actively maintained with faster release cadence
- Larger community (185 vs 154 stars)
- Better documentation for faster onboarding
Choose mcp-opennutrition if you need:
- Consider if it better fits your specific use case
Switching from git-mcp-server to mcp-opennutrition (or vice versa)
When migrating between git-mcp-server and mcp-opennutrition, consider these factors:
- API Compatibility: git-mcp-server (infrastructure) and mcp-opennutrition (infrastructure) share similar interfaces since they are in the same category.
- Security Review: Run a security audit after migration. Check the git-mcp-server safety report and mcp-opennutrition safety report for known issues.
- Testing: Ensure your test suite covers all integration points before switching in production.
- Community Support: git-mcp-server has 185 stars and mcp-opennutrition has 154. Larger communities typically mean better Stack Overflow answers and migration guides.
Related Pages
Frequently Asked Questions
Related Comparisons
Last updated: 2026-05-09 | 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.