Home / MCP registry index / app.traderspy/traderspy

TraderSpy

app.traderspy/traderspy in the official MCP registry. Endpoint https://mcp.traderspy.app/mcp. Source: github.com/target1m/traderspy-mcp.

The registry describes it as: AI crypto signals, whale positions, 19 technical indicators, derivatives, screener and backtests

Tools it advertises

get_signals get_signal_details get_signal_stats get_top_traders get_elite_leaderboard get_trader_profile get_trader_position_history get_positions get_market_stats get_exchanges get_price get_candles get_tracked_symbols get_technical_indicators get_derivatives screen_symbols backtest_condition

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/app-traderspy-traderspy/badge.svg)](https://lazaretto.dev/mcp-registry/app-traderspy-traderspy)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers