Signal source

A signal source is wherever a trade instruction originates: a Telegram channel or group, a TradingView strategy or indicator alert, an AI assistant connected through MCP, or a manual entry in a dashboard; the source decides what to trade, and the execution platform decides whether and how.

Why it matters

Sources differ in format, reliability and delay. A TradingView strategy is deterministic and fires as soon as its condition is met; a Telegram channel is written by a person, posts irregularly and may edit or delete; an AI assistant can reason about context but needs a policy wall so a prompt cannot make it exceed your limits. A platform that treats all of them the same way either over-trusts the human sources or under-uses the automated ones. Choosing the source is also a plan decision: some plans allow one source at a time, others several in parallel.

How AlgoVesta handles it

AlgoVesta accepts three source types, Telegram, TradingView and MCP, plus manual trades from the dashboard, and applies the same risk layer to all of them. Each bot is tied to one source and one target account, and each source has its own intake: Telegram through your own account session, TradingView through a per-strategy webhook URL with source verification, MCP through a scoped key that lets Claude, ChatGPT or Cursor trade behind server-side rules. Every executed trade records its source, and the dashboard labels positions by where they came from so a TradingView position is never shown as a Telegram one. Plan limits apply per source type: the Starter plan runs one source and one market at a time, Pro and Elite run several. Details are on the Telegram, TradingView and MCP feature pages.

Example

A Pro user runs three bots: a Telegram bot mirroring a gold channel into an MT5 account, a TradingView bot executing a breakout strategy on Bybit futures, and an MCP connection letting an AI assistant manage a small paper account. Each bot has its own size and risk rules; the dashboard shows all positions with their source label, and the MCP assistant cannot exceed the limits set for its key.

Common mistakes

• Pointing two sources at the same account and symbol without shared exposure limits.
• Trusting a source's advertised results without paper-testing its actual message format.
• Giving an AI assistant a live key before testing it on paper.
• Expecting a single-source plan to run Telegram and TradingView at the same time.