mcpproxy-go vs monolithic-nl2sql-ai-agent-streamlit — Trust Score Comparison
Side-by-side trust comparison of mcpproxy-go and monolithic-nl2sql-ai-agent-streamlit. Scores based on security, compliance, maintenance, popularity, and ecosystem signals.
proxy — Nerq Trust Score 69.2/100 (B-). lithic — Nerq Trust Score 79.2/100 (B+). lithic leads by 10.0 points.
Detailed Score Analysis
| Dimension | proxy | lithic |
|---|---|---|
| Security | 90/100 | 90/100 |
| Maintenance | 66/100 | 100/100 |
| Popularity | 75/100 | 60/100 |
| Quality | 65/100 | 80/100 |
| Community | 40/100 | 45/100 |
Five-dimension Nerq trust breakdown (registries: npm / npm). Scored equally weighted across security, maintenance, popularity, quality, community.
Detailed Metric Comparison
| Metric | mcpproxy-go | monolithic-nl2sql-ai-agent-streamlit |
|---|---|---|
| Trust Score | 79.1/100 | 62.0/100 |
| Grade | B | C |
| Stars | 156 | 3 |
| Category | infrastructure | data |
| Security | 0 | 0 |
| Compliance | 97 | 80 |
| Maintenance | 1 | 1 |
| Documentation | 1 | 0 |
| EU AI Act Risk | minimal | N/A |
| Verified | Yes | No |
Verdict
mcpproxy-go leads with a trust score of 79.1/100 compared to monolithic-nl2sql-ai-agent-streamlit's 62.0/100 (a 17.1-point difference). mcpproxy-go scores higher on compliance (97 vs 80), maintenance (1 vs 1). Both agents should be evaluated based on your specific requirements.
Detailed Score Analysis
Five-dimensional trust breakdown for mcpproxy-go (npm) and monolithic-nl2sql-ai-agent-streamlit (npm) from Nerq’s enrichment pipeline. All 5 dimensions scored on 0–100 scales, refreshed every 7 days, covering 5M+ indexed assets across 14 registries.
| Dimension | mcpproxy-go | monolithic-nl2sql-ai-agent-streamlit |
|---|---|---|
| Security | 90/100 | 90/100 |
| Maintenance | 66/100 | 100/100 |
| Popularity | 75/100 | 60/100 |
| Quality | 65/100 | 80/100 |
| Community | 40/100 | 45/100 |
5-Dimension Breakdown
Security — mcpproxy-go vs monolithic-nl2sql-ai-agent-streamlit
Security aggregates dependency vulnerability scans, known CVE exposure, supply-chain hygiene, and adherence to security best practices. On this dimension mcpproxy-go scores 90/100 (top-tier) while monolithic-nl2sql-ai-agent-streamlit scores 90/100 (top-tier). The two are effectively tied on security (both at 90/100). The mcpproxy-go figure is derived from its npm registry footprint; the monolithic-nl2sql-ai-agent-streamlit figure from npm. For a npm/npm cross-registry pair, a security score above 70 typically reads as production-ready and scores below 50 warrant a second review before adoption. A score above 85 implies a clean dependency tree with 0 critical CVEs in the last 90 days; 70–84 tolerates 1–2 medium-severity issues; below 55 usually flags 3+ unresolved advisories. Given the current 90/100 for mcpproxy-go and 90/100 for monolithic-nl2sql-ai-agent-streamlit, the combined midpoint is 90.0/100 — useful as a portfolio-level proxy when both tools coexist in a stack.
Maintenance — mcpproxy-go vs monolithic-nl2sql-ai-agent-streamlit
Maintenance captures commit cadence, issue turnaround, release frequency, and the health of the project’s active contributor base. On this dimension mcpproxy-go scores 66/100 (mid-band) while monolithic-nl2sql-ai-agent-streamlit scores 100/100 (top-tier). monolithic-nl2sql-ai-agent-streamlit leads by 34 points (100/100 vs 66/100), a spread wide enough that teams should weight maintenance heavily when choosing. The mcpproxy-go figure is derived from its npm registry footprint; the monolithic-nl2sql-ai-agent-streamlit figure from npm. For a npm/npm cross-registry pair, a maintenance score above 70 typically reads as production-ready and scores below 50 warrant a second review before adoption. Scores above 80 correspond to release cadences of 30 days or less and median issue-response times under 7 days; below 50 often means no release in 180+ days. Given the current 66/100 for mcpproxy-go and 100/100 for monolithic-nl2sql-ai-agent-streamlit, the combined midpoint is 83.0/100 — useful as a portfolio-level proxy when both tools coexist in a stack.
Popularity — mcpproxy-go vs monolithic-nl2sql-ai-agent-streamlit
Popularity measures adoption signals—weekly downloads, dependent packages, GitHub stars, and cross-registry citation density. On this dimension mcpproxy-go scores 75/100 (strong) while monolithic-nl2sql-ai-agent-streamlit scores 60/100 (mid-band). mcpproxy-go leads by 15 points (75/100 vs 60/100), a spread wide enough that teams should weight popularity heavily when choosing. The mcpproxy-go figure is derived from its npm registry footprint; the monolithic-nl2sql-ai-agent-streamlit figure from npm. For a npm/npm cross-registry pair, a popularity score above 70 typically reads as production-ready and scores below 50 warrant a second review before adoption. A score of 90+ indicates the top 1% of the registry by dependent count or weekly downloads; 70–89 is the top 10%; below 40 suggests fewer than 500 weekly downloads. Given the current 75/100 for mcpproxy-go and 60/100 for monolithic-nl2sql-ai-agent-streamlit, the combined midpoint is 67.5/100 — useful as a portfolio-level proxy when both tools coexist in a stack.
Quality — mcpproxy-go vs monolithic-nl2sql-ai-agent-streamlit
Quality evaluates documentation completeness, test coverage indicators, typed-API availability, and the presence of examples or tutorials. On this dimension mcpproxy-go scores 65/100 (mid-band) while monolithic-nl2sql-ai-agent-streamlit scores 80/100 (strong). monolithic-nl2sql-ai-agent-streamlit leads by 15 points (80/100 vs 65/100), a spread wide enough that teams should weight quality heavily when choosing. The mcpproxy-go figure is derived from its npm registry footprint; the monolithic-nl2sql-ai-agent-streamlit figure from npm. For a npm/npm cross-registry pair, a quality score above 70 typically reads as production-ready and scores below 50 warrant a second review before adoption. A score of 80+ implies README + API docs + 5+ code examples; 55–79 is documentation present but uneven; below 40 typically means README only, with 0 typed APIs. Given the current 65/100 for mcpproxy-go and 80/100 for monolithic-nl2sql-ai-agent-streamlit, the combined midpoint is 72.5/100 — useful as a portfolio-level proxy when both tools coexist in a stack.
Community — mcpproxy-go vs monolithic-nl2sql-ai-agent-streamlit
Community looks at contributor breadth, issue-response participation, Stack Overflow answer volume, and third-party tutorial ecosystem. On this dimension mcpproxy-go scores 40/100 (below-average) while monolithic-nl2sql-ai-agent-streamlit scores 45/100 (below-average). monolithic-nl2sql-ai-agent-streamlit leads by 5 points (45/100 vs 40/100), a moderate gap that matters when community is a hard requirement. The mcpproxy-go figure is derived from its npm registry footprint; the monolithic-nl2sql-ai-agent-streamlit figure from npm. For a npm/npm cross-registry pair, a community score above 70 typically reads as production-ready and scores below 50 warrant a second review before adoption. Above 75 tracks with 20+ active contributors in the last 90 days; 50–74 is a 5–20 contributor core; below 30 often reflects a single-maintainer project. Given the current 40/100 for mcpproxy-go and 45/100 for monolithic-nl2sql-ai-agent-streamlit, the combined midpoint is 42.5/100 — useful as a portfolio-level proxy when both tools coexist in a stack.
Score-Card Summary
Across the 5 measured dimensions, mcpproxy-go averages 67.2/100 (range 40–90) and monolithic-nl2sql-ai-agent-streamlit averages 75.0/100 (range 45–100). mcpproxy-go leads on 1 dimensions, monolithic-nl2sql-ai-agent-streamlit leads on 3, with 1 tied.
| Band | Range | mcpproxy-go dims | monolithic-nl2sql-ai-agent-streamlit dims |
|---|---|---|---|
| Top-tier | 85–100 | 1 | 2 |
| Strong | 70–85 | 1 | 1 |
| Mid-band | 55–70 | 2 | 1 |
| Below-avg | 40–55 | 1 | 1 |
| Weak | 0–40 | 0 | 0 |
Scoring scale: 0–39 weak, 40–54 below-average, 55–69 mid-band, 70–84 strong, 85–100 top-tier. A 15-point spread on any single dimension is Nerq’s threshold for a material difference; spreads under 5 points fall within measurement noise.
Head-to-Head Deltas
| Dimension | mcpproxy-go | monolithic-nl2sql-ai-agent-streamlit | Delta | Leader |
|---|---|---|---|---|
| Security | 90 | 90 | +0 | tied |
| Maintenance | 66 | 100 | -34 | monolithic-nl2sql-ai-agent-streamlit |
| Popularity | 75 | 60 | +15 | mcpproxy-go |
| Quality | 65 | 80 | -15 | monolithic-nl2sql-ai-agent-streamlit |
| Community | 40 | 45 | -5 | monolithic-nl2sql-ai-agent-streamlit |
Combined 5-dimension average: mcpproxy-go 67.2/100, monolithic-nl2sql-ai-agent-streamlit 75.0/100, overall spread -7.8 points.
- Max spread: 34 points on Maintenance
- Min spread: 0 points on Security
- Dimensions within 10 points: 2/5
- mcpproxy-go above 70 on: 2/5 dimensions
- monolithic-nl2sql-ai-agent-streamlit above 70 on: 3/5 dimensions
Detailed Analysis
Security
mcpproxy-go leads on security with a score of 0/100 compared to monolithic-nl2sql-ai-agent-streamlit'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
mcpproxy-go demonstrates stronger maintenance activity (1/100 vs 1/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
mcpproxy-go has better documentation (1/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
mcpproxy-go has 156 GitHub stars while monolithic-nl2sql-ai-agent-streamlit has 3. 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 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 3 stars)
- Better documentation for faster onboarding
Choose monolithic-nl2sql-ai-agent-streamlit if you need:
- Consider if it better fits your specific use case
Switching from mcpproxy-go to monolithic-nl2sql-ai-agent-streamlit (or vice versa)
When migrating between mcpproxy-go and monolithic-nl2sql-ai-agent-streamlit, consider these factors:
- API Compatibility: mcpproxy-go (infrastructure) and monolithic-nl2sql-ai-agent-streamlit (data) serve different categories, so migration may require significant refactoring.
- Security Review: Run a security audit after migration. Check the mcpproxy-go safety report and monolithic-nl2sql-ai-agent-streamlit safety report for known issues.
- Testing: Ensure your test suite covers all integration points before switching in production.
- Community Support: mcpproxy-go has 156 stars and monolithic-nl2sql-ai-agent-streamlit has 3. Larger communities typically mean better Stack Overflow answers and migration guides.
Related Pages
Frequently Asked Questions
Related Comparisons
Last updated: 2026-05-06 | 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.