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