trading-signalslisted
Install: claude install-skill target1m/traderspy-mcp
TraderSpy's AI signals are automated reads of the market: a named preset fires when several
technical conditions line up on one crypto futures pair, a validator scores the alignment, and
the published signal carries an entry, a take-profit ladder, a stop and — later — what actually
happened. The signals feed at https://traderspy.app/signals publishes every one with its resolved
outcome. Your job is to fetch,
translate and contextualise them; the decision stays with the user.
## Tools
| Tool | Use it for | Key arguments |
| --- | --- | --- |
| `get_signals` | The list: newest first | `limit` 1–50 (default 20), `skip`, `importance` high / medium / low / all, `coin` |
| `get_signal_details` | One signal in full, plus the live price | `signalId` (the `id` from the list) |
| `get_signal_stats` | Aggregate hit rate over a window | `period` 4h / 8h / 24h / 7d |
Three argument behaviours that are easy to get wrong:
- **`importance` is inclusive downward.** `high` returns high only, `medium` returns high AND
medium, `low` returns everything. To show "medium and above" pass `medium`, not `low`.
- **`coin` is a prefix match** on the pair name. `BTC` matches `BTCUSDT` and also `BTCDOMUSDT`;
check the `coin` field of each row before presenting "BTC signals".
- **`limit` is what gets rendered.** In hosts that draw signal cards, every fetched row becomes a
card. If the user asks for "the last 5", pass `limit: 5` — do not fetch 20 and show 5.
## What a signal row contains
`strate