Er Mcpshell sikker?

Mcpshell — Nerq Trust Score 47.4/100 (Karakter D). Baseret på analyse af 3 tillidsdimensioner vurderes det som har bemærkelsesværdige sikkerhedsproblemer. Sidst opdateret: 2026-04-23.

Vær forsigtig med Mcpshell. Mcpshell er en software tool med en Nerq Tillidsscore på 47.4/100 (D), based on 3 uafhængige datadimensioner. Under Nerqs verificerede tærskel Vedligeholdelse: 0/100. Popularitet: 0/100. Data hentet fra flere offentlige kilder herunder pakkeregistre, GitHub, NVD, OSV.dev og OpenSSF Scorecard. Sidst opdateret: 2026-04-23. Maskinlæsbare data (JSON).

Er Mcpshell sikker?

NO — USE WITH CAUTION — Mcpshell has a Nerq Trust Score of 47.4/100 (D). Har under gennemsnitlige tillidssignaler med betydelige huller in sikkerhed, vedligeholdelse, or dokumentation. Not recommended for production use without thorough manual review and additional sikkerhed measures.

Sikkerhedsanalyse → Mcpshell privatlivsrapport →

Hvad er Mcpshells tillidsscore?

Mcpshell har en Nerq Trust Score på 47.4/100 med karakteren D. Denne score er baseret på 3 uafhængigt målte dimensioner, herunder sikkerhed, vedligeholdelse og community-adoption.

Vedligeholdelse
0
Dokumentation
0
Popularitet
0

Hvad er de vigtigste sikkerhedsresultater for Mcpshell?

Mcpshells stærkeste signal er vedligeholdelse på 0/100. Ingen kendte sårbarheder er fundet. It has not yet reached the Nerq Verified threshold of 70+.

Vedligeholdelse: 0/100 — lav vedligeholdelsesaktivitet
Dokumentation: 0/100 — begrænset dokumentation
Popularitet: 0/100 — 58 stjerner på pulsemcp

Hvad er Mcpshell og hvem vedligeholder det?

Udviklerhttps://github.com/inercia/mcpshell
KategoriInfrastructure
Stjerner58
Kildehttps://github.com/inercia/mcpshell

Populære alternativer i infrastructure

n8n-io/n8n
52.2/100 · C-
github
langflow-ai/langflow
66.1/100 · B-
github
langgenius/dify
65.5/100 · B-
github
open-webui/open-webui
74.8/100 · B
github
google-gemini/gemini-cli
71.8/100 · B
github

What Is Mcpshell?

Mcpshell is a software tool in the infrastructure category: Provides a secure bridge between language models and operating system commands through a configurable YAML interface with constraint-based sikkerhed, multiple sandboxing options, and robust error handling.. It has 58 GitHub stars. Nerq Trust Score: 47/100 (D).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including sikkerhed vulnerabilities, vedligeholdelse activity, license overholdelse, and fællesskabsadoption.

How Nerq Assesses Mcpshell's Safety

Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensioner. Here is how Mcpshell performs in each:

The overall Trust Score of 47.4/100 (D) 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 Mcpshell?

Mcpshell is designed for:

Risk guidance: We recommend caution with Mcpshell. The low trust score suggests potential risks in sikkerhed, vedligeholdelse, or community support. Consider using a more established alternative for any production or sensitive workload.

How to Verify Mcpshell's Safety Yourself

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

  1. Check the source code — Gennemgå repository sikkerhed policy, open issues, and recent commits for signs of active vedligeholdelse.
  2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for known vulnerabilities in Mcpshell's dependency tree.
  3. Anmeldelse permissions — Understand what access Mcpshell requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Mcpshell 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=MCPShell
  6. Gennemgå license — Confirm that Mcpshell'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 sikkerhed concerns openly. Low community engagement may indicate limited peer review of the codebase.

Common Safety Concerns with Mcpshell

When evaluating whether Mcpshell is safe, consider these category-specific risks:

Data handling

Understand how Mcpshell processes, stores, and transmits your data. Gennemgå tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency sikkerhed

Check Mcpshell's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher sikkerhed risk.

Update frequency

Regularly check for updates to Mcpshell. Sikkerhed patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

If Mcpshell 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.

License and IP overholdelse

Verify that Mcpshell's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Mcpshell in violation of its license can expose your organization to legal liability.

Best Practices for Using Mcpshell Safely

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

Conduct regular audits

Periodically review how Mcpshell is used in your workflow. Check for unexpected behavior, permissions drift, and overholdelse with your sikkerhed policies.

Keep dependencies updated

Ensure Mcpshell and all its dependencies are running the latest stable versions to benefit from sikkerhed patches.

Follow least privilege

Grant Mcpshell only the minimum permissions it needs to function. Avoid granting admin or root access.

Monitor for sikkerhed advisories

Subscribe to Mcpshell's sikkerhed advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.

Document usage policies

Create and maintain a clear policy for how Mcpshell is used within your organization, including data handling guidelines and acceptable use cases.

When Should You Avoid Mcpshell?

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

For each scenario, evaluate whether Mcpshell's trust score of 47.4/100 meets your organization's risk tolerance. We recommend running a manual sikkerhed assessment alongside the automated Nerq score.

How Mcpshell Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among infrastructure tools, the average Trust Score is 62/100. Mcpshell's score of 47.4/100 is below the category average of 62/100.

This suggests that Mcpshell trails behind many comparable infrastructure tools. Organizations with strict sikkerhed 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 moderat 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 Mcpshell 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 vedligeholdelse patterns change, Mcpshell'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 sikkerhed and quality. Conversely, a downward trend may signal reduced vedligeholdelse, growing technical debt, or unresolved vulnerabilities. To track Mcpshell's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=MCPShell&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 — sikkerhed, vedligeholdelse, dokumentation, overholdelse, and community — has evolved independently, providing granular visibility into which aspects of Mcpshell are strengthening or weakening over time.

Mcpshell vs Alternativer

In the infrastructure category, Mcpshell scores 47.4/100. There are higher-scoring alternatives available. For a detailed comparison, see:

Vigtigste pointer

Detaljeret scoreanalyse

DimensionScore
Vedligeholdelse0/100
Popularitet0/100

Baseret på 2 dimensioner. Data from flere offentlige kilder herunder pakkeregistre, GitHub, NVD, OSV.dev og OpenSSF Scorecard.

Hvilke data indsamler Mcpshell?

Privatliv assessment for Mcpshell is not yet available. See our methodology for how Nerq measures privacy, or the public privacy review for any community-contributed notes.

Er Mcpshell sikker?

Sikkerhed score: under vurdering. Review sikkerhed practices and consider alternatives with higher sikkerhed scores for sensitive use cases.

Nerq overvåger denne enhed mod NVD, OSV.dev og registrespecifikke sårbarhedsdatabaser til løbende sikkerhedsvurdering.

Fuld analyse: Mcpshell sikkerhedsrapport

Sådan beregnede vi denne score

Mcpshell's trust score of 47.4/100 (D) beregnes ud fra flere offentlige kilder herunder pakkeregistre, GitHub, NVD, OSV.dev og OpenSSF Scorecard. Scoren afspejler 2 uafhængige dimensioner: vedligeholdelse (0/100), popularitet (0/100). Hver dimension vægtes ens for at producere den samlede tillidsscore.

Nerq analyserer over 7,5 millioner enheder i 26 registre med samme metodik, hvilket muliggør direkte sammenligning mellem enheder. Scorer opdateres løbende, efterhånden som nye data bliver tilgængelige.

Denne side blev sidst gennemgået den April 23, 2026. Dataversion: 1.0.

Fuld metodikdokumentation · Maskinlæsbare data (JSON API)

Ofte stillede spørgsmål

Er Mcpshell sikker?
Vær forsigtig. MCPShell med en Nerq Tillidsscore på 47.4/100 (D). Stærkeste signal: vedligeholdelse (0/100). Score baseret på Vedligeholdelse (0/100), Popularitet (0/100), Dokumentation (0/100).
Hvad er Mcpshells tillidsscore?
MCPShell: 47.4/100 (D). Score baseret på Vedligeholdelse (0/100), Popularitet (0/100), Dokumentation (0/100). Scorer opdateres når nye data bliver tilgængelige. API: GET nerq.ai/v1/preflight?target=MCPShell
Hvad er sikrere alternativer til Mcpshell?
I kategorien Infrastructure, higher-rated alternatives include n8n-io/n8n (52/100), langflow-ai/langflow (66/100), langgenius/dify (66/100). MCPShell scores 47.4/100.
Hvor ofte opdateres Mcpshells sikkerhedsscore?
Nerq continuously monitors Mcpshell and updates its trust score as new data becomes available. Current: 47.4/100 (D), last verificeret 2026-04-23. API: GET nerq.ai/v1/preflight?target=MCPShell
Kan jeg bruge Mcpshell i et reguleret miljø?
Mcpshell har ikke nået Nerq-verificeringstærsklen på 70. Yderligere gennemgang anbefales.
API: /v1/preflight Trust Badge API Docs

Se også

Disclaimer: Nerqs tillidsscorer er automatiserede vurderinger baseret på offentligt tilgængelige signaler. De udgør ikke anbefalinger eller garantier. Foretag altid din egen verificering.

Vi bruger cookies til analyse og caching. Privatliv