Featured

Deploy OpenClaw in 60 seconds — 20% off logoDeploy OpenClaw in 60 seconds — 20% off

Launch OpenClaw on Hostinger in about 60 seconds and keep your agent live 24/7. Our referral link gives you 20% off, no coupon code needed.

Launch on Hostinger
Run your Hermes agent on Hostinger, fully managed logoRun your Hermes agent on Hostinger, fully managed

Launch Hermes on Hostinger in one click, fully managed, no VPS knowledge needed. Use code ZACAARON10 for 10% off.

Launch on Hostinger
Crawl and scrape any site into clean data, 10% off logoCrawl and scrape any site into clean data, 10% off

Firecrawl crawls and scrapes any site into clean markdown for your agent. Get 1,000 free credits, and new users get 10% off their first purchase.

Try Firecrawl free
Your own AI agent, running 24/7 with QwikClaw logoYour own AI agent, running 24/7 with QwikClaw

QwikClaw sets up and runs an always-on OpenClaw agent for you. One click, no config files, no server setup.

Deploy now
One API to scrape, enrich, and extract the internet. logoOne API to scrape, enrich, and extract the internet.

Context.dev gives your agents a single API to scrape, enrich, and extract live web data — no proxies, no parsers, no maintenance.

Start building free
SetupClaw: done-for-you OpenClaw for founders & exec teams logoSetupClaw: done-for-you OpenClaw for founders & exec teams

White-glove OpenClaw for founders and exec teams (4–50+ employees): we install, harden, integrate your tools, and maintain it — secured from day one.

Get it set up for you
SEO data APIs for your agent, $1 free credit logoSEO data APIs for your agent, $1 free credit

DataForSEO gives your agent live access to SERP results, keyword data, backlinks, and on-page SEO data through one API. New accounts get a $1 credit, good for up to 20,000 keyword or backlink lookups.

Try DataForSEO free
Reach 47,000+ AI builders

A flat monthly placement in front of developers actively installing AI tools. No lock-in, cancel anytime.

Advertise here

Works with

Claude CodeClaude DesktopCursorVS CodeClineCodex CLIOpenClaw+ any MCP client

Install to Claude Code

This server doesn't publish a one-line install command. Follow the setup in the source repository.

Summary

Provides cryptocurrency market data (prices, symbols) and a gated demo trading flow via MCP tools, with safety defaults like dry-run and confirmation gates.

README.md

crypto_mcp

crypto_mcp is a refactor of crypto_bot into a single MCP-first repository.

Python requirement: >=3.11.

For user-facing capability map, see: docs/CAPABILITIES.MD.

What this project does

  • Expose deterministic MCP tools over stdio.
  • Keep transport contract stable for LLM clients.
  • Separate market data (safe/read-only) from trading (gated).
  • Keep exchange adapters replaceable.

Architecture

  • src/crypto_mcp/mcp_server.py: FastMCP server and tool definitions.
  • src/crypto_mcp/agent.py: NL command router mapping prompts to MCP tools.
  • src/crypto_mcp/config.py: Typed settings loader with sane defaults and clamps.
  • src/crypto_mcp/adapters/binance.py: Binance HTTP adapter abstraction.
  • src/crypto_mcp/main.py: Runnable MCP entrypoint.
  • tests/: MCP contract, core server, and agent unit tests.

Detailed architecture: docs/ARCHITECTURE.MD.

Capabilities quick table

| Area | What it does | Main MCP tools | |---|---|---| | Runtime health | Reports service state, limits, mode, exchanges | health | | Exchange inventory | Lists adapter-backed exchanges | list_exchanges | | Market data | Fetches ticker prices and symbol lists | get_price, list_exchange_symbols | | Guarded execution | Submits demo orders with explicit confirmation gate | submit_demo_order, confirm_pending_order | | NL routing | Maps natural language to MCP tool calls | crypto-mcp-agent |

Design pattern references taken from polymarket_mcp:

  • deterministic tool envelope: {ok, tool, ...}
  • bounded limits for list/read tools
  • safety confirmation flow for trade tools
  • split entrypoint (main.py) from MCP server implementation

Quickstart

python -m venv .venv
source .venv/bin/activate
pip install -e ".[dev]"
cp .env.example .env
python -m pytest
crypto-mcp-server
# separate terminal
crypto-mcp-agent

Setup path-style variant:

cd /path/to/crypto_mcp
python -m venv .venv
source .venv/bin/activate
pip install -e ".[dev]"
cp .env.example .env

Alternative module runner:

python -m crypto_mcp.main
crypto-mcp

Safety defaults

  • DRY_RUN=true

Default path is non-live demo execution.

Run MCP server locally

Stdio server (local MCP clients):

crypto-mcp-server

For MCP Inspector debugging:

npx @modelcontextprotocol/inspector python -m crypto_mcp.main

Do not write print() logs inside stdio server paths. Use logging to stderr.

Available MCP tools:

  • health
  • list_exchanges
  • get_price
  • list_exchange_symbols
  • submit_demo_order
  • confirm_pending_order

