mcp-server-browserbase vs stable-hash — Trust Score Comparison

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

mcp-server-browserbase scores 70.4/100 (B) while stable-hash scores 56.8/100 (D) on the Nerq Trust Score. mcp-server-browserbase leads by 13.6 points. mcp-server-browserbase is a infrastructure tool with 3,116 stars, Nerq Verified. stable-hash is a uncategorized tool with 0 stars.
70.4
B verified
Categoryinfrastructure
Stars3,116
Sourcemcp
Security0
Compliance100
Maintenance0
Documentation0
vs
56.8
D
Categoryuncategorized
Stars0
Sourcenpm_full
Compliance100

Detailed Metric Comparison

Metric mcp-server-browserbase stable-hash
Trust Score70.4/10056.8/100
GradeBD
Stars3,1160
Categoryinfrastructureuncategorized
Security0N/A
Compliance100100
Maintenance0N/A
Documentation0N/A
EU AI Act RiskminimalN/A
VerifiedYesNo

Verdict

mcp-server-browserbase leads with a trust score of 70.4/100 compared to stable-hash's 56.8/100 (a 13.6-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. mcp-server-browserbase scores 0 and stable-hash scores N/A on this dimension.

Maintenance & Activity

Activity scores reflect how actively each project is maintained. mcp-server-browserbase: 0, stable-hash: N/A.

Documentation

Documentation quality is evaluated based on README, API docs, and example coverage. mcp-server-browserbase: 0, stable-hash: N/A.

Community & Adoption

mcp-server-browserbase has 3,116 GitHub stars while stable-hash has 0. mcp-server-browserbase 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 mcp-server-browserbase if you need:

  • Higher overall trust score — more reliable for production use
  • Larger community (3,116 vs 0 stars)

Choose stable-hash if you need:

  • Consider if it better fits your specific use case

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

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

  1. API Compatibility: mcp-server-browserbase (infrastructure) and stable-hash (uncategorized) serve different categories, so migration may require significant refactoring.
  2. Security Review: Run a security audit after migration. Check the mcp-server-browserbase 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: mcp-server-browserbase has 3,116 stars and stable-hash has 0. Larger communities typically mean better Stack Overflow answers and migration guides.
mcp-server-browserbase Safety Report stable-hash Safety Report mcp-server-browserbase Alternatives stable-hash Alternatives

Related Pages

Frequently Asked Questions

Which is safer, mcp-server-browserbase or stable-hash?
Based on Nerq's independent trust assessment, mcp-server-browserbase has a trust score of 70.4/100 (B) while stable-hash scores 56.8/100 (D). The 13.6-point difference suggests mcp-server-browserbase has a stronger trust profile. Trust scores are based on security, compliance, maintenance, documentation, and community adoption.
How do mcp-server-browserbase and stable-hash compare on security?
mcp-server-browserbase has a security score of 0/100 and stable-hash scores N/A/100. There is a notable difference in their security assessments. mcp-server-browserbase's compliance score is 100/100 (EU risk: minimal), while stable-hash's is 100/100 (EU risk: N/A).
Should I use mcp-server-browserbase or stable-hash?
The choice depends on your requirements. mcp-server-browserbase (infrastructure, 3,116 stars) and stable-hash (uncategorized, 0 stars) serve different use cases. On trust, mcp-server-browserbase scores 70.4/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 (0 vs N/A), and maintenance activity (0 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