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/vkdnjznd/crypto-trading-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/vkdnjznd/crypto-trading-mcp/crypto_mcp)<a href="https://agentmods.dev/mcp/vkdnjznd/crypto-trading-mcp/crypto_mcp"><img src="https://agentmods.dev/badge/mcp/vkdnjznd/crypto-trading-mcp/crypto_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/vkdnjznd/crypto-trading-mcp/crypto_mcp"><img src="https://agentmods.dev/badge/mcp/vkdnjznd/crypto-trading-mcp/crypto_mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
crypto_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 10d 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
{ "crypto_mcp": { "command": "uvx", "args": [ "crypto_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.
- 10d ago First seen · 8 lines scan A a51fa5af8600
crypto_mcp is an MCP server published in the GitHub repository vkdnjznd/crypto-trading-mcp (9 stars, last pushed 1y 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
tradingview-mcp
Real-time market data, screeners, technical analysis & backtesting for stocks, crypto and forex. Remote server at mcp.cryptosieve.com.
tickdb-market-data
Real-time & historical market data: forex, stocks, crypto, indices, metals, K-line, quotes. Remote server at mcp.tickdb.ai.
truss44-mcp-crypto-price
Provide real-time cryptocurrency price data and market analysis. Remote server at server.smithery.ai.
hive
MCP server "hive", hosted remotely at mcp.hiveintelligence.xyz, as configured in hive-intel/hive-sdk.
crypto-quant-platform
MCP server "crypto-quant-platform" as configured in FETKlOkAn2/crypto-quant-platform. Runs locally from the crypto-quant-platform Python package.
hermes-finance
MCP server "hermes-finance" as configured in Lzh-xbccz/hermes-finance. Runs bin/hermes_finance_mcp.py with python3. Needs 1 environment variable to run.