litellm vs github-mcp-server — Trust Score Comparison
Side-by-side trust comparison of litellm and github-mcp-server. Scores based on security, compliance, maintenance, popularity, and ecosystem signals.
Detailed Metric Comparison
| Metric | litellm | github-mcp-server |
|---|---|---|
| Trust Score | 78.0/100 | 67.6/100 |
| Grade | B | B- |
| Stars | 36,444 | 27,114 |
| Category | infrastructure | infrastructure |
| Security | 0 | 1 |
| Compliance | 80 | 100 |
| Maintenance | 1 | 1 |
| Documentation | 0 | 1 |
| EU AI Act Risk | minimal | minimal |
| Verified | Yes | No |
Verdict
litellm leads with a trust score of 78.0/100 compared to github-mcp-server's 67.6/100 (a 10.4-point difference). Both agents should be evaluated based on your specific requirements.
Detailed Analysis
Security
github-mcp-server leads on security with a score of 1/100 compared to litellm'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
litellm demonstrates stronger maintenance activity (1/100 vs 1/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
github-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
litellm has 36,444 GitHub stars while github-mcp-server has 27,114. Both tools have comparable community sizes, suggesting similar levels of ecosystem support and third-party resources.
When to Choose Each Tool
Choose litellm if you need:
- Higher overall trust score — more reliable for production use
- Larger community (36,444 vs 27,114 stars)
Choose github-mcp-server if you need:
- Stronger security profile with fewer known vulnerabilities
- Better documentation for faster onboarding
Switching from litellm to github-mcp-server (or vice versa)
When migrating between litellm and github-mcp-server, consider these factors:
- API Compatibility: litellm (infrastructure) and github-mcp-server (infrastructure) share similar interfaces since they are in the same category.
- Security Review: Run a security audit after migration. Check the litellm safety report and github-mcp-server safety report for known issues.
- Testing: Ensure your test suite covers all integration points before switching in production.
- Community Support: litellm has 36,444 stars and github-mcp-server has 27,114. Larger communities typically mean better Stack Overflow answers and migration guides.
Related Pages
Frequently Asked Questions
Related Comparisons
Last updated: 2026-04-19 | 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.