Amazon Shopping vs mcp-context-forge — Trust Score Comparison
Side-by-side trust comparison of Amazon Shopping and mcp-context-forge. Scores based on security, compliance, maintenance, popularity, and ecosystem signals.
Detailed Metric Comparison
| Metric | Amazon Shopping | mcp-context-forge |
|---|---|---|
| Trust Score | 38.9/100 | 86.4/100 |
| Grade | E | A |
| Stars | 0 | 3,477 |
| Category | uncategorized | infrastructure |
| Security | N/A | 1 |
| Compliance | N/A | 97 |
| Maintenance | N/A | 1 |
| Documentation | N/A | 1 |
| EU AI Act Risk | N/A | N/A |
| Verified | No | Yes |
Verdict
mcp-context-forge leads with a trust score of 86.4/100 compared to Amazon Shopping's 38.9/100 (a 47.5-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. Amazon Shopping scores N/A and mcp-context-forge scores 1 on this dimension.
Maintenance & Activity
Activity scores reflect how actively each project is maintained. Amazon Shopping: N/A, mcp-context-forge: 1.
Documentation
Documentation quality is evaluated based on README, API docs, and example coverage. Amazon Shopping: N/A, mcp-context-forge: 1.
Community & Adoption
Amazon Shopping has 0 GitHub stars while mcp-context-forge has 3,477. mcp-context-forge 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 Amazon Shopping if you need:
- Consider if it better fits your specific use case
Choose mcp-context-forge 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
- Larger community (3,477 vs 0 stars)
- Better documentation for faster onboarding
Switching from Amazon Shopping to mcp-context-forge (or vice versa)
When migrating between Amazon Shopping and mcp-context-forge, consider these factors:
- API Compatibility: Amazon Shopping (uncategorized) and mcp-context-forge (infrastructure) serve different categories, so migration may require significant refactoring.
- Security Review: Run a security audit after migration. Check the Amazon Shopping safety report and mcp-context-forge safety report for known issues.
- Testing: Ensure your test suite covers all integration points before switching in production.
- Community Support: Amazon Shopping has 0 stars and mcp-context-forge has 3,477. Larger communities typically mean better Stack Overflow answers and migration guides.
Related Pages
Frequently Asked Questions
Related Comparisons
Last updated: 2026-09-27 | 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.