tradingview-mcp (pueschel88/Tradingview-MCP) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 11 tools. No publisher has claimed this listing.

C
Emerging
74/100
20 days ago

tradingview-mcp

Enables MCP clients to control a local TradingView Desktop instance, providing tools to read chart state, change symbols and timeframes, and fetch OHLCV data.

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

pueschel88

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Known vulnerabilities in dependencies: 1 critical
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 1 credential: TV_MCP_REDIS_PASSWORD
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 critical

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalvitest@2.1.9GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configTV_MCP_HOSTlocalhost CDP host
configTV_MCP_PORT"": "9222",
configTV_MCP_REDIS_DB0 Redis database index
configTV_MCP_REDIS_ENABLEDIf Redis is not running, the server still works — it logs a warning and skips caching. Set =false to disable Redis entirely.
configTV_MCP_REDIS_HOST"": "127.0.0.1",
configTV_MCP_REDIS_KEY_PREFIXtradingview-mcp: Key prefix for cached entries
🔐 secretTV_MCP_REDIS_PASSWORD(none) Redis password, if required
configTV_MCP_REDIS_PORT"": "6379"
configTV_MCP_REDIS_TTL_OHLCV60 OHLCV cache TTL in seconds
configTV_MCP_REDIS_TTL_QUOTE5 Quote cache TTL in seconds
configTV_MCP_REDIS_TTL_STATE5 Chart state cache TTL in seconds
configTV_MCP_TARGET(auto-detect) Explicit CDP target ID — only needed if you have multiple TradingView windows open
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

11/11 tools missing one or more hints — chart_get_state (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); chart_set_symbol (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); chart_set_timeframe (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +8 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Dev dependencies

1 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 3 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/pueschel88/tradingview-mcp)](https://m8ven.ai/mcp/pueschel88/tradingview-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: a255b81c84285ab87e688ee0a3f32ef3a100ef92
code hash: c03dd588c4788d04d59e749892c1438352216bbe4d59157e189b0c985c34c9ce
verified: 8/20/2026, 7:09:08 PM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client