ccusage vs fixzi-mcp — Trust Score Comparison

Name: ccusage vs fixzi-mcp Trust Comparison
Creator: Nerq

Side-by-side trust comparison of ccusage and fixzi-mcp. Scores based on security, compliance, maintenance, popularity, and ecosystem signals.

ccusage scores 71.2/100 (B) while fixzi-mcp scores 67.5/100 (B-) on the Nerq Trust Score. ccusage leads by 3.7 points. ccusage is a coding tool with 10,847 stars, Nerq Verified. fixzi-mcp is a uncategorized tool with 0 stars.

ccusage

71.2

B verified

Categorycoding

Stars10,847

Sourcegithub

Security0

Compliance100

Maintenance0

Documentation0

fixzi-mcp

67.5

B-

Categoryuncategorized

Stars0

Sourcemcp_registry

Detailed Metric Comparison

Metric	ccusage	fixzi-mcp
Trust Score	71.2/100	67.5/100
Grade	B	B-
Stars	10,847	0
Category	coding	uncategorized
Security	0	N/A
Compliance	100	N/A
Maintenance	0	N/A
Documentation	0	N/A
EU AI Act Risk	N/A	N/A
Verified	Yes	No

Verdict

ccusage leads with a trust score of 71.2/100 compared to fixzi-mcp's 67.5/100 (a 3.7-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. ccusage scores 0 and fixzi-mcp scores N/A on this dimension.

Maintenance & Activity

Activity scores reflect how actively each project is maintained. ccusage: 0, fixzi-mcp: N/A.

Documentation

Documentation quality is evaluated based on README, API docs, and example coverage. ccusage: 0, fixzi-mcp: N/A.

Community & Adoption

ccusage has 10,847 GitHub stars while fixzi-mcp has 0. ccusage 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 ccusage if you need:

Higher overall trust score — more reliable for production use
Larger community (10,847 vs 0 stars)

Choose fixzi-mcp if you need:

Consider if it better fits your specific use case

Switching from ccusage to fixzi-mcp (or vice versa)

When migrating between ccusage and fixzi-mcp, consider these factors:

API Compatibility: ccusage (coding) and fixzi-mcp (uncategorized) serve different categories, so migration may require significant refactoring.
Security Review: Run a security audit after migration. Check the ccusage safety report and fixzi-mcp safety report for known issues.
Testing: Ensure your test suite covers all integration points before switching in production.
Community Support: ccusage has 10,847 stars and fixzi-mcp has 0. Larger communities typically mean better Stack Overflow answers and migration guides.

ccusage Safety Report fixzi-mcp Safety Report ccusage Alternatives fixzi-mcp Alternatives

Frequently Asked Questions

Which is safer, ccusage or fixzi-mcp?

Based on Nerq's independent trust assessment, ccusage has a trust score of 71.2/100 (B) while fixzi-mcp scores 67.5/100 (B-). The 3.7-point difference suggests ccusage has a stronger trust profile. Trust scores are based on security, compliance, maintenance, documentation, and community adoption.

How do ccusage and fixzi-mcp compare on security?

ccusage has a security score of 0/100 and fixzi-mcp scores N/A/100. There is a notable difference in their security assessments. ccusage's compliance score is 100/100 (EU risk: N/A), while fixzi-mcp's is N/A/100 (EU risk: N/A).

Should I use ccusage or fixzi-mcp?

The choice depends on your requirements. ccusage (coding, 10,847 stars) and fixzi-mcp (uncategorized, 0 stars) serve different use cases. On trust, ccusage scores 71.2/100 and fixzi-mcp scores 67.5/100. Review the full KYA reports for each agent before making a decision. Consider factors like integration requirements, documentation quality (0 vs N/A), and maintenance activity (0 vs N/A).

Related Comparisons

Last updated: 2026-08-03 | 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.