TraderSpy Trading Signals

TraderSpy Trading Signals interprets published indicator alignments for crypto futures pairs. Each signal names a preset and timeframe, records its trigger price and conditions, and carries target percentages, a stop, importance, strength, creation time, and an evolving resolution status. The workflow fetches that evidence and explains its context rather than treating the signal as an instruction.

Three tools supply recent signal lists, full details with a live price, and aggregate statistics over a selected window. List limits match the user's requested count because some hosts render a card for every fetched row. Importance filtering is inclusive downward: medium includes high and medium, while low includes everything. Coin filtering is a prefix match, so the returned pair name is checked before a row is described as belonging to a particular coin.

Target percentages are converted into prices relative to the trigger price. Buy targets rise above entry and buy stops fall below it; sell targets fall below entry and sell stops rise above it. First-target reward-to-risk is read alongside historical hit rates rather than judged in isolation. All displayed values come from returned fields, with nulls kept unavailable.

Use it for recent alerts, long or short signal ideas, a signal's entry and exit levels, current-price context, or outcomes over four hours to seven days. A performance question can be:

How have the signals resolved over the last 7 days?

Tracked trader positioning belongs to smart-money, and a current indicator read belongs to technical-analysis. A signal's indicator values describe trigger time, not the current chart. The workflow covers TraderSpy's own published signals and cannot place, close, transfer, or withdraw anything. Historical statistics describe their sample rather than future probability guarantees.

Inputs include coin, desired list size, importance threshold, signal ID, or statistics window. A list becomes a compact table with coin, side, timeframe, entry, first target, stop, preset, status, and age. Resolved rows remain visible instead of being mixed into an apparently active list. An empty coin result is reported rather than replaced with another pair.

A single-signal report gives identity, price levels with percentages, trigger conditions, live-price distance from entry and boundaries, and outcome so far. The live price carries its timestamp. Highest and lowest prices since entry provide historical context. A crossed boundary can expose a stale pending status, and the tracking window is checked before calling a signal active.

Resolution distinguishes pending, highest target reached, an early locked partial gain, stop before any target, and expiry without either boundary. Later stop touches do not downgrade a recorded target hit. Outcome checks use one-minute wicks. Statistics use hits divided by hits plus stops for signals created in the chosen window, alongside total and pending counts; small windows are flagged as limited samples.

get_signals supports limit 1-50, with API default 20; the workflow defaults to 10 when no requested count is given. get_signal_details uses signalId from the list. get_signal_stats accepts 4h, 8h, 24h or 7d. Unfiltered pagination.total counts the whole archive, not today's signals. Importance is the preset tier, distinct from matched-condition signalStrength, which is capped at strong unless entry was fresh.

For a buy, target price is entry multiplied by one plus target pct divided by 100 and stop price uses one minus stop pct divided by 100. For a sell, those signs reverse. TP1 reward-to-risk divides TP1 pct by SL pct. TP2 and TP3 are approximately 1.7x and 2.4x TP1, a graded ladder rather than independent forecasts. Trigger-time validation_score is not a ranking guarantee; very high scores may reflect late entries. validation_directional_move_pct above roughly 1.5% indicates an entry after the move was underway. aiReview can be null; a present score and decision remain reviewer opinion.

The detailed history can have a recalibrated entryPrice and a null currentPrice on a fresh signal; livePrice gives the current call-time price. Indicator values include rsi, macd_histogram, adx, obv_slope, obv_flow_pct, volume_ratio and williams_r with validation fields. Signed realized movement uses resolution.price relative to history.entryPrice. Tracking checkpoints are 1x, 4x and 24x the signal timeframe. One-minute highs and lows start after the entry minute; same-minute target/stop ambiguity records the stop first. TP2 and TP3 count after TP1, and a later stop cannot downgrade a target hit. An untouched old pending row can remain pending indefinitely; it is roughly flat historical evidence rather than an active idea.

profit_locked records a trend-exhaustion check that locks a partial gain before TP1. targetHits includes tp1_hit, tp2_hit, tp3_hit and profit_locked. Statistics pending is total minus hits minus stops and therefore also includes expired rows. winRate is rounded hits divided by hits plus stops times 100, and remains null when nothing has resolved. highCount counts high importance. Single-digit totals in short windows are noise, not a forecast.

The hosted endpoint is https://mcp.traderspy.app/mcp over Streamable HTTP. Connect it in the client and authorize with OAuth or a personal key from https://traderspy.app/mcp. A free account is sufficient. Daily tool limits are 300 calls on the free tier and 5,000 on premium. Without the server connection, this skill has no live market data.