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/cstamigo-droid/signal-scannerWrote 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/cstamigo-droid/signal-scanner/signal-scanner)<a href="https://agentmods.dev/mcp/cstamigo-droid/signal-scanner/signal-scanner"><img src="https://agentmods.dev/badge/mcp/cstamigo-droid/signal-scanner/signal-scanner/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/cstamigo-droid/signal-scanner/signal-scanner"><img src="https://agentmods.dev/badge/mcp/cstamigo-droid/signal-scanner/signal-scanner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
signal-scanner 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.
What it actually says
{ "signal-scanner": { "command": "uvx", "args": [ "signal-scanner" ] } }
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 · 8 lines scan A a8492f0c53b5
signal-scanner is an MCP server published in the GitHub repository cstamigo-droid/signal-scanner (0 stars, last pushed 27d 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
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.
tradeos-mcp
TradeOS MCP: ticker search, My Agent, chart TA, macro news. npm stdio or HTTP. Runs locally from the @tradeos/tradeos-mcp npm package. Needs 1 environment variable to run.
mcp-trading
Keyless prediction-market data across 12 venues plus paper-trading of crypto spot, futures, and PM. Runs locally from the @coinrithm/mcp-trading npm package. Needs 2 environment variables to run.
apollo-proxy
26 AI tools: DeFi, OSINT, crypto, intel feeds, search, proxy. x402 micropayments. Runs locally from the @apollo_ai/mcp-proxy npm package.
trading-cli
MCP server "trading-cli" as configured in Alorse/trading-cli. Launched with trading-cli mcp.