Czy Paprika Mcp Python Server jest bezpieczny?
Paprika Mcp Python Server — Nerq Trust Score 65.3/100 (Ocena C). Wynik oparty na 5 independent trust signals.
Paprika Mcp Python Server to software tool z wynikiem zaufania Nerq 65.3/100 (C), based on 5 niezależnych wymiarów danych. 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: n/a. Dane odczytywalne maszynowo (JSON).
Czy Paprika Mcp Python Server jest bezpieczny?
Szczegóły wyniku zaufania — Paprika Mcp Python Server has a Nerq Trust Score of 65.3/100 (C). Measured across 5 independent trust signals.
Jaki jest wynik zaufania Paprika Mcp Python Server?
Paprika Mcp Python Server ma Nerq Trust Score 65.3/100 z oceną C. 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 Paprika Mcp Python Server?
Najsilniejszy sygnał Paprika Mcp Python Server to zgodność na poziomie 100/100. Nie wykryto znanych luk w zabezpieczeniach.
Czym jest Paprika Mcp Python Server i kto go utrzymuje?
| Autor | sandordaroczi |
| Kategoria | Productivity |
| Gwiazdki | 3 |
| Źródło | https://github.com/sandordaroczi/paprika-mcp-python-server |
| Frameworks | autogen · anthropic · mcp |
| Protocols | mcp · rest |
Zgodność z przepisami
| EU AI Act Risk Class | MINIMAL |
| Compliance Score | 100/100 |
| Jurisdictions | Assessed across 52 jurisdictions |
Popularne alternatywy w productivity
What Is Paprika Mcp Python Server?
Paprika Mcp Python Server is a software tool in the productivity category: A Model Context Protocol server for integrating Paprika Recipe Manager with Claude Desktop.. It has 3 GitHub stars. Nerq Trust Score: 65/100 (C).
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 Paprika Mcp Python Server's Safety
Nerq's Trust Score is calculated from 13+ independent signals aggregated into five wymiarów. Here is how Paprika Mcp Python Server performs in each:
- Bezpieczeństwo (0/100): Paprika Mcp Python Server'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): Paprika Mcp Python Server 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): Paprika Mcp Python Server 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 65.3/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 Paprika Mcp Python Server?
Paprika Mcp Python Server is commonly evaluated by:
- Developers and teams working with productivity tools
- Organizations evaluating AI tools for their stack
- Researchers exploring AI capabilities in this domain
How to read the signals: Paprika Mcp Python Server's measured signals (bezpieczeństwo 0/100, konserwacja 1/100, dokumentacja 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 Paprika Mcp Python Server'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 Paprika Mcp Python Server's dependency tree. - Opinia permissions — Understand what access Paprika Mcp Python Server requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Paprika Mcp Python Server 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=paprika-mcp-python-server - Sprawdź license — Confirm that Paprika Mcp Python Server'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 Paprika Mcp Python Server
When evaluating whether Paprika Mcp Python Server is safe, consider these category-specific risks:
Understand how Paprika Mcp Python Server processes, stores, and transmits your data. Sprawdź tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Paprika Mcp Python Server's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher bezpieczeństwo risk.
Regularly check for updates to Paprika Mcp Python Server. Bezpieczeństwo patches and bug fixes are only effective if you're running the latest version.
If Paprika Mcp Python Server 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 Paprika Mcp Python Server's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Paprika Mcp Python Server in violation of its license can expose your organization to legal liability.
Paprika Mcp Python Server and the EU AI Act
Paprika Mcp Python Server 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 Paprika Mcp Python Server Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Paprika Mcp Python Server while minimizing risk:
Periodically review how Paprika Mcp Python Server is used in your workflow. Check for unexpected behavior, permissions drift, and zgodność with your bezpieczeństwo policies.
Ensure Paprika Mcp Python Server and all its dependencies are running the latest stable versions to benefit from bezpieczeństwo patches.
Grant Paprika Mcp Python Server only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Paprika Mcp Python Server'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 Paprika Mcp Python Server is used within your organization, including data handling guidelines and acceptable use cases.
Situations That Warrant Independent Review of Paprika Mcp Python Server
Nerq's signals are one input. In the following situations, evaluate Paprika Mcp Python Server'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 Paprika Mcp Python Server's measured trust score of 65.3/100 and its individual signals against your organization's own criteria. Nerq does not assert whether Paprika Mcp Python Server is suitable for any particular use.
How Paprika Mcp Python Server Compares to Industry Standards
Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among productivity tools, the average Trust Score is 62/100. Paprika Mcp Python Server's score of 65.3/100 is above the category average of 62/100.
This positions Paprika Mcp Python Server favorably among productivity tools. While it outperforms the average, there is still room for improvement in certain trust wymiarów.
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 Paprika Mcp Python Server 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, Paprika Mcp Python Server'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 Paprika Mcp Python Server's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=paprika-mcp-python-server&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 Paprika Mcp Python Server are strengthening or weakening over time.
Paprika Mcp Python Server vs Alternatywy
In the productivity category, Paprika Mcp Python Server scores 65.3/100. There are higher-scoring alternatives available. For a detailed comparison, see:
- Paprika Mcp Python Server vs cherry-studio — Trust Score: 73.9/100
- Paprika Mcp Python Server vs ToolJet — Trust Score: 76.5/100
- Paprika Mcp Python Server vs posthog — Trust Score: 60.3/100
Kluczowe wnioski
- Paprika Mcp Python Server has a measured Nerq Trust Score of 65.3/100 (C) — a composite of independent signals, not a suitability judgment.
- Among productivity tools, Paprika Mcp Python Server scores above the category average of 62/100 (a positional measurement relative to peers).
- The individual signals — bezpieczeństwo, konserwacja, dokumentacja, zgodność, community — are shown above. Weigh them against your own requirements.
- Query the current measured values via Nerq's Preflight API.
Często zadawane pytania
Czy Paprika Mcp Python Server jest bezpieczny?
Jaki jest wynik zaufania Paprika Mcp Python Server?
Jakie są bezpieczniejsze alternatywy dla Paprika Mcp Python Server?
Jak często aktualizowana jest ocena bezpieczeństwa Paprika Mcp Python Server?
Czy mogę używać Paprika Mcp Python Server 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ę.