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/manavaga/web3-signals-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/manavaga/web3-signals-mcp/web3-signals)<a href="https://agentmods.dev/mcp/manavaga/web3-signals-mcp/web3-signals"><img src="https://agentmods.dev/badge/mcp/manavaga/web3-signals-mcp/web3-signals/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/manavaga/web3-signals-mcp/web3-signals"><img src="https://agentmods.dev/badge/mcp/manavaga/web3-signals-mcp/web3-signals.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
web3-signals 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
{
"web3-signals": {
"url": "https://web3-signals-api-production.up.railway.app/mcp/sse",
"type": "sse"
}
}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 dde3a20654ad
web3-signals is an MCP server published in the GitHub repository manavaga/web3-signals-mcp (3 stars, last pushed 25d 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
quantoracle
73 deterministic quant tools for AI agents. LLMs drift on Black-Scholes; these are exact math. Runs locally from the quantoracle-mcp npm package.
gsc
MCP server "gsc" as configured in QuantOracledev/quantoracle. Launched with D:\Quantcalc\venv\Scripts\python.exe D:\Quantcalc\mcp-gsc\server.py.
crypto-quant-signal-mcp
Quant trading signals, funding rate arb scanning, and market regime detection for crypto perps. Runs locally from the crypto-quant-signal-mcp npm package.
crypto-swap
Native cross-chain swaps: Bitcoin, Ethereum, Solana, Polkadot, Tron, Arbitrum. Quote, swap, track. Remote server at chainflip-broker.io.
coinopai-mcp
Kronos crypto signals + trade decisions + 819 automation prompts. x402 micropayments, USDC/Base. Runs locally from the coinopai-mcp npm package. Needs 1 environment variable to run.
hl-portfolio
Hyperliquid account analysis: positions, PnL, fills, orders, funding. x402 pay-per-call. Remote server at hl-portfolio.api.klymax402.com.