¿Es Code Executor Mcp Seguro?

¿Es Code Executor Mcp Seguro?

Desglose de Puntuación de Confianza — Code Executor Mcp has a Nerq Trust Score of 51.2/100 (D). Measured across 5 independent trust signals.

What Is Code Executor Mcp?

Code Executor Mcp is a software tool in the coding category: Code Executor MCP efficiently manages and executes code, reducing token usage.. Nerq Trust Score: 51/100 (D).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including seguridad vulnerabilities, mantenimiento activity, license cumplimiento, and adopción por la comunidad.

How Nerq Assesses Code Executor Mcp's Safety

Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensiones. Here is how Code Executor Mcp performs in each:

• Seguridad (0/100): Code Executor Mcp's seguridad posture is poor. This score factors in known CVEs, dependency vulnerabilities, seguridad policy presence, and code signing practices.
• Mantenimiento (1/100): Code Executor Mcp 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 documentación, usage examples, and contribution guidelines.
• Compliance (100/100): Code Executor 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. Basado en GitHub stars, forks, download counts, and ecosystem integrations.

The overall Trust Score of 51.2/100 (D) 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 Code Executor Mcp?

Code Executor Mcp is commonly evaluated by:

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

How to read the signals: Code Executor Mcp's measured signals (seguridad 0/100, mantenimiento 1/100, documentación 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 Code Executor 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 — Revisar el/la repository seguridad policy, open issues, and recent commits for signs of active mantenimiento.
2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for known vulnerabilities in Code Executor Mcp's dependency tree.
3. Reseña permissions — Understand what access Code Executor Mcp requires. Software tools should follow the principle of least privilege.
4. Test in isolation — Run Code Executor 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=code-executor-MCP
6. Revisar el/la license — Confirm that Code Executor 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 seguridad concerns openly. Low community engagement may indicate limited peer review of the codebase.

Common Safety Concerns with Code Executor Mcp

When evaluating whether Code Executor Mcp is safe, consider these category-specific risks:

Code Executor Mcp and the EU AI Act

Code Executor 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 cumplimiento assessment covers 52 jurisdictions worldwide. For organizations deploying AI tools in regulated environments, understanding these classifications is essential for legal cumplimiento.

Best Practices for Using Code Executor Mcp Safely

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

Situations That Warrant Independent Review of Code Executor Mcp

Nerq's signals are one input. In the following situations, evaluate Code Executor Mcp'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 Code Executor Mcp's measured trust score of 51.2/100 and its individual signals against your organization's own criteria. Nerq does not assert whether Code Executor Mcp is suitable for any particular use.

How Code Executor 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. Code Executor Mcp's score of 51.2/100 is below the category average of 62/100.

This suggests that Code Executor Mcp trails behind many comparable coding tools. Organizations with strict seguridad requirements should evaluate whether higher-scoring alternatives better meet their needs.

Industry benchmarks matter because they contextualize a tool's safety profile. A score that looks moderado 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 Code Executor 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 mantenimiento patterns change, Code Executor 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 seguridad and quality. Conversely, a downward trend may signal reduced mantenimiento, growing technical debt, or unresolved vulnerabilities. To track Code Executor Mcp's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=code-executor-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 — seguridad, mantenimiento, documentación, cumplimiento, and community — has evolved independently, providing granular visibility into which aspects of Code Executor Mcp are strengthening or weakening over time.

Code Executor Mcp vs Alternativas

In the coding category, Code Executor Mcp scores 51.2/100. There are higher-scoring alternatives available. For a detailed comparison, see:

• Code Executor Mcp vs AutoGPT — Trust Score: 65.3/100
• Code Executor Mcp vs ollama — Trust Score: 64.4/100
• Code Executor Mcp vs langchain — Trust Score: 77.0/100

Puntos Clave

• Code Executor Mcp has a measured Nerq Trust Score of 51.2/100 (D) — a composite of independent signals, not a suitability judgment.
• Among coding tools, Code Executor Mcp scores below the category average of 62/100 (a positional measurement relative to peers).
• The individual signals — seguridad, mantenimiento, documentación, cumplimiento, community — are shown above. Weigh them against your own requirements.
• Query the current measured values via Nerq's Preflight API.