Mcpb có an toàn không?
Mcpb — Nerq Trust Score 67.9/100 (Hạng C). Điểm dựa tr��n 4 independent trust signals.
Mcpb là một software tool với Điểm tin cậy Nerq 67.9/100 (C), dựa trên 4 chiều dữ liệu độc lập. Bảo trì: 0/100. Độ phổ biến: 1/100. Dữ liệu từ nhiều nguồn công khai bao gồm registry gói, GitHub, NVD, OSV.dev và OpenSSF Scorecard. Cập nhật lần cuối: n/a. Dữ liệu máy đọc được (JSON).
Mcpb có an toàn không?
Chi tiết điểm tin cậy — Mcpb has a Nerq Trust Score of 67.9/100 (C). Measured across 4 independent trust signals.
Điểm tin cậy của Mcpb là bao nhiêu?
Mcpb có Điểm tin cậy Nerq là 67.9/100 với xếp hạng C. Điểm này dựa trên 4 chiều dữ liệu được đo lường độc lập bao gồm bảo mật, bảo trì và sự chấp nhận của cộng đồng.
Các phát hiện bảo mật chính của Mcpb là gì?
Tín hiệu mạnh nhất của Mcpb là tuân thủ ở mức 100/100. Không phát hiện lỗ hổng đã biết.
Mcpb là gì và ai duy trì nó?
| Nhà phát triển | modelcontextprotocol |
| Danh mục | Hạ Tầng |
| Sao | 1,717 |
| Nguồn | https://github.com/modelcontextprotocol/mcpb |
| Protocols | mcp |
Tuân thủ quy định
| EU AI Act Risk Class | Not assessed |
| Compliance Score | 100/100 |
| Quyền Tài Pháns | Assessed across 52 quyền tài pháns |
Lựa chọn phổ biến trong infrastructure
Mcpb trên các nền tảng khác
Cùng nhà phát triển/công ty trong các registry khác:
What Is Mcpb?
Mcpb is a software tool in the infrastructure category: Desktop Extensions: One-click local MCP server installation in desktop apps. It has 1,717 sao GitHub. Nerq Trust Score: 68/100 (C).
Nerq independently analyzes every software tool, app, and extension across multiple trust signals including bảo mật vulnerabilities, bảo trì activity, license tuân thủ, and sự chấp nhận của cộng đồng.
How Nerq Assesses Mcpb's Safety
Nerq's Trust Score is calculated from 13+ independent signals aggregated into five tiêu chí. Here is how Mcpb performs in each:
- Bảo trì (0/100): Mcpb 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 tài liệu, usage examples, and contribution guidelines.
- Compliance (100/100): Mcpb is broadly compliant. Assessed against regulations in 52 quyền tài pháns including the EU AI Act, CCPA, and GDPR.
- Community (1/100): Community adoption is limited. Dựa trên sao GitHub, forks, download counts, and ecosystem integrations.
The overall Trust Score of 67.9/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 Mcpb?
Mcpb 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: Mcpb's measured signals (bảo trì 0/100, tài liệu 0/100, community 1/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 Mcpb's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — Xem xét repository bảo mật policy, open issues, and recent commits for signs of active bảo trì.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for known vulnerabilities in Mcpb's dependency tree. - Đánh giá permissions — Understand what access Mcpb requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Mcpb 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=mcpb - Xem xét license — Confirm that Mcpb'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 bảo mật concerns openly. Low community engagement may indicate limited peer review of the codebase.
Common Safety Concerns with Mcpb
When evaluating whether Mcpb is safe, consider these category-specific risks:
Understand how Mcpb processes, stores, and transmits your data. Xem xét tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Mcpb's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher bảo mật risk.
Regularly check for updates to Mcpb. Bảo mật patches and bug fixes are only effective if you're running the latest version.
If Mcpb 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 Mcpb's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Mcpb in violation of its license can expose your organization to legal liability.
Best Practices for Using Mcpb Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Mcpb while minimizing risk:
Periodically review how Mcpb is used in your workflow. Check for unexpected behavior, permissions drift, and tuân thủ with your bảo mật policies.
Ensure Mcpb and all its dependencies are running the latest stable versions to benefit from bảo mật patches.
Grant Mcpb only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Mcpb's bảo mật advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Mcpb is used within your organization, including data handling guidelines and acceptable use cases.
Situations That Warrant Độc lập Review of Mcpb
Nerq's signals are one input. In the following situations, evaluate Mcpb'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 Mcpb's measured trust score of 67.9/100 and its individual signals against your organization's own criteria. Nerq does not assert whether Mcpb is suitable for any particular use.
How Mcpb 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. Mcpb's score of 67.9/100 is above the category average of 62/100.
This positions Mcpb favorably among infrastructure tools. While it outperforms the average, there is still room for improvement in certain trust tiêu chí.
Industry benchmarks matter because they contextualize a tool's safety profile. A score that looks trung bình 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 Mcpb 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 bảo trì patterns change, Mcpb'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 bảo mật and quality. Conversely, a downward trend may signal reduced bảo trì, growing technical debt, or unresolved vulnerabilities. To track Mcpb's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=mcpb&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 — bảo mật, bảo trì, tài liệu, tuân thủ, and community — has evolved independently, providing granular visibility into which aspects of Mcpb are strengthening or weakening over time.
Mcpb vs Lựa chọn thay thế
In the infrastructure category, Mcpb scores 67.9/100. There are higher-scoring alternatives available. For a detailed comparison, see:
- Mcpb vs n8n — Trust Score: 69.1/100
- Mcpb vs langflow — Trust Score: 77.0/100
- Mcpb vs dify — Trust Score: 69.7/100
Điểm chính
- Mcpb has a measured Nerq Trust Score of 67.9/100 (C) — a composite of independent signals, not a suitability judgment.
- Among infrastructure tools, Mcpb scores above the category average of 62/100 (a positional measurement relative to peers).
- The individual signals — bảo mật, bảo trì, tài liệu, tuân thủ, community — are shown above. Weigh them against your own requirements.
- Query the current measured values via Nerq's Preflight API.
Câu hỏi thường gặp
Mcpb có an toàn không?
Điểm tin cậy của Mcpb là bao nhiêu?
Các lựa chọn an toàn hơn Mcpb là gì?
Điểm an toàn của Mcpb được cập nhật bao lâu một lần?
Tôi có thể sử dụng Mcpb trong môi trường được quản lý không?
Xem thêm
Disclaimer: Điểm tin cậy Nerq là đánh giá tự động dựa trên tín hiệu công khai. Đây không phải khuyến nghị hay bảo đảm. Hãy luôn tự xác minh.