crypto-signals-mcp
# Crypto Signals by ForgeMesh
[](https://m8ven.ai/mcp/forgemeshlabs-crypto-signals-mcp-1qui57)
Dedicated MCP wrapper for [ForgeMesh Crypto Signals](https://crypto.forgemesh.io), an x402 crypto market-intelligence service.
This is separate from `coinopai-mcp`. Every tool targets `crypto.forgemesh.io` and pays the ForgeMesh Crypto Signals service wallet through x402 on Base.
## Install
```bash
npx -y @forgemeshlabs/crypto-signals-mcp
```
Configure `WALLET_PRIVATE_KEY` with a dedicated low-balance Base wallet funded only with the USDC you intend the agent to spend. Never use a primary wallet.
Example MCP configuration:
```json
{
"mcpServers": {
"crypto-signals-mcp": {
"command": "npx",
"args": ["-y", "@forgemeshlabs/crypto-signals-mcp"],
"env": {
"WALLET_PRIVATE_KEY": "${WALLET_PRIVATE_KEY}"
}
}
}
}
```
## Tools
- `get_crypto_signals` — $0.05
- `get_crypto_risk` — $0.02
- `get_crypto_signal_history` — $0.05
- `get_crypto_preflight` — $0.05
- `get_crypto_decision` — $0.15
- `audit_crypto_decision` — $0.07
- `get_crypto_forecast` — $0.05
- `get_single_crypto_signal` — $0.05
- `get_crypto_whale_alerts` — $0.02
- `submit_crypto_feedback` — $0.005
All outputs are market intelligence for research and decision support, not financial advice or market activity instructions.
TDQS
Scored across 10 tools
Most tools target distinct capabilities: signals, risk, history, preflight, decision creation, audit, forecast, single signal, whale alerts, and feedback. The overlap between get_crypto_signals and get_single_crypto_signal is clarified by descriptions (multi-symbol vs. single-symbol compatibility route), and get_crypto_forecast adds price-interval data. Overall, boundaries are clear enough with only minor potential confusion.
All tools follow a consistent verb_noun pattern: get_crypto_* for retrievals, audit_crypto_decision for auditing, and submit_crypto_feedback for submissions. No mixing of naming conventions like camelCase or inconsistent verb styles. The pattern is predictable across the entire set.
With 10 tools, the count is well within the ideal 3-15 range and each tool earns its place for the crypto-signals domain. The set covers data retrieval, risk assessment, decision journaling, auditing, forecasting, and user feedback without feeling bloated or sparse.
The tool surface covers the core lifecycle: retrieving signals, risk state, history, preflight checks, creating decision journals, auditing them against outcomes, forecasts, whale alerts, and feedback. Minor gaps exist, such as no direct listing/update/delete for decision journals, but these are not critical dead ends for the primary use case of obtaining and acting on crypto intelligence.