Is Mcp Safe?

Is Mcp safe?

YES — Mcp has a Nerq Trust Score of 84.7/100 (A). It meets Nerq's trust threshold with strong signals across security, maintenance, and community adoption. Recommended for use — review the full report below for specific considerations.

What Is Mcp?

Mcp is a DevOps tool: MCP Server for interacting with Salesforce instances. It has 284 GitHub stars. Nerq Trust Score: 85/100 (A).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including security vulnerabilities, maintenance activity, license compliance, and community adoption.

How Nerq Assesses Mcp's Safety

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

• Security (1/100): Mcp's security posture is poor. This score factors in known CVEs, dependency vulnerabilities, security policy presence, and code signing practices.
• Maintenance (1/100): Mcp 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 documentation, usage examples, and contribution guidelines.
• Compliance (100/100): Mcp is broadly compliant. Assessed against regulations in 52 jurisdictions including the EU AI Act, CCPA, and GDPR.
• Community (0/100): Community adoption is limited. Based on GitHub stars, forks, download counts, and ecosystem integrations.

The overall Trust Score of 84.7/100 (A) 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?

Mcp is designed for:

• Developers and teams working with devops tools
• Organizations evaluating AI tools for their stack
• Researchers exploring AI capabilities in this domain

Risk guidance: Mcp is well-suited for production environments. Its high trust score indicates robust security, active maintenance, and strong community support. Standard security practices (dependency pinning, access controls, monitoring) are still recommended.

How to Verify Mcp's Safety Yourself

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

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

Common Safety Concerns with Mcp

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

Mcp and the EU AI Act

Mcp 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 compliance assessment covers 52 jurisdictions worldwide. For organizations deploying AI tools in regulated environments, understanding these classifications is essential for legal compliance.

Best Practices for Using Mcp Safely

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

When Should You Avoid Mcp?

Even well-trusted tools aren't right for every situation. Consider avoiding Mcp in these scenarios:

• Scenarios where Mcp's specific capabilities exceed your actual needs — simpler tools may be safer
• Air-gapped environments where the tool cannot receive security updates
• Projects with strict regulatory requirements that haven't been explicitly validated

For each scenario, evaluate whether Mcp's trust score of 84.7/100 meets your organization's risk tolerance. The Nerq Verified status indicates general production readiness, but sector-specific requirements may apply.

How Mcp Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among DevOps tools, the average Trust Score is 63/100. Mcp's score of 84.7/100 is significantly above the category average of 63/100.

This places Mcp in the top tier of DevOps tools that Nerq tracks. Tools scoring this far above average typically demonstrate mature security practices, consistent release cadence, and broad community adoption.

Industry benchmarks matter because they contextualize a tool's safety profile. A score that looks moderate 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 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 maintenance patterns change, 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 security and quality. Conversely, a downward trend may signal reduced maintenance, growing technical debt, or unresolved vulnerabilities. To track Mcp's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=salesforcecli/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 — security, maintenance, documentation, compliance, and community — has evolved independently, providing granular visibility into which aspects of Mcp are strengthening or weakening over time.

Mcp vs Alternatives

In the devops category, Mcp scores 84.7/100. It ranks among the top tools in its category. For a detailed comparison, see:

• Mcp vs ansible — Trust Score: 84.3/100
• Mcp vs Flowise — Trust Score: 76.9/100
• Mcp vs learn-claude-code — Trust Score: 81.5/100

Key Takeaways

• Mcp has a Trust Score of 84.7/100 (A) and is Nerq Verified.
• Mcp demonstrates strong trust signals and is well-suited for production use with standard security precautions.
• Among DevOps tools, Mcp scores significantly above the category average of 63/100, demonstrating above-average reliability.
• Always verify safety independently — use Nerq's Preflight API for automated, up-to-date trust checks before integration.