Is Github Mcp Worker Safe?

Is Github Mcp Worker safe?

YES — Github Mcp Worker has a Nerq Trust Score of 76.5/100 (B). It meets Nerq's trust threshold with strong signals across security, maintenance, and community adoption. Recommended for use — review the full report below for specific considerations.

What Is Github Mcp Worker?

Github Mcp Worker is a software tool in the coding category: A read-only GitHub MCP server for Claude to browse public repos without access errors.. It has 1 GitHub stars. Nerq Trust Score: 76/100 (B).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including security vulnerabilities, maintenance activity, license compliance, and community adoption.

How Nerq Assesses Github Mcp Worker's Safety

Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensions. Here is how Github Mcp Worker performs in each:

• Security (0/100): Github Mcp Worker's security posture is poor. This score factors in known CVEs, dependency vulnerabilities, security policy presence, and code signing practices.
• Maintenance (1/100): Github Mcp Worker is potentially abandoned. We track commit frequency, release cadence, issue response times, and PR merge rates.
• Documentation (1/100): Documentation quality is insufficient. This includes README completeness, API documentation, usage examples, and contribution guidelines.
• Compliance (100/100): Github Mcp Worker is broadly compliant. Assessed against regulations in 52 jurisdictions including the EU AI Act, CCPA, and GDPR.
• Community (0/100): Community adoption is limited. Based on GitHub stars, forks, download counts, and ecosystem integrations.

The overall Trust Score of 76.5/100 (B) reflects the weighted combination of these signals. This exceeds the Nerq Verified threshold of 70, indicating the tool meets our standards for production use.

Who Should Use Github Mcp Worker?

Github Mcp Worker is designed for:

• Developers and teams working with coding tools
• Organizations evaluating AI tools for their stack
• Researchers exploring AI capabilities in this domain

Risk guidance: Github Mcp Worker meets the minimum threshold for production use, but we recommend monitoring for security advisories and keeping dependencies up to date. Consider implementing additional guardrails for sensitive workloads.

How to Verify Github Mcp Worker's Safety Yourself

While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:

1. Check the source code — Review the repository's security policy, open issues, and recent commits for signs of active maintenance.
2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for known vulnerabilities in Github Mcp Worker's dependency tree.
3. Review permissions — Understand what access Github Mcp Worker requires. Software tools should follow the principle of least privilege.
4. Test in isolation — Run Github Mcp Worker in a sandboxed environment before granting access to production data or systems.
5. Monitor continuously — Use Nerq's API to set up automated trust checks: GET nerq.ai/v1/preflight?target=github-mcp-worker
6. Review the license — Confirm that Github Mcp Worker's license is compatible with your intended use case. Pay attention to restrictions on commercial use, redistribution, and derivative works. Some AI tools use dual licensing or have separate terms for enterprise customers that differ from the open-source license.
7. Check community signals — Look at the project's issue tracker, discussion forums, and social media presence. A healthy community actively reports bugs, contributes fixes, and discusses security concerns openly. Low community engagement may indicate limited peer review of the codebase.

Common Safety Concerns with Github Mcp Worker

When evaluating whether Github Mcp Worker is safe, consider these category-specific risks:

Github Mcp Worker and the EU AI Act

Github Mcp Worker is classified as Minimal Risk under the EU AI Act. This is the lowest risk category, meaning it faces minimal regulatory requirements. However, transparency obligations still apply.

Nerq's compliance assessment covers 52 jurisdictions worldwide. For organizations deploying AI tools in regulated environments, understanding these classifications is essential for legal compliance.

Best Practices for Using Github Mcp Worker Safely

Whether you're an individual developer or an enterprise team, these practices will help you get the most from Github Mcp Worker while minimizing risk:

When Should You Avoid Github Mcp Worker?

Even well-trusted tools aren't right for every situation. Consider avoiding Github Mcp Worker in these scenarios:

• Scenarios where Github Mcp Worker's specific capabilities exceed your actual needs — simpler tools may be safer
• Air-gapped environments where the tool cannot receive security updates
• Projects with strict regulatory requirements that haven't been explicitly validated

For each scenario, evaluate whether Github Mcp Worker's trust score of 76.5/100 meets your organization's risk tolerance. The Nerq Verified status indicates general production readiness, but sector-specific requirements may apply.

How Github Mcp Worker Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among coding tools, the average Trust Score is 62/100. Github Mcp Worker's score of 76.5/100 is significantly above the category average of 62/100.

This places Github Mcp Worker in the top tier of coding tools that Nerq tracks. Tools scoring this far above average typically demonstrate mature security practices, consistent release cadence, and broad community adoption.

Industry benchmarks matter because they contextualize a tool's safety profile. A score that looks moderate in isolation may actually represent strong performance within a challenging category — or vice versa. Nerq's category-relative analysis helps teams make informed decisions by showing not just absolute quality, but how a tool ranks against its direct peers.

Trust Score History

Nerq continuously monitors Github Mcp Worker and recalculates its Trust Score as new data becomes available. Our scoring engine ingests real-time signals from source repositories, vulnerability databases (NVD, OSV.dev), package registries, and community metrics. When a new CVE is published, a major release ships, or maintenance patterns change, Github Mcp Worker's score is updated within 24 hours.

Historical trust trends reveal whether a tool is improving, stable, or declining over time. A tool that consistently maintains or improves its score demonstrates ongoing commitment to security and quality. Conversely, a downward trend may signal reduced maintenance, growing technical debt, or unresolved vulnerabilities. To track Github Mcp Worker's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=github-mcp-worker&include=history

Nerq retains trust score snapshots at regular intervals, enabling trend analysis across weeks and months. Enterprise users can access detailed historical reports showing how each dimension — security, maintenance, documentation, compliance, and community — has evolved independently, providing granular visibility into which aspects of Github Mcp Worker are strengthening or weakening over time.

Github Mcp Worker vs Alternatives

In the coding category, Github Mcp Worker scores 76.5/100. It ranks among the top tools in its category. For a detailed comparison, see:

• Github Mcp Worker vs AutoGPT — Trust Score: 74.7/100
• Github Mcp Worker vs ollama — Trust Score: 73.8/100
• Github Mcp Worker vs langchain — Trust Score: 86.4/100

Key Takeaways

• Github Mcp Worker has a Trust Score of 76.5/100 (B) and is Nerq Verified.
• Github Mcp Worker meets the minimum threshold for production deployment, though monitoring and additional guardrails are recommended.
• Among coding tools, Github Mcp Worker scores significantly above the category average of 62/100, demonstrating above-average reliability.
• Always verify safety independently — use Nerq's Preflight API for automated, up-to-date trust checks before integration.