Is Github To Mcp Safe?

Is Github To Mcp safe?

CAUTION — Github To Mcp has a Nerq Trust Score of 64.3/100 (C+). It has moderate trust signals but shows some areas of concern that warrant attention. Suitable for development use — review security and maintenance signals before production deployment.

What Is Github To Mcp?

Github To Mcp is a software tool in the coding category: Convert GitHub repositories to MCP servers automatically. Extract tools from OpenAPI, GraphQL & REST APIs for Claude Desktop, Cursor, Windsurf, Cline & VS Code. AI-powered code generation creates type-safe TypeScript/Python MCP servers. Zero config setup - just paste a repo URL. Built for AI assista. It has 11 GitHub stars. Nerq Trust Score: 64/100 (C+).

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 To Mcp's Safety

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

• Security (0/100): Github To Mcp's security posture is poor. This score factors in known CVEs, dependency vulnerabilities, security policy presence, and code signing practices.
• Maintenance (1/100): Github To Mcp is potentially abandoned. We track commit frequency, release cadence, issue response times, and PR merge rates.
• Documentation (0/100): Documentation quality is insufficient. This includes README completeness, API documentation, usage examples, and contribution guidelines.
• Compliance (87/100): Github To Mcp 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 64.3/100 (C+) reflects the weighted combination of these signals. This is below the Nerq Verified threshold of 70. We recommend additional due diligence before production deployment.

Who Should Use Github To Mcp?

Github To Mcp 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 To Mcp is suitable for development and testing environments. Before production deployment, conduct a thorough review of its security posture, review the specific trust signals above, and consider whether a higher-scored alternative meets your requirements.

How to Verify Github To Mcp'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 To Mcp's dependency tree.
3. Review permissions — Understand what access Github To Mcp requires. Software tools should follow the principle of least privilege.
4. Test in isolation — Run Github To Mcp 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=nirholas/github-to-mcp
6. Review the license — Confirm that Github To Mcp'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 To Mcp

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

Github To Mcp and the EU AI Act

Github To Mcp 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 To Mcp Safely

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

When Should You Avoid Github To Mcp?

Even promising tools aren't right for every situation. Consider avoiding Github To Mcp in these scenarios:

• Production environments handling sensitive customer data
• Regulated industries (healthcare, finance, government) without additional compliance review
• Mission-critical systems where downtime has significant business impact

For each scenario, evaluate whether Github To Mcp's trust score of 64.3/100 meets your organization's risk tolerance. We recommend running a manual security assessment alongside the automated Nerq score.

How Github To Mcp 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 To Mcp's score of 64.3/100 is above the category average of 62/100.

This positions Github To Mcp favorably among coding tools. While it outperforms the average, there is still room for improvement in certain trust dimensions.

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 To Mcp 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 To Mcp'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 To Mcp's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=nirholas/github-to-mcp&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 To Mcp are strengthening or weakening over time.

Github To Mcp vs Alternatives

In the coding category, Github To Mcp scores 64.3/100. There are higher-scoring alternatives available. For a detailed comparison, see:

• Github To Mcp vs AutoGPT — Trust Score: 63.2/100
• Github To Mcp vs ollama — Trust Score: 58.0/100
• Github To Mcp vs langchain — Trust Score: 71.3/100

Key Takeaways

• Github To Mcp has a Trust Score of 64.3/100 (C+) and is not yet Nerq Verified.
• Github To Mcp shows moderate trust signals. Conduct thorough due diligence before deploying to production environments.
• Among coding tools, Github To Mcp scores 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.