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/truss44/mcp-crypto-priceWrote 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/truss44/mcp-crypto-price/truss44-mcp-crypto-price)<a href="https://agentmods.dev/mcp/truss44/mcp-crypto-price/truss44-mcp-crypto-price"><img src="https://agentmods.dev/badge/mcp/truss44/mcp-crypto-price/truss44-mcp-crypto-price/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/truss44/mcp-crypto-price/truss44-mcp-crypto-price"><img src="https://agentmods.dev/badge/mcp/truss44/mcp-crypto-price/truss44-mcp-crypto-price.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
truss44-mcp-crypto-price 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
{ "truss44-mcp-crypto-price": { "url": "https://server.smithery.ai/@truss44/mcp-crypto-price/mcp", "type": "streamable-http" } }
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 · 6 lines scan A fa6a6b4e2272
truss44-mcp-crypto-price is an MCP server published in the GitHub repository truss44/mcp-crypto-price (39 stars, last pushed 5d 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
crypto-intel-mcp
Crypto market intelligence (price, momentum, trending) over MCP. Runs locally from the crypto-intel-mcp Python package.
hive
MCP server "hive", hosted remotely at mcp.hiveintelligence.xyz, as configured in hive-intel/hive-sdk.
robinhood-mcp
Robinhood Crypto Trading API for AI agents: quotes, holdings, orders read-only; opt-in trading. Runs locally from the robinhood-mcp npm package. Needs 4 environment variables to run.
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.
kainext-binance-mcp
MCP server for Binance spot: read market data, analyze, and propose real-money trades behind a human-gated confirmer. The model never holds a trade key. Runs locally from the kainext-binance-mcp Python package. Needs 3 environment variables to run.
binance-mcp
MCP server for Binance exchange - spot trading, staking, wallet, NFT, pay, mining, and more. Runs locally from the @nirholas/binance-mcp-server npm package. Needs 2 environment variables to run.