d2l-zh vs awesome-mcp-servers — Trust Score Comparison
Side-by-side trust comparison of d2l-zh and awesome-mcp-servers. Scores based on security, compliance, maintenance, popularity, and ecosystem signals.
Detailed Metric Comparison
| Metric | d2l-zh | awesome-mcp-servers |
|---|---|---|
| Trust Score | 51.2/100 | 63.9/100 |
| Grade | C- | C+ |
| Stars | 75,716 | 81,364 |
| Category | AI tool | infrastructure |
| Security | 0 | 0 |
| Compliance | 92 | 100 |
| Maintenance | 0 | 1 |
| Documentation | 0 | 0 |
| EU AI Act Risk | N/A | minimal |
| Verified | No | No |
Verdict
awesome-mcp-servers leads with a trust score of 63.9/100 compared to d2l-zh's 51.2/100 (a 12.7-point difference). awesome-mcp-servers scores higher on compliance (100 vs 92), maintenance (1 vs 0). Both agents should be evaluated based on your specific requirements.
Detailed Analysis
Security
d2l-zh leads on security with a score of 0/100 compared to awesome-mcp-servers'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
awesome-mcp-servers 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
d2l-zh has better documentation (0/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
d2l-zh has 75,716 GitHub stars while awesome-mcp-servers has 81,364. Both tools have comparable community sizes, suggesting similar levels of ecosystem support and third-party resources.
When to Choose Each Tool
Choose d2l-zh if you need:
- Consider if it better fits your specific use case
Choose awesome-mcp-servers if you need:
- Higher overall trust score — more reliable for production use
- More actively maintained with faster release cadence
- Larger community (81,364 vs 75,716 stars)
Switching from d2l-zh to awesome-mcp-servers (or vice versa)
When migrating between d2l-zh and awesome-mcp-servers, consider these factors:
- API Compatibility: d2l-zh (AI tool) and awesome-mcp-servers (infrastructure) serve different categories, so migration may require significant refactoring.
- Security Review: Run a security audit after migration. Check the d2l-zh safety report and awesome-mcp-servers safety report for known issues.
- Testing: Ensure your test suite covers all integration points before switching in production.
- Community Support: d2l-zh has 75,716 stars and awesome-mcp-servers has 81,364. Larger communities typically mean better Stack Overflow answers and migration guides.
Related Pages
Frequently Asked Questions
Related Comparisons
Last updated: 2026-05-13 | 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.