ccxt-mcp vs stable-hash — Trust Score Comparison

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

ccxt-mcp scores 65.2/100 (B-) while stable-hash scores 56.8/100 (D) on the Nerq Trust Score. ccxt-mcp leads by 8.4 points. ccxt-mcp is a uncategorized agent with 0 stars. stable-hash is a uncategorized agent with 0 stars.
65.2
B-
Categoryuncategorized
Stars0
Sourcemcp_registry
vs
56.8
D
Categoryuncategorized
Stars0
Sourcenpm_full
Compliance100

Detailed Metric Comparison

Metric ccxt-mcp stable-hash
Trust Score65.2/10056.8/100
GradeB-D
Stars00
Categoryuncategorizeduncategorized
SecurityN/AN/A
ComplianceN/A100
MaintenanceN/AN/A
DocumentationN/AN/A
EU AI Act RiskN/AN/A
VerifiedNoNo

Verdict

ccxt-mcp leads with a trust score of 65.2/100 compared to stable-hash's 56.8/100 (a 8.4-point difference). Both agents should be evaluated based on your specific requirements.

Detailed Analysis

Community & Adoption

ccxt-mcp has 0 GitHub stars while stable-hash has 0. Both tools have comparable community sizes, suggesting similar levels of ecosystem support and third-party resources.

When to Choose Each Tool

Choose ccxt-mcp if you need:

  • Higher overall trust score — more reliable for production use

Choose stable-hash if you need:

  • Consider if it better fits your specific use case

Switching from ccxt-mcp to stable-hash (or vice versa)

When migrating between ccxt-mcp and stable-hash, consider these factors:

  1. API Compatibility: ccxt-mcp (uncategorized) and stable-hash (uncategorized) share similar interfaces since they are in the same category.
  2. Security Review: Run a security audit after migration. Check the ccxt-mcp safety report and stable-hash safety report for known issues.
  3. Testing: Ensure your test suite covers all integration points before switching in production.
  4. Community Support: ccxt-mcp has 0 stars and stable-hash has 0. Larger communities typically mean better Stack Overflow answers and migration guides.
ccxt-mcp Safety Report stable-hash Safety Report ccxt-mcp Alternatives stable-hash Alternatives

Related Pages

Frequently Asked Questions

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

Related Comparisons

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