tradingview-mcp Security Audit Report

🔭 Continuously monitored by ClawSecure Watchtower

Source:

SHA-256:

tradingview-mcp is an AI agent skill, created by atilaahmettaner and published at atilaahmettaner/tradingview-mcp. ClawSecure audited tradingview-mcp across 76 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 55/100 (Warning). The 5 findings concentrate in Code Injection and Permissions Manifest, including Potentially dangerous code pattern detected: curl.*\|.*sh and Potentially dangerous code pattern detected: curl.*\|.*sh. 4 were rated high or critical severity.

Is tradingview-mcp safe?

ClawSecure audited tradingview-mcp and assigned a security score of 55/100 (Warning), identifying 5 findings across Code Injection and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in tradingview-mcp?

ClawSecure identified 5 findings in tradingview-mcp, concentrated in Code Injection and Permissions Manifest. 4 were rated high or critical severity. The most severe include Potentially dangerous code pattern detected: curl.*\|.*sh and Potentially dangerous code pattern detected: curl.*\|.*sh.

How was tradingview-mcp audited?

ClawSecure ran tradingview-mcp through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 76 files from atilaahmettaner/tradingview-mcp.

What does a score of 55 mean?

ClawSecure assigned tradingview-mcp a security score of 55/100, placing it in the Warning range. This is driven by 5 findings led by Code Injection that should be addressed before use. ClawSecure derives this score with a weighted deduction model (critical -20, high -10, medium -5, low -2 from a base of 100).

Audit Findings for tradingview-mcp

ClawSecure detected 5 security findings in tradingview-mcp, spanning Code Injection and Permissions Manifest.

high · Potentially dangerous code pattern detected: curl.*\|.*sh. Code Injection finding detected in CONTRIBUTING.md.
high · Potentially dangerous code pattern detected: curl.*\|.*sh. Code Injection finding detected in INSTALLATION.md.
high · Potentially dangerous code pattern detected: curl.*\|.*sh. Code Injection finding detected in OPENCLAW.md.
high · Potentially dangerous code pattern detected: curl.*\|.*sh. Code Injection finding detected in README.md.
medium · Missing config.json - agent may not be properly configured. Permissions Manifest finding.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for tradingview-mcp

Eliminate dynamic code execution

tradingview-mcp evaluates code at runtime (for example eval or dynamic exec). Remove dynamic evaluation of untrusted input, and where code generation is unavoidable, sandbox it and validate every input.

Add a config.json permissions manifest

A config.json file declares what an agent component can access: file system, network, shell execution and more. Without it, users have no visibility into what the component can do before installing. This is the single most impactful security improvement for any AI agent skill.

Pin dependencies to exact versions

Unpinned dependencies allow supply-chain attacks where a compromised version is pulled in automatically. Use exact version numbers in package.json (for example 1.2.3 instead of ^1.2.3) to keep unauthorized code out of your dependency tree. ClawSecure checks every dependency against known CVE databases.

Related Security Research

Why Generic Scanners Fail at AI Agent Security→Beyond Static Scans: Why ClawSecure Verifies Agentic Intent→How to Secure an MCP Server: The 2026 Guide→

Related AI Agent Security Audits

openclaw-token-optimizerScore 46/100 tradingview-mcpScore 55/100 tradingview-mcpScore 55/100 jiraScore 50/100 playwright-best-practicesScore 63/100

Scanned on October 14, 2026. tradingview-mcp is one of thousands of agents audited by ClawSecure from the community-curated awesome-openclaw-skills list and the openclaw/skills repository.

Start Your Free Scan