forecast_archive — crypto intelligence MCP Tool
forecast_archive
(forecast archive) is one of 50 tools on the
crypto intelligence
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call forecast_archive from your client
- Claude Code crypto intelligence forecast_archive run in your project directory
- Claude Desktop crypto intelligence forecast_archive ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor crypto intelligence forecast_archive ~/.cursor/mcp.json
- VS Code crypto intelligence forecast_archive .vscode/mcp.json
- Zed crypto intelligence forecast_archive ~/.config/zed/settings.json
- Windsurf crypto intelligence forecast_archive ~/.codeium/windsurf/mcp_config.json
- Cline crypto intelligence forecast_archive ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI crypto intelligence forecast_archive ~/.gemini/settings.json
- Grok crypto intelligence forecast_archive .mcp.json (in your project root)
- ChatGPT crypto intelligence forecast_archive Settings → Connectors → Advanced → Developer mode
- Claude.ai crypto intelligence forecast_archive Settings → Connectors → Add custom connector
- LangChain crypto intelligence forecast_archive pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http crypto-intelligence https://api.carbon-cashmere.de/mcp/Other tools on this server
- kaspa_toccata_status
- kaspa_fee_regime
- kaspa_throughput_health
- kaspa_timeseries
- bittensor_subnet_stake_flows
- bittensor_subnet_coordination
- btc_miner_attribution
- btc_ordinals_flow
- btc_coin_days_destroyed
- btc_diversity
- btc_mempool_pressure
- btc_fee_curve
- btc_blocks
- btc_blocks_range
- btc_coinbase_messages
- kaspa_dag_state
- kaspa_chain_density
- kaspa_supply_trend
- kaspa_diversity
- kaspa_mempool_pulse
- kaspa_blocks
- kaspa_recent_blocks
- subtensor_registration_pulse
- subtensor_transfer_flow
- subtensor_weights_activity
- subtensor_block_metrics
- subtensor_evm_activity
- subtensor_events
- bittensor_subnet
- bittensor_subnet_metagraph
- bittensor_subnet_validators
- bittensor_subnet_emission_trend
- bittensor_subnets_all
- bittensor_alpha_prices
- bittensor_alpha_price_history
- bittensor_network_fundamentals
- bittensor_registration_cost_history
- bittensor_top_validators_cross_subnet
- safety_check_quick
- safety_check_standard
- safety_check_deep
- safety_check_token
- bittensor_mining_viability
- bittensor_yield_history
- bittensor_wallet_reputation
- bittensor_weights_integrity
- bittensor_alpha_risk
- bittensor_owner_reputation
- forecast_scorecard
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.