crypto-signals-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WALLET_PRIVATE_KEY | Yes | A dedicated low-balance Base wallet private key funded with USDC for agent spending. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_crypto_signalsA | Retrieve current BTC, ETH, SOL, XRP, and ADA market-intelligence signals, ranked context, regime, and freshness. Costs $0.05 USDC. |
| get_crypto_riskA | Retrieve the current market risk state, signal streaks, and cooldown context before deeper analysis. Costs $0.02 USDC. |
| get_crypto_signal_historyB | Retrieve recent Kronos market context history for supported crypto symbols. Costs $0.05 USDC. |
| get_crypto_preflightA | Run the market-state, cooldown, freshness, and model-context preflight step before creating a decision journal. Costs $0.05 USDC. |
| get_crypto_decisionC | Create an auditable market-intelligence journal containing calibrated context and a decision_id for later outcome review. Costs $0.15 USDC. |
| audit_crypto_decisionA | Audit a prior decision_id against subsequent market prices over a 1h, 4h, or 24h evaluation window. Costs $0.07 USDC. |
| get_crypto_forecastA | Retrieve an empirically calibrated 80% price interval, current price, point return, and upside probability. Costs $0.05 USDC. |
| get_single_crypto_signalB | Retrieve the current signal context for one crypto symbol using the compatibility lookup route. Costs $0.05 USDC. |
| get_crypto_whale_alertsA | Retrieve whale-scale transfers, exchange flows, bridge flows, and stablecoin events for Ethereum, Base, or Arbitrum. Costs $0.02 USDC. |
| submit_crypto_feedbackA | Submit paid feedback, a symbol request, bug report, or integration suggestion to ForgeMesh Crypto Signals. Costs $0.005 USDC. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.