convez.ai
MCP Server
AmaLS367

TradeMcp

AmaLS367/TradeMcp

Ver no GitHub
BomPluginScore · de 0 a 100

AI-powered crypto trading & earn assistant via MCP — Binance, Bybit, real-time data, technical analysis

Instalação

$npx convez-ai AmaLS367/TradeMcp

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
1
Acompanhando
0
Saúde
100%
Último commit
há 2 dias
Versão
—
Issues abertas
25
Contribuidores
3

README

A tradução para o português deste README ainda está na fila.

Secure remote MCP for human-in-the-loop crypto workflows.


✨ What Is Trade MCP?

Trade MCP transforms AI coding assistants (like Cursor, Claude, and ChatGPT) into secure, production-ready trading agents.

Instead of configuring dozens of local, brittle scripts or exposing raw exchange API keys to LLMs, Trade MCP provides a single, OAuth-secured remote hub. It bridges the gap between powerful language models and secure financial execution by encrypting stored credentials, enforcing granular security profiles, and requiring human-in-the-loop approval for staged trade execution.


💎 Why It Feels Useful

Setting up algorithmic execution usually requires managing complex local configurations, system services, and raw secrets. Trade MCP changes this:

  • 🔐 Secured Credentials: Exchange connections (Binance, Bybit) and provider API keys are encrypted with AES-256-GCM using the server-side ENCRYPTION_KEY. Decryption keys never touch the database.
  • 🛡️ Granular Safety Policies: MCP tools are grouped into profiles (safe_research, trading_review, full_access). Clients cannot run tools above their approved profile.
  • 🤝 Human-Approved Execution: High-risk write actions (submitting orders, moving funds) generate structured proposals that require explicit user confirmation through the dashboard before executing.
  • 📊 Unified Multi-Exchange Earn: Easily search, compare, and track active yield positions across Binance (Flexible/Locked) and Bybit (Flexible/Fixed-term Featured savings).
  • 🌐 Remote-First Architecture: No local dependencies. Works perfectly across cloud servers (like Docker on Contabo), local environments, and SaaS AI platforms.

🌟 Features

GroupKey ToolsDescription
💼 Portfolio & Yieldget_balances, compare_earn_opportunities, get_bybit_earn_position, get_binance_earn_positionsFetch account balances, track active yield products, and aggregate real-time APRs.
📈 Market & Indicatorsget_market_price, get_crypto_indicators, get_taapi_indicators, get_newsCalculate local indicators (EMA, RSI, MACD), query TAAPI.io, and gather CryptoPanic news.
⚡ Execution Controlpropose_trade, review_proposal, cancel_proposalGenerate structured trade proposals that require human-in-the-loop approvals.
🛡️ Access ControlsOAuth (PKCE), Dashboard API Keys, Policy ProfilesRestrict tool usage by client connection and security scope.

🧠 Why Remote MCP?

Local MCP servers are difficult to configure across multiple editors, cannot easily support OAuth, and are highly vulnerable to prompt injection attacks executing destructive actions.

Trade MCP addresses these issues directly:

  • Zero Local Config: Connect Claude or Cursor to a single HTTPS URL.
  • OAuth-Protected Workspace: Keep your API keys and portfolio data securely isolated from standard workspace contexts.
  • Blast Radius Mitigation: Trade proposals are staged as read-only database records. An rogue agent cannot bypass the human approval screen.

🧭 How It Works

sequenceDiagram
    participant Client as AI Client (Cursor/Claude)
    participant Server as Trade MCP Server (Node.js/Express)
    participant Auth as Firebase OAuth
    participant DB as Encrypted Firestore
    participant Exchange as Exchange APIs (CCXT)

    Client->>Server: Handshake & Discovery
    Server-->>Client: Prompt OAuth Authentication
    Client->>Auth: Sign in with Google / GitHub
    Auth-->>Client: OAuth Access Token
    Client->>Server: Call MCP Tool (e.g. get_balances)
    Server->>DB: Fetch Encrypted API Keys
    Server->>Server: Decrypt Keys & Validate Tool Policy
    Server->>Exchange: CCXT Signed Request
    Exchange-->>Server: Response Raw Payload
    Server-->>Client: Normalized Context-Efficient JSON

⚡ Quick Start

1. Install Dependencies

Clone the repository and install the production dependencies:

git clone https://github.com/AmaLS367/TradeMcp.git
cd TradeMcp
npm install

2. Configure Environment

Create your local .env configuration:

cp .env.example .env

Generate a secure 64-character encryption key:

node -e "console.log(require('crypto').randomBytes(32).toString('hex'))"

Configure your .env with the generated ENCRYPTION_KEY and your Firebase credentials.

3. Run the Server

Development Mode:

npm run dev

Production Build:

npm run build
npm start

🐳 Docker Deployment:

docker compose up -d --build

⚙️ Configuration

Runtime settings are managed securely using .env variables:

VariableRequiredDefaultDescription
ENCRYPTION_KEYYes-64-char hex key for AES-256-GCM encryption of user API credentials.
FIREBASE_SERVICE_ACCOUNT_KEYYes-Raw JSON string or path to Firebase Admin SDK service account key.
PORTNo3000Port the Express server listens on.
PUBLIC_BASE_URLNohttp://localhost:3000Public URL of the server (required for production OAuth).
PUBLIC_GITHUB_CLIENT_IDNo-Optional client ID for GitHub OAuth authentication.
PUBLIC_GITHUB_CLIENT_SECRETNo-Optional client secret for GitHub OAuth authentication.

🧪 Quality Checks

Keep code clean, typed, and fully tested before every deployment:

# Type check TypeScript without emitting files
npm run lint

# Run all unit and integration tests using Vitest
npm test

💖 Support

If Trade MCP helps you, you can support development through GitHub Sponsors, referral links, or crypto donations.

MethodLink
GitHub SponsorsSponsor AmaLS367
Bybit referralRegister with Bybit
Binance referralRegister with Binance

Crypto wallets:

NetworkAddress
TONUQA0r9FHhWDP3HbS5bIN7RPUcF9H8AAzN_P3niATSS5SyALG
MetaMask (BTC)bc1q47h0yzwps6hgsmg809q9hy86e3n4jck29sgw6v

Referral links may provide a small reward to the maintainer at no extra cost to you.


📁 Project Structure

TradeMcp/
├── src/
│   ├── server/
│   │   ├── env.ts              # Zod environment schema and validation
│   │   ├── mcpEarn.ts          # Unified Bybit & Binance yield aggregator
│   │   ├── mcpServerFactory.ts # MCP Server creation, tool schemas, and routes
│   │   ├── mcpToolPolicy.ts    # Access profiles and security mapping
│   │   └── logger.ts           # Structured Pino logger
│   └── App.tsx                 # Web dashboard frontend application
├── docs/                       # Comprehensive documentation
│   ├── agent-guide.md          # Multi-tenant agent guides
│   ├── client-setup.md         # ChatGPT, Cursor, and Claude configuration
│   └── architecture.md         # Component mapping and structural flow
├── docker-compose.yml          # Container configuration for VPS deployment
├── package.json                # Project dependencies and workspace scripts
└── tsconfig.json               # TypeScript strict options configuration

Ver o original no GitHub

Bom para

Relacionados