crypto-signals-mcp
This server provides paid x402 crypto market-intelligence tools on Base, with built-in USDC spending caps and refusal-based safety controls.
Retrieve ranked crypto signals, market risk state, signal history, and single-symbol signal context.
Run preflight checks and create auditable decision journals with decision IDs for later review.
Audit prior decisions over 1h, 4h, or 24h windows, and retrieve calibrated price forecasts.
Monitor whale transfers, exchange/bridge flows, and stablecoin events on Ethereum, Base, or Arbitrum.
Submit paid feedback, symbol requests, bug reports, or integration suggestions.
Enforce Base mainnet, USDC-only, approved-payee, $0.15 per-call, and $10 per-session limits; caps can only be lowered.
Return structured errors with HTTP status and charged flag; refusals such as unknown symbols, stale data, or open audit windows are not charged.
Provides crypto market-intelligence coverage for XRP as a supported symbol, including current signals, risk and preflight context, calibrated price forecasts, decision journals, and outcome audits.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@crypto-signals-mcp What are the latest crypto signals for Bitcoin?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Crypto Signals by ForgeMesh
Dedicated MCP wrapper for ForgeMesh Crypto Signals, 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
npx -y @forgemeshlabs/crypto-signals-mcpConfigure 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:
{
"mcpServers": {
"crypto-signals-mcp": {
"command": "npx",
"args": ["-y", "@forgemeshlabs/crypto-signals-mcp"],
"env": {
"WALLET_PRIVATE_KEY": "${WALLET_PRIVATE_KEY}"
}
}
}
}Related MCP server: API for Chads
Requirements
Node.js 20 or newer and a dedicated, low-balance Base wallet (
WALLET_PRIVATE_KEY).Spending caps: the server only talks to
https://crypto.forgemesh.ioand refuses to sign for any other payee, any network except Base mainnet, any asset except USDC, or any amount above the built-in $0.15 per-call and $10 per-session caps. The environment variablesX402_MAX_PRICE_USDandX402_SESSION_BUDGET_USDcan only lower those caps, never raise them.
Tools
get_crypto_signals— $0.05get_crypto_risk— $0.02get_crypto_signal_history— $0.05get_crypto_preflight— $0.05get_crypto_decision— $0.15audit_crypto_decision— $0.07get_crypto_forecast— $0.05get_single_crypto_signal— $0.05get_crypto_whale_alerts— $0.02submit_crypto_feedback— $0.005
Notes on live behavior: signal, preflight and decision tools cover every tracked symbol (crypto pairs plus US stocks and ETFs); forecasts cover BTC, ETH, SOL, XRP and ADA only. confidence in a decision journal is the measured directional hit rate for that symbol, or null when there are too few evaluated outcomes. audit_crypto_decision returns HTTP 425 with available_at while the window is still open, and decisions stay auditable for 7 days. History hours is an integer from 1 to 168. Stale data is refused, and refusals (unknown symbol 404, stale 503, window open 425) are not charged: errors from this server carry the HTTP status, charged flag and the service's own upstream body.
All outputs are market intelligence for research and decision support, not financial advice or market activity instructions.
Available Tools
10 toolsaudit_crypto_decisionA
Audit a prior decision_id against subsequent market prices over a 1h, 4h, or 24h evaluation window. Costs $0.07 USDC.
Inputs: decision_id (required), window.
get_crypto_decisionC
Create an auditable market-intelligence journal containing calibrated context and a decision_id for later outcome review. Costs $0.15 USDC.
Inputs: symbol (required).
get_crypto_forecastA
Retrieve an empirically calibrated 80% price interval, current price, point return, and upside probability. Costs $0.05 USDC.
Inputs: symbol.
get_crypto_preflightA
Run the market-state, cooldown, freshness, and model-context preflight step before creating a decision journal. Costs $0.05 USDC.
Inputs: symbol (required).
get_crypto_riskA
Retrieve the current market risk state, signal streaks, and cooldown context before deeper analysis. Costs $0.02 USDC.
Inputs: no named parameters.
get_crypto_signal_historyB
Retrieve recent Kronos market context history for supported crypto symbols. Costs $0.05 USDC.
Inputs: hours.
get_crypto_signalsA
Retrieve current BTC, ETH, SOL, XRP, and ADA market-intelligence signals, ranked context, regime, and freshness. Costs $0.05 USDC.
Inputs: no named parameters.
get_crypto_whale_alertsA
Retrieve whale-scale transfers, exchange flows, bridge flows, and stablecoin events for Ethereum, Base, or Arbitrum. Costs $0.02 USDC.
Inputs: chain, hours.
get_single_crypto_signalB
Retrieve the current signal context for one crypto symbol using the compatibility lookup route. Costs $0.05 USDC.
Inputs: symbol (required).
submit_crypto_feedbackA
Submit paid feedback, a symbol request, bug report, or integration suggestion to ForgeMesh Crypto Signals. Costs $0.005 USDC.
Inputs: message (required), type, symbol, contact, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Unlock the power of real-time cryptocurrency data with our Crypto Price Insights MCP server.
Crypto market intelligence, token rug-checks, and wallet verification in one MCP server.
Programmatic web-scraping MCP server powered by x402 micro-transactions on Base.
Remote MCP server exposing 330 production AI-agent services for web/data processing, validation, AI utilities, blockchain/crypto utilities, and x402 pay-per-use access.
Related MCP Servers
- AlicenseAqualityDmaintenanceAn MCP server that delivers cryptocurrency sentiment analysis to AI agents.547MIT
- AlicenseNot gradedqualityDmaintenanceMCP server providing real-time crypto prices (Chainlink + Binance), Polymarket prediction market data, deep web research, and JS-rendered web scraping. All services available via x402 Solana micropayments.MIT
- AlicenseAqualityBmaintenanceKronos crypto signals + trade decisions + 819 automation prompts. x402 micropayments, USDC/Base.11718 npm1MIT
- AlicenseNot gradedqualityCmaintenanceMCP server providing 50+ crypto, market intelligence, and AI inference endpoints with x402 pay-per-request micropayments on Base.2Apache 2.0