Home / MCP registry index / de.carbon-cashmere.api/crypto-intelligence
de.carbon-cashmere.api/crypto-intelligence
de.carbon-cashmere.api/crypto-intelligence in the official MCP registry.
Endpoint https://api.carbon-cashmere.de/mcp/. Source: github.com/Nedeljko87/Carbon-Cashmere.
The registry describes it as: Pay-per-call crypto intelligence: 50 tools, own BTC/Kaspa/Bittensor nodes, x402 USDC, no API key.
We read its 40 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
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_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 bittensor_yield_history forecast_archive forecast_scorecard
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/de-carbon-cashmere-api-crypto-intelligence)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.
Related
| The Stall ai.intuitek.the-stall/the-stall | 200 tools, nothing matched 2026-10-22 |
| SAP MCP Server ai.oobeprotocol.sap.mcp/sap-mcp | 200 tools, nothing matched 2026-10-22 |
| Citiview Agent Market com.citiviewgroup.mcp/agent-market | 200 tools, nothing matched 2026-10-26 |
| ScorpTech x402 API com.it.scorptech/x402 | 200 tools, nothing matched 2026-10-26 |
| Apex Edge — x402-paid machine services dev.pages.nonsynthetic/apex-edge | 200 tools, nothing matched 2026-10-23 |
| io.github.praneeth12098/x402-factory io.github.praneeth12098/x402-factory | 200 tools, nothing matched 2026-10-26 |