Ist Svc Mcp Github sicher?

Ist Svc Mcp Github sicher?

CAUTION — Svc Mcp Github hat eine Nerq-Vertrauensbewertung von 65.5/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 Svc Mcp Github?

Svc Mcp Github is a DevOps tool: MCP server for GitHub operations with Keycard authentication.. Nerq Trust Score: 66/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 Svc Mcp Github's Safety

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

• Sicherheit (0/100): Svc Mcp Github's security posture is poor. This score factors in known CVEs, dependency vulnerabilities, security policy presence, and code signing practices.
• Wartung (1/100): Svc Mcp Github 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): Svc Mcp Github 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 65.5/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 Svc Mcp Github?

Svc Mcp Github is designed for:

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

Risk guidance: Svc Mcp Github 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 Svc Mcp Github'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 Svc Mcp Github's dependency tree.
3. Bewertung permissions — Understand what access Svc Mcp Github requires. Software tools should follow the principle of least privilege.
4. Test in isolation — Run Svc Mcp Github 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=svc-mcp-github
6. Überprüfen Sie das/die license — Confirm that Svc Mcp Github'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 Svc Mcp Github

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

Svc Mcp Github and the EU AI Act

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

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

When Should You Avoid Svc Mcp Github?

Even promising tools aren't right for every situation. Consider avoiding Svc Mcp Github 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 Svc Mcp Github von 65.5/100 meets your organization's risk tolerance. We recommend running a manual security assessment alongside the automated Nerq score.

How Svc Mcp Github Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among DevOps tools, the average Trust Score is 63/100. Svc Mcp Github's score of 65.5/100 is above the category average of 63/100.

This positions Svc Mcp Github favorably among DevOps 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 Svc Mcp Github 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, Svc Mcp Github'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 Svc Mcp Github's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=svc-mcp-github&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 Svc Mcp Github are strengthening or weakening over time.

Svc Mcp Github vs Alternatives

In the devops category, Svc Mcp Github erzielt 65.5/100. There are higher-scoring alternatives available. For a detailed comparison, see:

• Svc Mcp Github vs ansible — Trust Score: 84.3/100
• Svc Mcp Github vs Flowise — Trust Score: 76.9/100
• Svc Mcp Github vs learn-claude-code — Trust Score: 81.5/100

Wichtigste Punkte

• Svc Mcp Github hat eine Vertrauensbewertung von 65.5/100 (C) and is not yet Nerq Verified.
• Svc Mcp Github shows moderate trust signals. Conduct thorough due diligence before deploying to production environments.
• Among DevOps tools, Svc Mcp Github erzielt above the category average of 63/100, demonstrating above-average reliability.
• Always verify safety independently — use Nerq's Preflight API for automated, up-to-date trust checks before integration.