---

👨‍💻 Developer & Company

This project is brought to you by Pelle Nyberg and his company, Corax CoLAB.

---

✨ Features & Capabilities

🎨 Visual & Technical Upgrades (Bolt & Palette)

• Matrix Digital Rain: Ambient, immersive cyberpunk background animations.
• Cyberpunk Glitch Text: Immersive text glitching effects across core UI headers.
• Interactive 3D Card Tilt: Hover over dashboard elements to see them dynamically tilt in 3D space.
• Holographic Sweeps: Primary buttons feature an animated light-sweep effect to represent active scanning.
• Typewriter AI Reasoning: AI logic is animated character-by-character for a more authentic 'terminal' feel.
• Performance & Security: Includes memoized 3D components, SSRF protection on endpoints, error-fallback for ERC20 contracts, and hmac.compare_digest for timing-safe equality in backend services.

Our terminal is a living, breathing Hedge Fund AI Orchestrator, packed with cutting-edge tools.

🤖 Autonomous Orchestrator Mode (Agentic Loop)

Evolving from a passive Multi-MCP tool, the server acts as an autonomous 24/7 trading agent framework running a continuous Observe-Analyze-Act (OODA) loop.

• Observe (gather_market_data): Queries multiple MCPs (e.g. Technical indicators, News sentiment, On-chain data).
• Analyze (analyze_with_llm): Evaluates signals using an LLM (Gemini, Claude, or OpenAI) for a structured decision (BUY, SELL, HOLD).
• Act (execute_trade): Executes trades via the local CCXT MCP.
• Agentic Backtesting: Safely test AI prompts and models against historical OHLCV data without risking real funds.
• Proof of Brain (Trading Diary): Comprehensive markdown reports detailing the "Board of Directors" reasoning for every action taken.

📱 Telegram Command Center

Receive real-time alerts and command your trading agent via Telegram.

• /status: View active AI providers and last decisions.
• /report: Receive your latest "Proof of Brain" report.
• /analyze: Trigger a manual OODA cycle.

🌌 100% Real Data Integration & Visualizer Dynamics (v3.0)

The Crypto MCP Server uses real data across all visualizers. The entire system operates without a single mockup!

• 🎯 Dark Pool Sonar: Real-time 3D sonar pings for large volume "whale" trades on central exchanges using @react-three/fiber.
• 🔥 Flash-Crash Prediction Matrix: Glowing heatmap grid of bids to asks, tracking liquidity drains.
• 🚀 Galaxy View (Gravity Well): 3D mapping of the top 50 cryptocurrencies.
• 🧠 AI Sentiment Word-Cloud Sphere: Extracts trending keywords and sentiment from real-time news to form an interactive 3D floating sphere.
• ⚡ Gas & Network Congestion Hologram: Visualizes Ethereum network congestion as a glowing, pulsating reactor core.

---

🚀 The Multi-MCP Ecosystem

This repository comes bundled with over a dozen powerful MCPs (Model Context Protocol). They provide execution, raw data, analysis, and external system integrations.

🛠️ View Included MCPs (Click to expand)

MCP Server	Description	Port
ccxt_mcp	The core exchange trading & market data integration via CCXT.	7001
onchain_mcp	ETH balances, ERC20 balances, transaction info, and live Gas Prices.	7002
ta_mcp	Compute Technical Indicators (RSI, MACD, SMA50, BB) and Monte Carlo Simulations.	7003
portfolio_mcp	Aggregated portfolio balances and performance tracking.	7004
coingecko_mcp	Deep market stats, top coins, and historical trends.	7005
llm_mcp	Local/Remote LLM operations and Copilot interactions.	7006
notifier_mcp	System notifications, alerts, and Telegram broadcasting.	7007
freqtrade_mcp	Interfaces with local Freqtrade instances via REST APIs.	7011
octobot_mcp	Interfaces with local OctoBot instances via REST APIs.	7012
hummingbot_mcp	Controls local Hummingbot Gateway APIs.	7013
superalgos_mcp	Interacts with the Superalgos platform API.	7014
news_mcp	Fetches the latest crypto news from CryptoPanic.	7017

---

🗺️ System Overview & Architecture

Explore the architecture, installation success, and security models below:

1️⃣ Architectural Overview (Click to expand)

Claude Desktop communicates via JSON-RPC with the Crypto MCP Server backend (REST + WebSocket). The server acts as a proxy, directing traffic to specific local MCP tools—such as CCXT, CoinGecko, and Portfolio—while logging orders to a local SQLite database.

2️⃣ Installation and Configuration (Click to expand)

