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.
git clone --depth 1 https://github.com/purple-flea/agent-tradingWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/purple-flea/agent-trading/trading-mcp)<a href="https://agentmods.dev/mcp/purple-flea/agent-trading/trading-mcp"><img src="https://agentmods.dev/badge/mcp/purple-flea/agent-trading/trading-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/purple-flea/agent-trading/trading-mcp"><img src="https://agentmods.dev/badge/mcp/purple-flea/agent-trading/trading-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
trading-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 1mo ago.
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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 1mo ago First seen · 9 lines scan A 134cb87d4a58
trading-mcp is an MCP server published in the GitHub repository purple-flea/agent-trading (0 stars, last pushed 7mo ago), with no licence file. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. 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 mcp servers, from other repositories
casino-mcp
MCP server for AI agent casino — provably fair gambling with 0.5% house edge. Coin flip, dice, roulette, crash, custom odds. Kelly Criterion bankroll protection. By Purple Flea. Runs locally from the @purpleflea/casino-mcp npm package.
crypto-quant-signal-mcp
Quant trading signals, funding rate arb scanning, and market regime detection for crypto perps. Runs locally from the crypto-quant-signal-mcp npm package.
crypto-swap
Native cross-chain swaps: Bitcoin, Ethereum, Solana, Polkadot, Tron, Arbitrum. Quote, swap, track. Remote server at chainflip-broker.io.
mcp-server
Agent payment infrastructure MCP server. Give AI agents autonomous payment capability — stablecoin transfers, currency swaps, agent wallets, and fiat operations on Hedera. Works with Claude, LangChain, CrewAI, AutoGPT. Runs locally from the @bananacrystal/mcp-server npm package.
headless-tracker
Not financial advice. Crypto portfolio aggregation across exchanges, wallets, prediction markets. Runs locally from the headless-tracker npm package.
coingecko-mcp-server
Crypto market data via CoinGecko — prices, markets, history, trending, and deep coin metadata. Runs locally from the @cyanheads/coingecko-mcp-server npm package. Needs 2 environment variables to run.