Is Screaming Frog Mcp Safe? — Trust Score: 0/100

According to Nerq's independent analysis of screaming frog mcp, this uncategorized has a trust score of 0 out of 100, earning a N/A grade. With 0 stars on unknown, it is below the recommended threshold of 70. Data sourced from 13+ independent signals including GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-03-18. Machine-readable data (JSON).

screaming frog mcp has a Nerq Trust Score of 0/100 (N/A). Not yet Nerq Verified (requires 70+). Last verified: 2026-03-18.

Is Screaming Frog Mcp safe?

NO — USE WITH CAUTION — Screaming Frog Mcp has a Nerq Trust Score of 0/100 (N/A). It has below-average trust signals with significant gaps in security, maintenance, or documentation. Not recommended for production use without thorough manual review and additional security measures.

out of 100

N/A uncategorized unknown

Trust Assessment

Low Trust — screaming frog mcp has significant trust concerns across multiple dimensions. We recommend thorough investigation before use. Consider higher-rated alternatives in the same category.

Trust Signal Breakdown

Overall Trust

Composite score across all trust dimensions.

Details

Author	Unknown
Category	uncategorized
Stars	0
Source	N/A

Community Reviews

No reviews yet. Be the first to review screaming frog mcp.

What Is Screaming Frog Mcp?

Screaming Frog Mcp is a AI tool in the uncategorized category. a AI tool in the uncategorized category

As of March 2026, Screaming Frog Mcp is available on unknown, making it an emerging tool in the AI ecosystem. But popularity alone does not equal safety — which is why Nerq independently analyzes every tool across 13+ trust signals.

How Nerq Assesses Screaming Frog Mcp's Safety

Nerq evaluates every AI tool across 13+ independent trust signals drawn from public sources including GitHub, NVD, OSV.dev, OpenSSF Scorecard, and package registries. These signals are grouped into five core dimensions: Security (known CVEs, dependency vulnerabilities, security policies), Maintenance (commit frequency, release cadence, issue response times), Documentation (README quality, API docs, examples), Compliance (license, regulatory alignment across 52 jurisdictions), and Community (stars, forks, downloads, ecosystem integrations).

Screaming Frog Mcp receives an overall Trust Score of 0.0/100 (N/A), which Nerq considers low. This is below the Nerq Verified threshold of 70. We recommend additional due diligence before production deployment.

Nerq updates trust scores continuously as new data becomes available. To get the latest assessment, query the API: GET nerq.ai/v1/preflight?target=screaming frog mcp

Each dimension is weighted according to its importance for the tool's category. For example, Security and Maintenance carry higher weight for tools that handle sensitive data or execute code, while Community and Documentation are weighted more heavily for developer-facing libraries and frameworks. This ensures that Screaming Frog Mcp's score reflects the risks most relevant to its actual usage patterns. The final score is a weighted average across all five dimensions, normalized to a 0-100 scale with letter grades from A (highest) to F (lowest).

Who Should Use Screaming Frog Mcp?

Screaming Frog Mcp is designed for:

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

Risk guidance: We recommend caution with Screaming Frog Mcp. The low trust score suggests potential risks in security, maintenance, or community support. Consider using a more established alternative for any production or sensitive workload.

How to Verify Screaming Frog Mcp's Safety Yourself

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

Check the source code — Review the repository security policy, open issues, and recent commits for signs of active maintenance.
Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for known vulnerabilities in Screaming Frog Mcp's dependency tree.
Review permissions — Understand what access Screaming Frog Mcp requires. AI tools should follow the principle of least privilege.
Test in isolation — Run Screaming Frog Mcp 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=screaming frog mcp
Review the license — Confirm that Screaming Frog 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.
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 Screaming Frog Mcp

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

Data handling

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

Dependency security

Check Screaming Frog Mcp's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher security risk.

Update frequency

Regularly check for updates to Screaming Frog Mcp. Security patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

If Screaming Frog 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 compliance

Verify that Screaming Frog 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 Screaming Frog Mcp in violation of its license can expose your organization to legal liability.

Best Practices for Using Screaming Frog Mcp Safely

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

Conduct regular audits

Periodically review how Screaming Frog Mcp is used in your workflow. Check for unexpected behavior, permissions drift, and compliance with your security policies.

Keep dependencies updated

Ensure Screaming Frog Mcp and all its dependencies are running the latest stable versions to benefit from security patches.

Follow least privilege

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

Monitor for security advisories

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

When Should You Avoid Screaming Frog Mcp?

Even promising tools aren't right for every situation. Consider avoiding Screaming Frog Mcp in these scenarios:

Production environments handling sensitive customer data
Regulated industries (healthcare, finance, government) without additional compliance review
Mission-critical systems where downtime has significant business impact

