gcloud-mcp vs health-ai-assistant-backend — Trust Score Comparison
Side-by-side trust comparison of gcloud-mcp and health-ai-assistant-backend. Scores based on security, compliance, maintenance, popularity, and ecosystem signals.
Detailed Metric Comparison
| Metric | gcloud-mcp | health-ai-assistant-backend |
|---|---|---|
| Trust Score | 81.2/100 | 44.8/100 |
| Grade | D | E |
| Stars | 0 | 0 |
| Category | infrastructure | uncategorized |
| Security | 1 | N/A |
| Compliance | 87 | 67 |
| Maintenance | 1 | N/A |
| Documentation | 1 | N/A |
| EU AI Act Risk | minimal | N/A |
| Verified | Yes | No |
Verdict
gcloud-mcp leads with a trust score of 81.2/100 compared to health-ai-assistant-backend's 44.8/100 (a 36.4-point difference). gcloud-mcp scores higher on compliance (87 vs 67). Both agents should be evaluated based on your specific requirements.
Detailed Analysis
Security
Security scores measure dependency vulnerabilities, CVE exposure, and security practices. gcloud-mcp scores 1 and health-ai-assistant-backend scores N/A on this dimension.
Maintenance & Activity
Activity scores reflect how actively each project is maintained. gcloud-mcp: 1, health-ai-assistant-backend: N/A.
Documentation
Documentation quality is evaluated based on README, API docs, and example coverage. gcloud-mcp: 1, health-ai-assistant-backend: N/A.
Community & Adoption
gcloud-mcp has 0 GitHub stars while health-ai-assistant-backend has 0. Both tools have comparable community sizes, suggesting similar levels of ecosystem support and third-party resources.
When to Choose Each Tool
Choose gcloud-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
- Better documentation for faster onboarding
Choose health-ai-assistant-backend if you need:
- Consider if it better fits your specific use case
Switching from gcloud-mcp to health-ai-assistant-backend (or vice versa)
When migrating between gcloud-mcp and health-ai-assistant-backend, consider these factors:
- API Compatibility: gcloud-mcp (infrastructure) and health-ai-assistant-backend (uncategorized) serve different categories, so migration may require significant refactoring.
- Security Review: Run a security audit after migration. Check the gcloud-mcp safety report and health-ai-assistant-backend safety report for known issues.
- Testing: Ensure your test suite covers all integration points before switching in production.
- Community Support: gcloud-mcp has 0 stars and health-ai-assistant-backend has 0. Larger communities typically mean better Stack Overflow answers and migration guides.
Related Pages
Frequently Asked Questions
Related Comparisons
Last updated: 2026-06-21 | 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.