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/lazymac2x/crypto-signal-apiWrote 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/lazymac2x/crypto-signal-api/crypto-signal)<a href="https://agentmods.dev/mcp/lazymac2x/crypto-signal-api/crypto-signal"><img src="https://agentmods.dev/badge/mcp/lazymac2x/crypto-signal-api/crypto-signal/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/lazymac2x/crypto-signal-api/crypto-signal"><img src="https://agentmods.dev/badge/mcp/lazymac2x/crypto-signal-api/crypto-signal.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
crypto-signal 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 · 6 lines scan A 11672f7c7b47
crypto-signal is an MCP server published in the GitHub repository lazymac2x/crypto-signal-api (0 stars, last pushed 6mo 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
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.
openchainbench
Live, neutral benchmarks for public RPC latency, oracles, bridges, perp DEX, and prediction markets. Remote server at openchainbench.com.
decker
Deterministic market-state engine for trading agents — state, gate, coordinates, with receipts. Remote server at api.decker-ai.com.
urantia-papers
The Urantia Papers in English and Spanish, with cross-references to the Bible and 21 texts. No key. Remote server at api.urantia.dev.
trading-signals
Live AI crypto trading signals for agents. No API key needed to try — 3 signals + hit rate. Remote server at signals.x70.ai.
newsline
News from 17 outlets with left/center/right bias tags and one-sided blindspot detection. Remote server at news.heyitsmejosh.com.