The terminal displays successful execution steps of the automated `install.sh` script, automating directory creation, Node.js installation, and service setup.

3️⃣ Security and Best Practices (Click to expand)

Summarizes the core security principles: using testnet keys, securing API keys, restricting network access, leveraging local control, and implementing an authenticated reverse proxy.

---

✅ Quick start — automated

Place the provided install.sh into $HOME/install.sh (or $HOME/cryptomcpserver/install.sh if you prefer). Make it executable and run it:

# Save install.sh to $HOME/install.sh, then:
cd $HOME
chmod +x install.sh
./install.sh

What install.sh does (summary):

1. Creates directories and writes backend & frontend files.
2. Installs Node.js if missing and runs npm install for backend & frontend.
3. Ensures the orders table exists in $HOME/cryptomcpserver/gui/backend/orders.db.
4. Frees port 4000 if occupied, then installs & enables the systemd service crypto-mcp-gui.service.
5. Attempts a production build of the frontend.

After running, check service status and logs:

sudo systemctl status crypto-mcp-gui.service
sudo journalctl -u crypto-mcp-gui.service -f

---

🛠 Manual install

If you prefer to do everything yourself:

1. Install system deps & Python Requirements:

   sudo apt update
   sudo apt install -y curl build-essential ca-certificates git python3-pip
   pip3 install -r requirements.txt
   

2. Install Node.js (if needed):

   curl -sL https://deb.nodesource.com/setup_20.x | sudo -E bash -
   sudo apt install -y nodejs
   

3. Backend & Global Config:

   cd $HOME/cryptomcpserver
   cp .env.example .env
   # edit .env to add your passwords, keys, and allowed pairs
   
   cd gui/backend
   npm install
   

4. Frontend (dev):

   cd $HOME/cryptomcpserver/gui/frontend
   npm install
   npm run dev -- --host   # open http://PI_IP:5173 on your laptop
   

5. Systemd (backend):

   # Create /etc/systemd/system/crypto-mcp-gui.service
   sudo systemctl daemon-reload
   sudo systemctl enable --now crypto-mcp-gui.service
   

---

⚙️ Configuration

The system uses a centralized .env file located at the root of the project to manage both Python MCP servers and the Node.js backend.

Copy and edit $HOME/cryptomcpserver/.env.example → .env:

# Essential configuration
PORT=4000
DASHBOARD_PASSWORD=your_secure_password # Required for trading and AI reasoning
ALLOWED_PAIRS=BTC/USDT,SOL/USDT # Fail-closed security: only these pairs are allowed
MAX_TRADE_USD=100.0 # Maximum allowed trade amount per transaction

# API Keys
BINANCE_API_KEY=your_key
BINANCE_API_SECRET=your_secret

# --- Autonomous Orchestrator Settings ---
ACTIVE_LLM_PROVIDER="gemini"
GEMINI_API_KEY="your_google_gemini_key_here"
TELEGRAM_BOT_TOKEN="your_token_here"
TELEGRAM_CHAT_ID="your_chat_id_here"

---

🔗 Claude Desktop integration

Add MCP servers in Claude Desktop (step-by-step)

1. Open Claude Desktop app.
2. Open App Settings / Preferences.
3. Find Local MCP Servers.
4. Click + (Add) — fill fields one by one:
   • Name: ccxt
   • Description: CCXT MCP – exchange trading & market data
   • Transport: http
   • Endpoint: http://127.0.0.1:7001/mcp (if Claude runs on Pi) or http://<pi-ip>:7001/mcp (if Claude runs on laptop)
5. Save. Repeat for other MCPs (coingecko, portfolio, onchain, ta, news, etc.) with their respective ports.

---

🖥 Dashboard user manual

• 📊 Portfolio: View aggregated balances & USD value.
• 📈 Ticker: Live market data (via ccxt MCP).
• 🛒 Order / Trade:
  • Preview (dry_run): Calculates estimated cost and logs a preview.
  • Confirm → Place order: Sends create_order to CCXT MCP.
• 📜 Orders log: Real-time updates via socket.io, paginated with indices.
• 🤖 AI Copilot: Voice-activated command center powered by local LLMs.

⚠️ Safety: Always test with testnet keys. The UI requires confirmation to execute live orders.

---

🔒 Security & best practices

• Testnet First: Use testnet keys while testing.
• Environment Variables: Keep API keys out of repo.
• Network Isolation: Restrict access to MCP endpoints to LAN only.
• Authentication: Endpoints are fully secured with DASHBOARD_PASSWORD verification.