Är Philidor Mcp säker?

Philidor Mcp — Nerq Trust Score 42.5/100 (Betyg E). Poäng baserad på 4 independent trust signals.

Philidor Mcp är en programvara med ett Nerq-förtroendepoäng på 42.5/100 (E), baserat på 4 oberoende datadimensioner. Säkerhet: 0/100. Underhåll: 0/100. Popularitet: 0/100. Data hämtad från flera offentliga källor inklusive paketregister, GitHub, NVD, OSV.dev och OpenSSF Scorecard. Senast uppdaterad: n/a. Maskinläsbar data (JSON).

Är Philidor Mcp säker?

Förtroendepoäng i detalj — Philidor Mcp has a Nerq Trust Score of 42.5/100 (E). Measured across 4 independent trust signals.

Säkerhetsanalys → Philidor Mcp integritetsrapport →

Vad är Philidor Mcps förtroendepoäng?

Philidor Mcp har ett Nerq-förtroendepoäng på 42.5/100 med betyget E. Denna poäng baseras på 4 oberoende mätta dimensioner inklusive säkerhet, underhåll och communityanvändning.

Säkerhet
0
Underhåll
0
Dokumentation
0
Popularitet
0

Vilka är de viktigaste säkerhetsresultaten för Philidor Mcp?

Philidor Mcps starkaste signal är säkerhet på 0/100. Inga kända sårbarheter har upptäckts.

⚠Säkerhetspoäng: 0/100 (svag)
⚠Underhåll: 0/100 — låg underhållsaktivitet
⚠Dokumentation: 0/100 — begränsad dokumentation
⚠Popularitet: 0/100 — 4 stjärnor på mcp

Vad är Philidor Mcp och vem underhåller det?

UtvecklarePhilidor-Labs
KategoriInfrastruktur
Stjärnor4
Källahttps://github.com/Philidor-Labs/philidor-mcp
Protocolsmcp

Populära alternativ inom infrastructure

n8n-io/n8n
69.1/100 · C
github
langflow-ai/langflow
77.0/100 · B
github
langgenius/dify
69.7/100 · C
github
open-webui/open-webui
60.4/100 · C
github
google-gemini/gemini-cli
56.2/100 · D
github

What Is Philidor Mcp?

Philidor Mcp is a programvara in the infrastructure category: MCP server for DeFi vault risk analytics. Search 700+ vaults, compare risk scores, analyze protocols. No API key needed.. It has 4 GitHub-stjärnor. Nerq Trust Score: 42/100 (E).

Nerq independently analyzes every programvara, app, and extension across multiple trust signals including säkerhet vulnerabilities, underhåll activity, license regelefterlevnad, and communityanvändning.

How Nerq Assesses Philidor Mcp's Safety

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

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 Philidor Mcp?

Philidor Mcp is commonly evaluated by:

How to read the signals: Philidor Mcp's measured signals (säkerhet 0/100, underhåll 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 Philidor Mcp's Safety Yourself

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

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

Common Safety Concerns with Philidor Mcp

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

Data handling

Understand how Philidor Mcp processes, stores, and transmits your data. Granska tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency säkerhet

Check Philidor Mcp's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher säkerhet risk.

Update frequency

Regularly check for updates to Philidor Mcp. Säkerhet patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

If Philidor Mcp 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 regelefterlevnad

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

Best Practices for Using Philidor Mcp Safely

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

Conduct regular audits

Periodically review how Philidor Mcp is used in your workflow. Check for unexpected behavior, permissions drift, and regelefterlevnad with your säkerhet policies.

Keep dependencies updated

Ensure Philidor Mcp and all its dependencies are running the latest stable versions to benefit from säkerhet patches.

Follow least privilege

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

Monitor for säkerhet advisories

Subscribe to Philidor Mcp's säkerhet 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 Philidor Mcp is used within your organization, including data handling guidelines and acceptable use cases.

Situations That Warrant Oberoende Review of Philidor Mcp

Nerq's signals are one input. In the following situations, evaluate Philidor Mcp's measured signals against your own requirements before making a decision:

For each situation, compare Philidor Mcp's measured trust score of 42.5/100 and its individual signals against your organization's own criteria. Nerq does not assert whether Philidor Mcp is suitable for any particular use.

How Philidor Mcp Compares to Industry Standards

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

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

Philidor Mcp vs Alternativ

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

Viktigaste slutsatser

Vanliga frågor

Är Philidor Mcp säker?
philidor-mcp med ett Nerq-förtroendepoäng på 42.5/100 (E). Starkaste signalen: säkerhet (0/100). Poäng baserad på Säkerhet (0/100), Underhåll (0/100), Popularitet (0/100), Dokumentation (0/100).
Vad är Philidor Mcps förtroendepoäng?
philidor-mcp: 42.5/100 (E). Poäng baserad på Säkerhet (0/100), Underhåll (0/100), Popularitet (0/100), Dokumentation (0/100). Poäng uppdateras när ny data finns tillgänglig. API: GET nerq.ai/v1/preflight?target=philidor-mcp
Vilka är säkrare alternativ till Philidor Mcp?
I kategorin Infrastruktur, higher-rated alternatives include n8n-io/n8n (69/100), langflow-ai/langflow (77/100), langgenius/dify (70/100). philidor-mcp scores 42.5/100.
Hur ofta uppdateras Philidor Mcps säkerhetspoäng?
Nerq recomputes Philidor Mcp's trust score as new data becomes available. Current: 42.5/100 (E). API: GET nerq.ai/v1/preflight?target=philidor-mcp
Kan jag använda Philidor Mcp i en reglerad miljö?
Philidor Mcp: 42.5/100 (E). Compliance signals are shown in the breakdown above. Evaluate against your own regulatory requirements.
API: /v1/preflight Trust Badge API Docs

Se även

Disclaimer: Nerqs förtroendepoäng är automatiserade bedömningar baserade på offentligt tillgängliga signaler. De utgör inte rekommendationer eller garantier. Gör alltid din egen verifiering.

Vi använder cookies för analys och cachelagring. Integritet