Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
/plugin marketplace add target1m/traderspy-mcpnpx agentmods add plugins/target1m/traderspy-mcp/traderspy-mcpgit clone --depth 1 https://github.com/target1m/traderspy-mcpGrade A, and why
traderspy-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"name": "traderspy-mcp",
"description": "TraderSpy — Read-only smart money tracking, AI trading signals, and elite trader leaderboard for crypto futures. Track whale positions across Binance, Hyperliquid, Bybit, and OKX. No order or withdrawal tools.",
"version": "1.2.0",
"author": {
"name": "TraderSpy",
"email": "[email protected]"
},
"homepage": "https://traderspy.app",
"repository": "https://github.com/target1m/traderspy-mcp",
"license": "MIT",
"keywords": ["crypto", "trading", "smart-money", "signals", "binance", "hyperliquid", "bybit", "okx"]
}
What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- yesterday First seen · 14 lines scan A e14a44c6383d
traderspy-mcp is a plugin published in the GitHub repository target1m/traderspy-mcp (0 stars, last pushed 6d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other plugins, from other repositories
0xarchive
Agent-ready 0xArchive market data skill for coding-agent clients across Hyperliquid and Lighter.xyz, including Hyperliquid HIP-3 builder perps, HIP-4 outcome markets, and Hyperliquid Spot. REST and WebSocket support are route-specific; HIP-4 trades, L4 events, and settlements are live while HIP-4 L2 and OI use REST or.
maia-skill
Tododeia — Multi-agent investment analysis system for market research, portfolio recommendations, and interactive reporting across crypto, stocks, forex, and commodities.
cdc-health-mcp-server
Search and query CDC public health data — mortality, vaccinations, surveillance, behavioral risk (Socrata SODA API) via MCP. STDIO or Streamable HTTP.
shotcut-mcp
Full transactional editor for Shotcut projects through a local MCP server.
pmtechdev
Local-first MCP plugins maintained by PMTechDev.
axcient
Every x360Recover endpoint, plus the fleet-wide backup-health answers the API alone can't give — offline, joined, and agent-ready.