Ist Mcp All sicher?
Mcp All — Nerq Trust Score 42.5/100 (Note E). Bewertung basierend auf 3 independent trust signals.
Mcp All ist ein software tool mit einem Nerq-Vertrauenswert von 42.5/100 (E), basierend auf 3 unabhängigen Datendimensionen. Wartung: 0/100. Beliebtheit: 0/100. Daten von mehreren öffentlichen Quellen einschließlich Paketregistern, GitHub, NVD, OSV.dev und OpenSSF Scorecard. Zuletzt aktualisiert: n/a. Maschinenlesbare Daten (JSON).
Ist Mcp All sicher?
Vertrauensbewertung im Detail — Mcp All has a Nerq Trust Score of 42.5/100 (E). Measured across 3 independent trust signals.
Was ist die Vertrauensbewertung von Mcp All?
Mcp All hat eine Nerq-Vertrauensbewertung von 42.5/100 und erhält die Note E. Diese Bewertung basiert auf 3 unabhängig gemessenen Dimensionen.
Was sind die wichtigsten Sicherheitsergebnisse für Mcp All?
Das stärkste Signal von Mcp All ist wartung mit 0/100. Es wurden keine bekannten Schwachstellen erkannt.
Was ist Mcp All und wer pflegt es?
| Autor | https://github.com/antonytm/mcp-all |
| Kategorie | Infrastructure |
| Sterne | 1 |
| Quelle | https://github.com/antonytm/mcp-all |
Beliebte Alternativen in infrastructure
What Is Mcp All?
Mcp All is a software tool in the infrastructure category: Meta-server for dynamically discovering and managing other MCP servers. It has 1 GitHub-Sternen. Nerq Trust Score: 42/100 (E).
Nerq independently analyzes every software tool, app, and extension across multiple trust signals including Sicherheit vulnerabilities, Wartung activity, license Konformität, and Community-Akzeptanz.
How Nerq Assesses Mcp All's Safety
Nerq's Trust Score is calculated from 13+ independent signals aggregated into five Dimensionen. Here is how Mcp All performs in each:
- Wartung (0/100): Mcp All 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 Dokumentation, usage examples, and contribution guidelines.
- Community (0/100): Community adoption is limited. Basierend auf GitHub-Sternen, forks, download counts, and ecosystem integrations.
The overall Trust Score of 42.5/100 (E) 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 All?
Mcp All is commonly evaluated by:
- Developers and teams working with infrastructure tools
- Organizations evaluating AI tools for their stack
- Researchers exploring AI capabilities in this domain
How to read the signals: Mcp All's measured signals (Wartung 0/100, Dokumentation 0/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 All's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — Überprüfen Sie das/die repository Sicherheit policy, open issues, and recent commits for signs of active Wartung.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for known vulnerabilities in Mcp All's dependency tree. - Bewertung permissions — Understand what access Mcp All requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Mcp All 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 All - Überprüfen Sie das/die license — Confirm that Mcp All'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 Sicherheit concerns openly. Low community engagement may indicate limited peer review of the codebase.
Common Safety Concerns with Mcp All
When evaluating whether Mcp All is safe, consider these category-specific risks:
Understand how Mcp All processes, stores, and transmits your data. Überprüfen Sie das/die tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Mcp All's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher Sicherheit risk.
Regularly check for updates to Mcp All. Sicherheit patches and bug fixes are only effective if you're running the latest version.
If Mcp All 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 All'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 All in violation of its license can expose your organization to legal liability.
Best Practices for Using Mcp All Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Mcp All while minimizing risk:
Periodically review how Mcp All is used in your workflow. Check for unexpected behavior, permissions drift, and Konformität with your Sicherheit policies.
Ensure Mcp All and all its dependencies are running the latest stable versions to benefit from Sicherheit patches.
Grant Mcp All only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Mcp All's Sicherheit advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Mcp All is used within your organization, including data handling guidelines and acceptable use cases.
Situations That Warrant Independent Review of Mcp All
Nerq's signals are one input. In the following situations, evaluate Mcp All'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 All's measured trust score of 42.5/100 and its individual signals against your organization's own criteria. Nerq does not assert whether Mcp All is suitable for any particular use.
How Mcp All 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. Mcp All's score of 42.5/100 is below the category average of 62/100.
This suggests that Mcp All trails behind many comparable infrastructure tools. Organizations with strict Sicherheit 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 Mcp All 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 Wartung patterns change, Mcp All'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 Sicherheit and quality. Conversely, a downward trend may signal reduced Wartung, growing technical debt, or unresolved vulnerabilities. To track Mcp All's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=MCP All&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 — Sicherheit, Wartung, Dokumentation, Konformität, and community — has evolved independently, providing granular visibility into which aspects of Mcp All are strengthening or weakening over time.
Mcp All vs Alternativen
In the infrastructure category, Mcp All scores 42.5/100. There are higher-scoring alternatives available. For a detailed comparison, see:
- Mcp All vs n8n — Trust Score: 69.1/100
- Mcp All vs langflow — Trust Score: 77.0/100
- Mcp All vs dify — Trust Score: 69.7/100
Wichtigste Punkte
- Mcp All has a measured Nerq Trust Score of 42.5/100 (E) — a composite of independent signals, not a suitability judgment.
- Among infrastructure tools, Mcp All scores below the category average of 62/100 (a positional measurement relative to peers).
- The individual signals — Sicherheit, Wartung, Dokumentation, Konformität, community — are shown above. Weigh them against your own requirements.
- Query the current measured values via Nerq's Preflight API.
Häufig gestellte Fragen
Ist Mcp All sicher?
Was ist die Vertrauensbewertung von Mcp All?
Was sind sicherere Alternativen zu Mcp All?
Wie oft wird die Sicherheitsbewertung von Mcp All aktualisiert?
Kann ich Mcp All in einer regulierten Umgebung verwenden?
Siehe auch
Disclaimer: Nerq-Vertrauensbewertungen sind automatisierte Bewertungen basierend auf öffentlich verfügbaren Signalen. Sie sind keine Empfehlungen oder Garantien. Führen Sie immer Ihre eigene Sorgfaltsprüfung durch.