datagouv-mcp vs zstd — Trust Score Comparison

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

datagouv-mcp scores 72.3/100 (B) while zstd scores 56.0/100 (D) on the Nerq Trust Score. datagouv-mcp leads by 16.3 points. datagouv-mcp is a data tool with 36 stars, Nerq Verified. zstd is a uncategorized tool with 0 stars.
72.3
B verified
Categorydata
Stars36
Sourcegithub
Security0
Compliance61
Maintenance1
Documentation1
vs
56.0
D
Categoryuncategorized
Stars0
Sourcenpm_full
Compliance100

Detailed Metric Comparison

Metric datagouv-mcp zstd
Trust Score72.3/10056.0/100
GradeBD
Stars360
Categorydatauncategorized
Security0N/A
Compliance61100
Maintenance1N/A
Documentation1N/A
EU AI Act RiskminimalN/A
VerifiedYesNo

Verdict

datagouv-mcp leads with a trust score of 72.3/100 compared to zstd's 56.0/100 (a 16.3-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. datagouv-mcp scores 0 and zstd scores N/A on this dimension.

Maintenance & Activity

Activity scores reflect how actively each project is maintained. datagouv-mcp: 1, zstd: N/A.

Documentation

Documentation quality is evaluated based on README, API docs, and example coverage. datagouv-mcp: 1, zstd: N/A.

Community & Adoption

datagouv-mcp has 36 GitHub stars while zstd has 0. datagouv-mcp 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 datagouv-mcp if you need:

  • Higher overall trust score — more reliable for production use
  • More actively maintained with faster release cadence
  • Larger community (36 vs 0 stars)
  • Better documentation for faster onboarding

Choose zstd if you need:

  • Consider if it better fits your specific use case

Switching from datagouv-mcp to zstd (or vice versa)

When migrating between datagouv-mcp and zstd, consider these factors:

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

Related Pages

Frequently Asked Questions

Which is safer, datagouv-mcp or zstd?
Based on Nerq's independent trust assessment, datagouv-mcp has a trust score of 72.3/100 (B) while zstd scores 56.0/100 (D). The 16.3-point difference suggests datagouv-mcp has a stronger trust profile. Trust scores are based on security, compliance, maintenance, documentation, and community adoption.
How do datagouv-mcp and zstd compare on security?
datagouv-mcp has a security score of 0/100 and zstd scores N/A/100. There is a notable difference in their security assessments. datagouv-mcp's compliance score is 61/100 (EU risk: minimal), while zstd's is 100/100 (EU risk: N/A).
Should I use datagouv-mcp or zstd?
The choice depends on your requirements. datagouv-mcp (data, 36 stars) and zstd (uncategorized, 0 stars) serve different use cases. On trust, datagouv-mcp scores 72.3/100 and zstd scores 56.0/100. Review the full KYA reports for each agent before making a decision. Consider factors like integration requirements, documentation quality (1 vs N/A), and maintenance activity (1 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