agent-fetch vs bankstatemently-mcp — Trust Score Comparison

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

agent-fetch scores 72.2/100 (B) while bankstatemently-mcp scores 67.5/100 (B-) on the Nerq Trust Score. agent-fetch leads by 4.7 points. agent-fetch is a content tool with 1 stars, Nerq Verified. bankstatemently-mcp is a uncategorized tool with 0 stars.
72.2
B verified
Categorycontent
Stars1
Sourcegithub
Security0
Compliance100
Maintenance1
Documentation1
vs
67.5
B-
Categoryuncategorized
Stars0
Sourcemcp_registry

Detailed Metric Comparison

Metric agent-fetch bankstatemently-mcp
Trust Score72.2/10067.5/100
GradeBB-
Stars10
Categorycontentuncategorized
Security0N/A
Compliance100N/A
Maintenance1N/A
Documentation1N/A
EU AI Act RiskminimalN/A
VerifiedYesNo

Verdict

agent-fetch leads with a trust score of 72.2/100 compared to bankstatemently-mcp's 67.5/100 (a 4.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. agent-fetch scores 0 and bankstatemently-mcp scores N/A on this dimension.

Maintenance & Activity

Activity scores reflect how actively each project is maintained. agent-fetch: 1, bankstatemently-mcp: N/A.

Documentation

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

Community & Adoption

agent-fetch has 1 GitHub stars while bankstatemently-mcp has 0. agent-fetch 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 agent-fetch if you need:

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

Choose bankstatemently-mcp if you need:

  • Consider if it better fits your specific use case

Switching from agent-fetch to bankstatemently-mcp (or vice versa)

When migrating between agent-fetch and bankstatemently-mcp, consider these factors:

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

Related Pages

Frequently Asked Questions

Which is safer, agent-fetch or bankstatemently-mcp?
Based on Nerq's independent trust assessment, agent-fetch has a trust score of 72.2/100 (B) while bankstatemently-mcp scores 67.5/100 (B-). The 4.7-point difference suggests agent-fetch has a stronger trust profile. Trust scores are based on security, compliance, maintenance, documentation, and community adoption.
How do agent-fetch and bankstatemently-mcp compare on security?
agent-fetch has a security score of 0/100 and bankstatemently-mcp scores N/A/100. There is a notable difference in their security assessments. agent-fetch's compliance score is 100/100 (EU risk: minimal), while bankstatemently-mcp's is N/A/100 (EU risk: N/A).
Should I use agent-fetch or bankstatemently-mcp?
The choice depends on your requirements. agent-fetch (content, 1 stars) and bankstatemently-mcp (uncategorized, 0 stars) serve different use cases. On trust, agent-fetch scores 72.2/100 and bankstatemently-mcp scores 67.5/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-08-07 | 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