Is Mcp Kind Manager veilig?
Mcp Kind Manager — Nerq Trust Score 64.4/100 (C-beoordeling). Score gebaseerd op 5 independent trust signals.
Mcp Kind Manager is een software tool met een Nerq Vertrouwensscore van 64.4/100 (C), based on 5 onafhankelijke gegevensdimensies. Beveiliging: 0/100. Onderhoud: 1/100. Populariteit: 0/100. Gegevens afkomstig van meerdere openbare bronnen waaronder pakketregisters, GitHub, NVD, OSV.dev en OpenSSF Scorecard. Laatst bijgewerkt: n/a. Machineleesbare gegevens (JSON).
Is Mcp Kind Manager veilig?
Vertrouwensscore details — Mcp Kind Manager has a Nerq Trust Score of 64.4/100 (C). Measured across 5 independent trust signals.
Wat is de vertrouwensscore van Mcp Kind Manager?
Mcp Kind Manager heeft een Nerq Trust Score van 64.4/100 met het cijfer C. Deze score is gebaseerd op 5 onafhankelijk gemeten dimensies, waaronder beveiliging, onderhoud en community-adoptie.
Wat zijn de belangrijkste beveiligingsbevindingen voor Mcp Kind Manager?
Het sterkste signaal van Mcp Kind Manager is naleving met 100/100. Er zijn geen bekende kwetsbaarheden gedetecteerd.
Wat is Mcp Kind Manager en wie onderhoudt het?
| Ontwikkelaar | kubevoidcraft |
| Categorie | Devops |
| Bron | https://github.com/kubevoidcraft/mcp-kind-manager |
| Frameworks | anthropic |
| Protocols | mcp |
Naleving van regelgeving
| EU AI Act Risk Class | MINIMAL |
| Compliance Score | 100/100 |
| Jurisdictions | Assessed across 52 jurisdicties |
Populaire alternatieven in devops
What Is Mcp Kind Manager?
Mcp Kind Manager is a DevOps tool: MCP server for managing Kind Kubernetes clusters.. Nerq Trust Score: 64/100 (C).
Nerq independently analyzes every software tool, app, and extension across multiple trust signals including beveiliging vulnerabilities, onderhoud activity, license naleving, and gemeenschapsacceptatie.
How Nerq Assesses Mcp Kind Manager's Safety
Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensies. Here is how Mcp Kind Manager performs in each:
- Beveiliging (0/100): Mcp Kind Manager's beveiliging posture is poor. This score factors in known CVEs, dependency vulnerabilities, beveiliging policy presence, and code signing practices.
- Onderhoud (1/100): Mcp Kind Manager 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 documentatie, usage examples, and contribution guidelines.
- Compliance (100/100): Mcp Kind Manager is broadly compliant. Assessed against regulations in 52 jurisdicties including the EU AI Act, CCPA, and GDPR.
- Community (0/100): Community adoption is limited. Gebaseerd op GitHub stars, forks, download counts, and ecosystem integrations.
The overall Trust Score of 64.4/100 (C) is the weighted combination of these measured signals. It is a measurement, not a pass/fail or suitability judgment — weigh the individual signals against your own requirements.
Who Typically Evaluates Mcp Kind Manager?
Mcp Kind Manager is commonly evaluated by:
- Developers and teams working with devops tools
- Organizations evaluating AI tools for their stack
- Researchers exploring AI capabilities in this domain
How to read the signals: Mcp Kind Manager's measured signals (beveiliging 0/100, onderhoud 1/100, documentatie 1/100, community 0/100) are shown above. These are measurements, not a suitability judgment — weigh each signal against the requirements of your own use case and risk tolerance.
How to Verify Mcp Kind Manager's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — Bekijk de repository's beveiliging policy, open issues, and recent commits for signs of active onderhoud.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for known vulnerabilities in Mcp Kind Manager's dependency tree. - Beoordeling permissions — Understand what access Mcp Kind Manager requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Mcp Kind Manager in a sandboxed environment before granting access to production data or systems.
- Monitor continuously — Use Nerq's API to set up automated trust checks:
GET nerq.ai/v1/preflight?target=mcp-kind-manager - Bekijk de license — Confirm that Mcp Kind Manager'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.
- 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 beveiliging concerns openly. Low community engagement may indicate limited peer review of the codebase.
Common Safety Concerns with Mcp Kind Manager
When evaluating whether Mcp Kind Manager is safe, consider these category-specific risks:
Understand how Mcp Kind Manager processes, stores, and transmits your data. Bekijk de tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Mcp Kind Manager's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher beveiliging risk.
Regularly check for updates to Mcp Kind Manager. Beveiliging patches and bug fixes are only effective if you're running the latest version.
If Mcp Kind Manager connects to external APIs or services, each integration point is a potential attack surface. Audit all third-party connections, verify that data shared with external services is minimized, and ensure that integration credentials are rotated regularly.
Verify that Mcp Kind Manager's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Mcp Kind Manager in violation of its license can expose your organization to legal liability.
Mcp Kind Manager and the EU AI Act
Mcp Kind Manager 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 naleving assessment covers 52 jurisdicties worldwide. For organizations deploying AI tools in regulated environments, understanding these classifications is essential for legal naleving.
Best Practices for Using Mcp Kind Manager Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Mcp Kind Manager while minimizing risk:
Periodically review how Mcp Kind Manager is used in your workflow. Check for unexpected behavior, permissions drift, and naleving with your beveiliging policies.
Ensure Mcp Kind Manager and all its dependencies are running the latest stable versions to benefit from beveiliging patches.
Grant Mcp Kind Manager only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Mcp Kind Manager's beveiliging advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Mcp Kind Manager is used within your organization, including data handling guidelines and acceptable use cases.
Situations That Warrant Independent Review of Mcp Kind Manager
Nerq's signals are one input. In the following situations, evaluate Mcp Kind Manager's measured signals against your own requirements before making a decision:
- Environments handling sensitive or regulated data (healthcare, finance, government)
- Mission-critical systems where downtime has significant business impact
- Deployments with strict regulatory requirements that must be independently validated
For each situation, compare Mcp Kind Manager's measured trust score of 64.4/100 and its individual signals against your organization's own criteria. Nerq does not assert whether Mcp Kind Manager is suitable for any particular use.
How Mcp Kind Manager 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. Mcp Kind Manager's score of 64.4/100 is above the category average of 63/100.
This positions Mcp Kind Manager favorably among DevOps tools. While it outperforms the average, there is still room for improvement in certain trust dimensies.
Industry benchmarks matter because they contextualize a tool's safety profile. A score that looks matig 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 Mcp Kind Manager 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 onderhoud patterns change, Mcp Kind Manager'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 beveiliging and quality. Conversely, a downward trend may signal reduced onderhoud, growing technical debt, or unresolved vulnerabilities. To track Mcp Kind Manager's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=mcp-kind-manager&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 — beveiliging, onderhoud, documentatie, naleving, and community — has evolved independently, providing granular visibility into which aspects of Mcp Kind Manager are strengthening or weakening over time.
Mcp Kind Manager vs Alternatieven
In the devops category, Mcp Kind Manager scores 64.4/100. There are higher-scoring alternatives available. For a detailed comparison, see:
- Mcp Kind Manager vs ansible — Trust Score: 74.9/100
- Mcp Kind Manager vs Flowise — Trust Score: 67.5/100
- Mcp Kind Manager vs learn-claude-code — Trust Score: 72.1/100
Belangrijkste conclusies
- Mcp Kind Manager has a measured Nerq Trust Score of 64.4/100 (C) — a composite of independent signals, not a suitability judgment.
- Among DevOps tools, Mcp Kind Manager scores above the category average of 63/100 (a positional measurement relative to peers).
- The individual signals — beveiliging, onderhoud, documentatie, naleving, community — are shown above. Weigh them against your own requirements.
- Query the current measured values via Nerq's Preflight API.
Veelgestelde vragen
Is Mcp Kind Manager veilig?
Wat is de vertrouwensscore van Mcp Kind Manager?
Wat zijn veiligere alternatieven voor Mcp Kind Manager?
Hoe vaak wordt de beveiligingsscore van Mcp Kind Manager bijgewerkt?
Kan ik Mcp Kind Manager gebruiken in een gereguleerde omgeving?
Zie ook
Disclaimer: Nerq-vertrouwensscores zijn geautomatiseerde beoordelingen op basis van openbaar beschikbare signalen. Ze vormen geen aanbeveling of garantie. Voer altijd uw eigen verificatie uit.