Container Use vs git-mcp-server — Trust Score Comparison

Side-by-side trust comparison of Container Use and git-mcp-server. Scores based on security, compliance, maintenance, popularity, and ecosystem signals.

Container Use scores 70.5/100 (B) while git-mcp-server scores 89.0/100 (B+) on the Nerq Trust Score. git-mcp-server leads by 18.5 points. Container Use is a uncategorized tool with 3,687 stars, Nerq Verified. git-mcp-server is a infrastructure tool with 0 stars, Nerq Verified.
70.5
B verified
Categoryuncategorized
Stars3,687
Sourcepulsemcp
vs
89.0
B+ verified
Categoryinfrastructure
Stars0
Sourcegithub
Security0
Compliance100
Maintenance1
Documentation1

Detailed Metric Comparison

Metric Container Use git-mcp-server
Trust Score70.5/10089.0/100
GradeBB+
Stars3,6870
Categoryuncategorizedinfrastructure
SecurityN/A0
ComplianceN/A100
MaintenanceN/A1
DocumentationN/A1
EU AI Act RiskN/AN/A
VerifiedYesYes

Verdict

git-mcp-server leads with a trust score of 89.0/100 compared to Container Use's 70.5/100 (a 18.5-point difference). However, Container Use has stronger community adoption (3,687 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. Container Use scores N/A and git-mcp-server scores 0 on this dimension.

Maintenance & Activity

Activity scores reflect how actively each project is maintained. Container Use: N/A, git-mcp-server: 1.

Documentation

Documentation quality is evaluated based on README, API docs, and example coverage. Container Use: N/A, git-mcp-server: 1.

Community & Adoption

Container Use has 3,687 GitHub stars while git-mcp-server has 0. Container Use 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 Container Use if you need:

  • Larger community (3,687 vs 0 stars)

Choose git-mcp-server if you need:

  • Higher overall trust score — more reliable for production use
  • More actively maintained with faster release cadence
  • Better documentation for faster onboarding

Switching from Container Use to git-mcp-server (or vice versa)

When migrating between Container Use and git-mcp-server, consider these factors:

  1. API Compatibility: Container Use (uncategorized) and git-mcp-server (infrastructure) serve different categories, so migration may require significant refactoring.
  2. Security Review: Run a security audit after migration. Check the Container Use safety report and git-mcp-server safety report for known issues.
  3. Testing: Ensure your test suite covers all integration points before switching in production.
  4. Community Support: Container Use has 3,687 stars and git-mcp-server has 0. Larger communities typically mean better Stack Overflow answers and migration guides.
Container Use Safety Report git-mcp-server Safety Report Container Use Alternatives git-mcp-server Alternatives

Related Pages

Frequently Asked Questions

Which is safer, Container Use or git-mcp-server?
Based on Nerq's independent trust assessment, Container Use has a trust score of 70.5/100 (B) while git-mcp-server scores 89.0/100 (B+). The 18.5-point difference suggests git-mcp-server has a stronger trust profile. Trust scores are based on security, compliance, maintenance, documentation, and community adoption.
How do Container Use and git-mcp-server compare on security?
Container Use has a security score of N/A/100 and git-mcp-server scores 0/100. There is a notable difference in their security assessments. Container Use's compliance score is N/A/100 (EU risk: N/A), while git-mcp-server's is 100/100 (EU risk: N/A).
Should I use Container Use or git-mcp-server?
The choice depends on your requirements. Container Use (uncategorized, 3,687 stars) and git-mcp-server (infrastructure, 0 stars) serve different use cases. On trust, Container Use scores 70.5/100 and git-mcp-server scores 89.0/100. Review the full KYA reports for each agent before making a decision. Consider factors like integration requirements, documentation quality (N/A vs 1), and maintenance activity (N/A vs 1).

Related Comparisons

Last updated: 2026-06-22 | 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.

We use cookies for analytics and caching. Privacy Policy