Tool response envelope is consistent:

  • ok: boolean
  • tool: tool name
  • error + error_category on failures
  • tool-specific payload under payload

MCP limits are controlled by:

  • MCP_DEFAULT_LIMIT
  • MCP_MAX_LIMIT
  • MCP_CONTEXT_MODE (shared or request)

Order safety controls are controlled by:

  • DRY_RUN
  • REQUIRE_CONFIRMATION_ABOVE_USD

Connect this MCP to clients

Use path placeholders:

  • path/to/crypto_mcp = repository root.
  • path/to/crypto_mcp/.venv/bin/python = project interpreter.

GitHub Copilot (VS Code Agent Mode)

Add MCP server config in your VS Code MCP settings JSON:

{
  "mcpServers": {
    "crypto-mcp": {
      "command": "python",
      "args": ["-m", "crypto_mcp.main"],
      "cwd": "path/to/crypto_mcp",
      "env": {
        "PYTHONPATH": "src"
      }
    }
  }
}

If your environment requires venv binary, use:

{
  "command": "path/to/crypto_mcp/.venv/bin/python",
  "args": ["-m", "crypto_mcp.main"]
}

Claude Desktop

Edit Claude Desktop MCP config and add:

{
  "mcpServers": {
    "crypto-mcp": {
      "command": "path/to/crypto_mcp/.venv/bin/python",
      "args": ["-m", "crypto_mcp.main"],
      "cwd": "path/to/crypto_mcp",
      "env": {
        "PYTHONPATH": "src"
      }
    }
  }
}

Restart Claude Desktop after changes.

OpenCode

OpenCode can run MCP from command config. Add server entry in your OpenCode MCP configuration:

{
  "mcpServers": {
    "crypto-mcp": {
      "command": "path/to/crypto_mcp/.venv/bin/python",
      "args": ["-m", "crypto_mcp.main"],
      "cwd": "path/to/crypto_mcp",
      "env": {
        "PYTHONPATH": "src"
      }
    }
  }
}

Then restart OpenCode session and verify tools:

  • health
  • list_exchanges
  • get_price
  • list_exchange_symbols
  • submit_demo_order
  • confirm_pending_order

OpenCode install and usage:

# install OpenCode (example)
npm install -g opencode-ai

# verify installation
opencode --version

# start session in this repository
cd path/to/crypto_mcp
opencode

Inside OpenCode:

  • ensure MCP server crypto-mcp is connected.
  • run a quick tool check with health.
  • ask natural language command examples:
  • "get btcusdt price"
  • "list 20 symbols"
  • "buy 50 btcusdt"

Environment

Copy .env.example to .env and update values.

  • MCP_DEFAULT_LIMIT, MCP_MAX_LIMIT
  • MCP_CONTEXT_MODE (shared or request)
  • DRY_RUN (true/false)
  • EXCHANGES_ENABLED (binance default)
  • GEMINI_API_KEY (optional, used by local NL routing layer)
  • BINANCE_API_BASE_URL
  • BINANCE_API_KEY, BINANCE_API_SECRET
  • REQUIRE_CONFIRMATION_ABOVE_USD

For this task, an empty .env file exists and is safe because defaults are clamped.

What this MCP can do

Read-only tools:

  • health: service status, context mode, limits, enabled exchanges.
  • list_exchanges: list adapter-backed exchanges.
  • get_price: fetch ticker price for symbol/exchange.
  • list_exchange_symbols: bounded symbol list with clamp.

Trading flow tools (safety-gated):

  • submit_demo_order: validates side/symbol/size and creates pending confirmation above threshold.
  • confirm_pending_order: executes pending order if valid and not expired.

Order confirmation flow:

  1. Call submit_demo_order.
  2. If payload has status=pending_confirmation, capture confirmation_id.
  3. Call confirm_pending_order(confirmation_id).

Contract:

  • deterministic response envelope: {ok, tool, payload} on success.
  • deterministic error envelope: {ok, tool, error, error_category} on failure.
  • live trading intentionally disabled: returns live_trading_not_implemented when DRY_RUN=false.

Safety Notes

  • submit_demo_order never executes live orders; with DRY_RUN=false it returns live_trading_not_implemented.
  • submit_demo_order requires explicit confirmation for large notional.
  • response shape never raises raw exceptions to MCP caller; errors are categorized.

Tests

python -m pytest

Important notes

  • Local MCP stdio transport must keep stdout clean JSON-RPC only.
  • This project is starter infrastructure. Not trading advice.
  • Add stronger risk modules before real funds.

Known improvement areas (scan summary)

  • Add adapter-level symbol tradability validation before order acceptance.
  • Replace broad internal exception mapping with sanitized provider error codes.
  • Add confirmation-expiry regression tests at MCP wrapper level.
  • Add optional HTTP transport runner for remote clients.

See related servers & alternatives →

Related MCP servers

Browse all →

Related guides

Hand-picked reading to help you choose and use Finance & Payments servers.