Czy Mcp Server Database jest bezpieczny?
Mcp Server Database — Nerq Trust Score 74.0/100 (Ocena B). Na podstawie analizy 5 wymiarów zaufania, jest ogólnie bezpieczny, ale z pewnymi zastrzeżeniami. Ostatnia aktualizacja: 2026-04-18.
Tak, Mcp Server Database jest bezpieczny w użyciu. Mcp Server Database to software tool z wynikiem zaufania Nerq 74.0/100 (B), based on 5 niezależnych wymiarów danych. Zalecane do użytku. Bezpieczeństwo: 0/100. Konserwacja: 1/100. Popularność: 0/100. Dane pochodzą z wiele źródeł publicznych, w tym rejestry pakietów, GitHub, NVD, OSV.dev i OpenSSF Scorecard. Ostatnia aktualizacja: 2026-04-18. Dane odczytywalne maszynowo (JSON).
Czy Mcp Server Database jest bezpieczny?
YES — Mcp Server Database has a Nerq Trust Score of 74.0/100 (B). Spełnia próg zaufania Nerq z silnymi sygnałami w zakresie bezpieczeństwa, konserwacji i przyjęcia przez społeczność. Zalecane do użytku — zapoznaj się z pełnym raportem poniżej, aby uzyskać szczegółowe informacje.
Jaki jest wynik zaufania Mcp Server Database?
Mcp Server Database ma Nerq Trust Score 74.0/100 z oceną B. Ten wynik opiera się na 5 niezależnie mierzonych wymiarach, w tym bezpieczeństwie, konserwacji i adopcji społeczności.
Jakie są kluczowe ustalenia bezpieczeństwa dla Mcp Server Database?
Najsilniejszy sygnał Mcp Server Database to zgodność na poziomie 100/100. Nie wykryto znanych luk w zabezpieczeniach. It meets the Nerq Verified threshold of 70+.
Czym jest Mcp Server Database i kto go utrzymuje?
| Autor | marlonbarreto-git |
| Kategoria | Data |
| Źródło | https://github.com/marlonbarreto-git/mcp-server-database |
| Frameworks | mcp |
| Protocols | mcp |
Zgodność z przepisami
| EU AI Act Risk Class | MINIMAL |
| Compliance Score | 100/100 |
| Jurisdictions | Assessed across 52 jurisdictions |
Popularne alternatywy w data
What Is Mcp Server Database?
Mcp Server Database is a software tool in the data category: An MCP server enabling safe LLM-powered SQL queries with read-only access. Nerq Trust Score: 74/100 (B).
Nerq independently analyzes every software tool, app, and extension across multiple trust signals including bezpieczeństwo vulnerabilities, konserwacja activity, license zgodność, and przyjęcie przez społeczność.
How Nerq Assesses Mcp Server Database's Safety
Nerq's Trust Score is calculated from 13+ independent signals aggregated into five wymiarów. Here is how Mcp Server Database performs in each:
- Bezpieczeństwo (0/100): Mcp Server Database's bezpieczeństwo posture is poor. This score factors in known CVEs, dependency vulnerabilities, bezpieczeństwo policy presence, and code signing practices.
- Konserwacja (1/100): Mcp Server Database 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 dokumentacja, usage examples, and contribution guidelines.
- Compliance (100/100): Mcp Server Database is broadly compliant. Assessed against regulations in 52 jurisdictions including the EU AI Act, CCPA, and GDPR.
- Community (0/100): Community adoption is limited. Na podstawie GitHub stars, forks, download counts, and ecosystem integrations.
The overall Trust Score of 74.0/100 (B) reflects the weighted combination of these signals. This exceeds the Nerq Verified threshold of 70, indicating the tool meets our standards for production use.
Who Should Use Mcp Server Database?
Mcp Server Database is designed for:
- Developers and teams working with data tools
- Organizations evaluating AI tools for their stack
- Researchers exploring AI capabilities in this domain
Risk guidance: Mcp Server Database meets the minimum threshold for production use, but we recommend monitoring for bezpieczeństwo advisories and keeping dependencies up to date. Consider implementing additional guardrails for sensitive workloads.
How to Verify Mcp Server Database's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — Sprawdź repository's bezpieczeństwo policy, open issues, and recent commits for signs of active konserwacja.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for known vulnerabilities in Mcp Server Database's dependency tree. - Opinia permissions — Understand what access Mcp Server Database requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Mcp Server Database 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-server-database - Sprawdź license — Confirm that Mcp Server Database'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 bezpieczeństwo concerns openly. Low community engagement may indicate limited peer review of the codebase.
Common Safety Concerns with Mcp Server Database
When evaluating whether Mcp Server Database is safe, consider these category-specific risks:
Understand how Mcp Server Database processes, stores, and transmits your data. Sprawdź tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Mcp Server Database's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher bezpieczeństwo risk.
Regularly check for updates to Mcp Server Database. Bezpieczeństwo patches and bug fixes are only effective if you're running the latest version.
If Mcp Server Database 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 Server Database'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 Server Database in violation of its license can expose your organization to legal liability.
Mcp Server Database and the EU AI Act
Mcp Server Database 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 zgodność assessment covers 52 jurisdictions worldwide. For organizations deploying AI tools in regulated environments, understanding these classifications is essential for legal zgodność.
Best Practices for Using Mcp Server Database Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Mcp Server Database while minimizing risk:
Periodically review how Mcp Server Database is used in your workflow. Check for unexpected behavior, permissions drift, and zgodność with your bezpieczeństwo policies.
Ensure Mcp Server Database and all its dependencies are running the latest stable versions to benefit from bezpieczeństwo patches.
Grant Mcp Server Database only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Mcp Server Database's bezpieczeństwo advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Mcp Server Database is used within your organization, including data handling guidelines and acceptable use cases.
When Should You Avoid Mcp Server Database?
Even well-trusted tools aren't right for every situation. Consider avoiding Mcp Server Database in these scenarios:
- Scenarios where Mcp Server Database's specific capabilities exceed your actual needs — simpler tools may be safer
- Air-gapped environments where the tool cannot receive bezpieczeństwo updates
- Projects with strict regulatory requirements that haven't been explicitly validated
For each scenario, evaluate whether Mcp Server Database's trust score of 74.0/100 meets your organization's risk tolerance. The Nerq Verified status indicates general production readiness, but sector-specific requirements may apply.
How Mcp Server Database Compares to Industry Standards
Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among data tools, the average Trust Score is 62/100. Mcp Server Database's score of 74.0/100 is significantly above the category average of 62/100.
This places Mcp Server Database in the top tier of data tools that Nerq tracks. Tools scoring this far above average typically demonstrate mature bezpieczeństwo practices, consistent release cadence, and broad przyjęcie przez społeczność.
Industry benchmarks matter because they contextualize a tool's safety profile. A score that looks umiarkowany 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 Server Database 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 konserwacja patterns change, Mcp Server Database'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 bezpieczeństwo and quality. Conversely, a downward trend may signal reduced konserwacja, growing technical debt, or unresolved vulnerabilities. To track Mcp Server Database's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=mcp-server-database&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 — bezpieczeństwo, konserwacja, dokumentacja, zgodność, and community — has evolved independently, providing granular visibility into which aspects of Mcp Server Database are strengthening or weakening over time.
Mcp Server Database vs Alternatywy
In the data category, Mcp Server Database scores 74.0/100. There are higher-scoring alternatives available. For a detailed comparison, see:
- Mcp Server Database vs firecrawl — Trust Score: 73.8/100
- Mcp Server Database vs MinerU — Trust Score: 84.6/100
- Mcp Server Database vs mindsdb — Trust Score: 77.5/100
Kluczowe wnioski
- Mcp Server Database has a Trust Score of 74.0/100 (B) and is Nerq Verified.
- Mcp Server Database meets the minimum threshold for production deployment, though monitoring and additional guardrails are recommended.
- Among data tools, Mcp Server Database scores significantly above the category average of 62/100, demonstrating above-average reliability.
- Always verify safety independently — use Nerq's Preflight API for automated, up-to-date trust checks before integration.
Często zadawane pytania
Czy Mcp Server Database jest bezpieczny?
Jaki jest wynik zaufania Mcp Server Database?
Jakie są bezpieczniejsze alternatywy dla Mcp Server Database?
Jak często aktualizowana jest ocena bezpieczeństwa Mcp Server Database?
Czy mogę używać Mcp Server Database w środowisku regulowanym?
Zobacz także
Disclaimer: Wyniki zaufania Nerq to zautomatyzowane oceny oparte na publicznie dostępnych sygnałach. Nie stanowią rekomendacji ani gwarancji. Zawsze przeprowadzaj własną weryfikację.