For each scenario, evaluate whether Screaming Frog Mcp's trust score of 0.0/100 meets your organization's risk tolerance. We recommend running a manual security assessment alongside the automated Nerq score.

How Screaming Frog Mcp Compares to Industry Standards

Nerq indexes over 204,000 AI agents and tools across dozens of categories. Among uncategorized tools, the average Trust Score is 62/100. Screaming Frog Mcp's score of 0.0/100 is below the category average of 62/100.

This suggests that Screaming Frog Mcp trails behind many comparable uncategorized tools. Organizations with strict security 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 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 Screaming Frog 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, Screaming Frog 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 Screaming Frog Mcp's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=screaming frog 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 Screaming Frog Mcp are strengthening or weakening over time.

Key Takeaways

Screaming Frog Mcp has a Trust Score of 0.0/100 (N/A) and is not yet Nerq Verified.
Screaming Frog Mcp has significant trust gaps. Consider higher-rated alternatives unless specific requirements mandate its use.
Among uncategorized tools, Screaming Frog Mcp scores below the category average of 62/100, suggesting room for improvement relative to peers.
Always verify safety independently — use Nerq's Preflight API for automated, up-to-date trust checks before integration.

Frequently Asked Questions

Is screaming frog mcp safe to use?

screaming frog mcp has a Nerq Trust Score of 0/100, earning a N/A grade. Low Trust — screaming frog mcp has significant trust concerns across multiple dimensions. We recommend thorough investigation before use. Consider higher-rated alternatives in the same category. Its strongest signal is overall trust (0/100). It has not yet reached the Nerq Verified threshold of 70. Always review the full KYA report before using any AI agent in production.

What is screaming frog mcp's trust score?

Nerq assigns screaming frog mcp a trust score of 0 out of 100, with a grade of N/A. This score is computed from multiple dimensions including security, compliance, maintenance activity, documentation quality, and community adoption (0 stars). Scores are updated daily based on the latest publicly available signals.

Are there safer alternatives to screaming frog mcp?

In the uncategorized category, no higher-rated alternatives were found — this is among the top-rated agents. screaming frog mcp scores 0/100. When choosing between agents, consider your specific requirements for security (N/A), maintenance activity (N/A), and documentation (N/A). Use Nerq's comparison tools or the KYA endpoint for detailed side-by-side analysis.

How often is Screaming Frog Mcp's safety score updated?

Nerq continuously monitors Screaming Frog Mcp and updates its trust score as new data becomes available. The system ingests signals from 13+ independent sources including GitHub, NVD (National Vulnerability Database), OSV.dev, OpenSSF Scorecard, and major package registries (npm, PyPI). When a new CVE is disclosed, a dependency is updated, or commit activity changes, the score adjusts automatically. For the most current score, query the Nerq API: GET nerq.ai/v1/preflight?target=screaming frog mcp. The current assessment (0/100, N/A) was last verified on 2026-03-18.

Can I use Screaming Frog Mcp in a regulated environment?

Screaming Frog Mcp has not yet reached the Nerq Verified threshold of 70, which means additional due diligence is recommended for regulated environments. Nerq assesses regulatory alignment across 52 jurisdictions including the EU AI Act, GDPR, CCPA, and sector-specific frameworks. For organizations in regulated industries (healthcare, finance, government), we recommend combining the Nerq Trust Score with your internal security review process, vendor risk assessment, and legal compliance check before deployment.

Add This Badge to YOUR Project

Show users your project is trusted. Add this badge to your README:

[![Nerq Trust Score](https://nerq.ai/badge/screaming frog mcp)](https://nerq.ai/safe/screaming-frog-mcp)

Click to copy. Works on GitHub, GitLab, and any markdown renderer.

Scan your project

pip install nerq && nerq scan

Scans all dependencies for trust scores and security issues.

Integrate trust checks

curl nerq.ai/v1/preflight?target=screaming-frog-mcp

API docs →

Improve this score

See recommendations →

Verify any agent

Browse uncategorized

All agents · MCP servers · Compare · Gateway

Related Safety Checks

Is Cursor safe? Is ChatGPT safe? Is Claude safe? Is Windsurf safe? Is Bolt safe? Is Cline safe? Is GitHub Copilot safe? Is Gemini safe? Is Ollama safe? Is LangChain safe? Is OpenAI safe? Is n8n safe? Is ComfyUI safe? Is CrewAI safe? Is AutoGPT safe? Is Devin safe? Is Continue safe? Is LlamaIndex safe? Is Hugging Face safe? Is Stable Diffusion safe?

Disclaimer: Nerq trust scores are automated assessments based on publicly available signals. They are not endorsements or guarantees. Always conduct your own due diligence.