modelcontextprotocol vs tempenv — Trust Score Comparison
Side-by-side trust comparison of modelcontextprotocol and tempenv. Scores based on security, compliance, maintenance, popularity, and ecosystem signals.
Detailed Metric Comparison
| Metric | modelcontextprotocol | tempenv |
|---|---|---|
| Trust Score | 0.0/100 | 63.5/100 |
| Grade | C | C+ |
| Stars | 1,968 | 0 |
| Category | infrastructure | uncategorized |
| Security | N/A | 90 |
| Compliance | 100 | N/A |
| Maintenance | 0 | 50 |
| Documentation | 0 | 60 |
| EU AI Act Risk | N/A | N/A |
| Verified | No | No |
Verdict
tempenv leads with a trust score of 63.5/100 compared to modelcontextprotocol's 0.0/100 (a 63.5-point difference). tempenv scores higher on maintenance (50 vs 0). However, modelcontextprotocol has stronger community adoption (1,968 vs 0 stars). Both agents should be evaluated based on your specific requirements.
Detailed Analysis
Security
Security scores measure dependency vulnerabilities, CVE exposure, and security practices. modelcontextprotocol scores N/A and tempenv scores 90 on this dimension.
Maintenance & Activity
tempenv demonstrates stronger maintenance activity (50/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
tempenv has better documentation (60/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
modelcontextprotocol has 1,968 GitHub stars while tempenv has 0. modelcontextprotocol 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 modelcontextprotocol if you need:
- Larger community (1,968 vs 0 stars)
Choose tempenv 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
- Better documentation for faster onboarding
Switching from modelcontextprotocol to tempenv (or vice versa)
When migrating between modelcontextprotocol and tempenv, consider these factors:
- API Compatibility: modelcontextprotocol (infrastructure) and tempenv (uncategorized) serve different categories, so migration may require significant refactoring.
- Security Review: Run a security audit after migration. Check the modelcontextprotocol safety report and tempenv safety report for known issues.
- Testing: Ensure your test suite covers all integration points before switching in production.
- Community Support: modelcontextprotocol has 1,968 stars and tempenv has 0. Larger communities typically mean better Stack Overflow answers and migration guides.
Related Pages
Frequently Asked Questions
Related Comparisons
Last updated: 2026-11-11 | 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.