purmemo-mcp vs md_exporter — Trust Score Comparison
Side-by-side trust comparison of purmemo-mcp and md_exporter. Scores based on security, compliance, maintenance, popularity, and ecosystem signals.
Detailed Metric Comparison
| Metric | purmemo-mcp | md_exporter |
|---|---|---|
| Trust Score | 58.5/100 | 74.2/100 |
| Grade | D | B |
| Stars | 2 | 183 |
| Category | infrastructure | content |
| Security | 0 | 0 |
| Compliance | 87 | 100 |
| Maintenance | 1 | 1 |
| Documentation | 1 | 1 |
| EU AI Act Risk | minimal | N/A |
| Verified | No | Yes |
Verdict
md_exporter leads with a trust score of 74.2/100 compared to purmemo-mcp's 58.5/100 (a 15.7-point difference). md_exporter scores higher on compliance (100 vs 87). Both agents should be evaluated based on your specific requirements.
Detailed Analysis
Security
purmemo-mcp leads on security with a score of 0/100 compared to md_exporter'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
purmemo-mcp 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
md_exporter has better documentation (1/100 vs 1/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
purmemo-mcp has 2 GitHub stars while md_exporter has 183. md_exporter 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 purmemo-mcp if you need:
- Consider if it better fits your specific use case
Choose md_exporter if you need:
- Higher overall trust score — more reliable for production use
- Larger community (183 vs 2 stars)
- Better documentation for faster onboarding
Switching from purmemo-mcp to md_exporter (or vice versa)
When migrating between purmemo-mcp and md_exporter, consider these factors:
- API Compatibility: purmemo-mcp (infrastructure) and md_exporter (content) serve different categories, so migration may require significant refactoring.
- Security Review: Run a security audit after migration. Check the purmemo-mcp safety report and md_exporter safety report for known issues.
- Testing: Ensure your test suite covers all integration points before switching in production.
- Community Support: purmemo-mcp has 2 stars and md_exporter has 183. Larger communities typically mean better Stack Overflow answers and migration guides.
Related Pages
Frequently Asked Questions
Related Comparisons
Last updated: 2026-09-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.