Crypto Intelligence MCP server
{
"mcpServers": {
"carbon-cashmere-crypto-intelligence": {
"type": "http",
"url": "https://api.carbon-cashmere.de/mcp/"
}
}
}{
"mcpServers": {
"carbon-cashmere-crypto-intelligence": {
"type": "http",
"url": "https://api.carbon-cashmere.de/mcp/"
}
}
}{
"mcpServers": {
"carbon-cashmere-crypto-intelligence": {
"type": "http",
"url": "https://api.carbon-cashmere.de/mcp/"
}
}
}{
"servers": {
"carbon-cashmere-crypto-intelligence": {
"type": "http",
"url": "https://api.carbon-cashmere.de/mcp/"
}
}
}{
"mcpServers": {
"carbon-cashmere-crypto-intelligence": {
"type": "http",
"url": "https://api.carbon-cashmere.de/mcp/"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 4.0.0
Pay-per-call crypto intelligence: 50 tools, own BTC/Kaspa/Bittensor nodes, x402 USDC, no API key.
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.
This server has not seen a commit in unknown. It may still work, but nobody is currently fixing it — check the alternatives before you build on it.