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.
npx agentmods add mcp/node2flow-th/binance-th-mcp-community/binance-th-mcpgit clone --depth 1 https://github.com/node2flow-th/binance-th-mcp-communityWrote 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/node2flow-th/binance-th-mcp-community/binance-th-mcp)<a href="https://agentmods.dev/mcp/node2flow-th/binance-th-mcp-community/binance-th-mcp"><img src="https://agentmods.dev/badge/mcp/node2flow-th/binance-th-mcp-community/binance-th-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
binance-th-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 5d 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
{ "binance-th-mcp": { "command": "npx", "args": [ "-y", "@node2flow/binance-th-mcp" ] } }
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.
- 5d ago First seen · 9 lines scan A c45cd2e1500d
binance-th-mcp is an MCP server published in the GitHub repository node2flow-th/binance-th-mcp-community (0 stars, last pushed 6mo 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-31.
Other mcp servers, from other repositories
binance-mcp
MCP server for Binance Global API — 23 tools for market data, trading, orders, and account management on the world's largest crypto exchange. Runs locally from the @node2flow/binance-mcp npm package.
bitget-agent-mcp
Official Bitget MCP Server for the Unified Trading Account (UTA v3) API. Runs locally from the @bitget-ai/bitget-agent-mcp npm package. Needs 3 environment variables to run.
tradestaq-mcp
AI-powered crypto trading tools. Strategies, backtests, bots, and portfolio management. Runs locally from the @the-staq/tradestaq-mcp npm package.
vybe-solana-api
Solana MCP for wallets, trades, markets, PnL, transfers, onchain data, signable swaps and API tools. Remote server at docs.vybenetwork.com.
horus-flow
Real-time orderflow intelligence for crypto & equities — whale detection, spoofing alerts, liquidation heatmaps, smart money divergence, block trades, and AI composite scoring. Runs locally from the horus-flow-mcp Python package. Needs 1 environment variable to run.
horus-flow-mcp
Real-time orderflow intelligence for crypto & equities — whale detection, spoofing alerts, liquidation heatmaps, smart money divergence, block trades, and AI composite scoring. Runs locally from the horus-flow-mcp Python package. Needs 1 environment variable to run.