Pod

Yes, this is on purpose. Pod is built for agents, so the default page is plain HTML.
Human? View the normal website.
Agent? You probably prefer /mcp/tradingview-mcp/issues.md or /mcp/tradingview-mcp/issues.json, or Pod over MCP.

Reported issues for tradingview-mcp

Pod holds 14 of 14 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to tradingview-mcp.

Most discussed

28 of 36 tools still block the event loop (and the async fan-out already double-spends the Marketaux budget)

README.md:56 states the problem exactly: "FastMCP runs sync tools serialized on the event loop." Seven hot-path tools were converted to async def with asyncio.to_thread offload, which is the right pattern.

The other 28 of 36 tools were not. So the server still serializes on most calls, and the asymmetry is arbitrary rather than principled:

Tool Handler Same underlying call
top_gainers async def → asyncio.to_thread fetch_trending_analysis
`top

Read the thread · 2026-07-10 · closed · external user · 1 comment

Error contract is half-migrated: 5 tools return structured envelopes, ~95 return sites still return strings

core/errors.py defines a clean structured envelope — stable string codes, a retryability signal, and an is_error() guard that deliberately distinguishes it from legacy payloads. It's good design. The module docstring says adoption is opt-in per tool, and README.md:222 tracks the adopted set by name.

The problem is that the migration stalled partway. As of main:

Read the thread · 2026-07-10 · open · external user · 2 comments

[BUG] walk_forward_backtest_strategy silently returns empty results when start_date > end_date

🐛 Bug Description

walk_forward_backtest_strategy does not validate that start_date < end_date. When called with the dates inverted (e.g. start_date="2026-01-01", end_date="2024-01-01"), the tool returns a successful response with empty / zero-trade results instead of a ValueError. This is misleading — users (especially LLM agents consuming the tool) cannot tell whether the empty result means "no data exists for the symbol" or "you passed invalid arguments".

backtest_strategy

Read the thread · 2026-06-13 · closed · external user · 2 comments

[HELP] Installation Issue:

🆘 Installation/Setup Help

📋 What are you trying to do?

🔧 Installation Method

📱 Your Environment

Read the thread · 2026-04-22 · closed · external user · 4 comments

[FEATURE] Add mexc data

🚀 Feature Request

Hi can u add mexc data source. As i see MEXC has a lot crypto trading pair that other exchanges don't have

🎯 Is your feature request related to a problem?

no

🛠️ Implementation Ideas

If you have ideas on how this could be implemented, please share them:

Technical Approach:

Read the thread · 2026-04-14 · closed · external user · 3 comments

Complement idea: "What happened next?" via Chart Library

Nice work on the TradingView MCP — getting real-time screening and indicators into AI agents is really useful.

One thing I noticed that could complement your data: the "what happened next?" question. Your server gives agents the current state (indicators, patterns, screening). Chart Library gives agents the historical context — "the last 10 times a chart looked like this, here's what happened."

Together an agent could say: "NVDA is showing a bullish engulfing pattern (from your server) a

Read the thread · 2026-03-30 · open · external user · 3 comments

[BUG]

This appears to only support KUCOIN, and doesn't look at my tradingview AT ALL.

Image

Read the thread · 2025-11-22 · closed · external user · 1 comment

[FEATURE] Docker image

Hello!

would be super useful for me if you can provide a docker image of your MCP server :)

Cheers Daniel

Read the thread · 2025-10-26 · closed · external user · 3 comments

Most recent

MCP spec conformance: 7 requirement(s) violated (via @hasmcp/mcp-spec-test) — spec 2026-07-28

An automated MCP protocol conformance sweep using @hasmcp/mcp-spec-test found that tradingview-mcp rejects requests sent before the client completes the MCP handshake, including the server/discover capability-discovery request and a version-less tools/list. The spec expects server/discover (and a couple of other pre-handshake checks) to be answerable without an initialized session; this server instead returns -32602 Invalid request parameters (or times out entirely for the very first

Read the thread · 2026-08-24 · open · external user · 0 comments

[BUG] 7 tools hang forever under the stdio server: lazy import pandas deadlocks in a to_thread worker

Summary

Seven tools never return when called through the MCP stdio server — no error, no timeout, no traceback. The call just hangs and the client waits indefinitely. The same functions return in ~1.5s when called directly in-process.

Affected:

The other 25 tools I exercised work fine.

Environment

Read the thread · 2026-08-19 · closed · external user · 1 comment

Feature Suggestion: Optional token metering & paid API key support via neuforge-pay

Hi @atilaahmettaner,

Love the work on atilaahmettaner/tradingview-mcp! As usage grows across AI agent frameworks, server compute costs can start adding up quickly. We've also seen developers report that their autonomous agents accidentally burn through thousands of dollars in a single session because traditional payment rails lack built-in agent guardrails.

Would you be open to adding an optional usage metering & billing decorator using neuforge-pay? It acts as a proactive **Spend Firewall

Read the thread · 2026-08-15 · open · external user · 0 comments

[FEATURE] Range intervals

🚀 Feature Request

🎯 Is your feature request related to a problem?

I use range intervals rather than time based intervals

💡 Describe the solution you'd like

The MCP uses time-based intervals, not range intervals

🔄 Describe alternatives you've considered

giving it an understanding of range data rather than just time

📊 Use Case

plotting indicators

Read the thread · 2026-08-08 · open · external user · 0 comments

[FEATURE]

🚀 Feature Request

🎯 Is your feature request related to a problem?

A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

💡 Describe the solution you'd like

A clear and concise description of what you want to happen.

🔄 Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

📊 Use Case

Describe your specific use case and how this feature would benefit you and oth

Read the thread · 2026-06-15 · closed · external user · 1 comment

[BUG] walk_forward_backtest_strategy throws TypeError on MACD, Supertrend, and Ichimoku strategies

🐛 Bug Description

Calling walk_forward_backtest_strategy with strategy set to MACD, Supertrend, or Ichimoku raises a Python TypeError: '<' not supported between instances of 'dict' and 'dict' on every fold. Other strategies (EMA, Bollinger, RSI, Donchian, MA Crossover, Keltner, VWAP) run without error. backtest_strategy (non-walk-forward) on the same three strategies works fine — the bug is isolated to the walk-forward variant.

🔄 Steps to Reproduce

  1. Start the MCP server (`

Read the thread · 2026-06-13 · closed · external user · 1 comment

The remaining reports are on the project's issue tracker.