kaspa_recent_blocks — crypto intelligence MCP Tool
kaspa_recent_blocks
(kaspa recent blocks) 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 kaspa_recent_blocks from your client
- Claude Code crypto intelligence kaspa_recent_blocks run in your project directory
- Claude Desktop crypto intelligence kaspa_recent_blocks ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor crypto intelligence kaspa_recent_blocks ~/.cursor/mcp.json
- VS Code crypto intelligence kaspa_recent_blocks .vscode/mcp.json
- Zed crypto intelligence kaspa_recent_blocks ~/.config/zed/settings.json
- Windsurf crypto intelligence kaspa_recent_blocks ~/.codeium/windsurf/mcp_config.json
- Cline crypto intelligence kaspa_recent_blocks ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI crypto intelligence kaspa_recent_blocks ~/.gemini/settings.json
- Grok crypto intelligence kaspa_recent_blocks .mcp.json (in your project root)
- ChatGPT crypto intelligence kaspa_recent_blocks Settings → Connectors → Advanced → Developer mode
- Claude.ai crypto intelligence kaspa_recent_blocks Settings → Connectors → Add custom connector
- LangChain crypto intelligence kaspa_recent_blocks 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
- 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_archive
- 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.