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/TradeOS-AI/tradeos-mcpWrote 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/tradeos-ai/tradeos-mcp/tradeos-mcp-test)<a href="https://agentmods.dev/mcp/tradeos-ai/tradeos-mcp/tradeos-mcp-test"><img src="https://agentmods.dev/badge/mcp/tradeos-ai/tradeos-mcp/tradeos-mcp-test/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/tradeos-ai/tradeos-mcp/tradeos-mcp-test"><img src="https://agentmods.dev/badge/mcp/tradeos-ai/tradeos-mcp/tradeos-mcp-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
tradeos-mcp-test 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 12d 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.
What it actually says
{
"tradeos-mcp-test": {
"command": "npx",
"args": [
"-y",
"@tradeos/tradeos-mcp-test",
"-y"
],
"env": {
"TRADEOS_ACCESS_TOKEN": ""
}
}
}What else server.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 12d ago First seen · 13 lines scan A ae4f99deb7bb
tradeos-mcp-test is an MCP server published in the GitHub repository TradeOS-AI/tradeos-mcp (16 stars, last pushed 3mo ago), licensed MIT. 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-30.
Other mcp servers, from other repositories
tradingview-mcp
MCP server "tradingview-mcp" as configured in moeuu/tradingview-mcp. Runs locally from the @moeuu/tradingview-mcp npm package.
cerebrus-pulse-mcp
MCP server for Cerebrus Pulse — real-time crypto intelligence API for Hyperliquid perpetuals. Runs locally from the cerebrus-pulse-mcp Python package.
bit-monk-signal-mcp
MCP server "bit-monk-signal-mcp" as configured in airblock2026/bit-monk-signal-mcp. Runs locally from the bit-monk-signal-mcp npm package.
eeye
MCP server "eeye", hosted remotely at localhost, as configured in vi88i/eeye.
signal-scanner
Rule-based stock/crypto screener with alerts — console, Telegram, MCP. Runs locally from the signal-scanner Python package.
tradingview-mcp
MCP server "tradingview-mcp", hosted remotely at mcp.cryptosieve.com, as configured in ankitjha67/TradingView-MCP.