Get the FREE Ultimate OpenClaw Setup Guide →

crypto

🪙 Model Context Protocol (MCP) server for cryptocurrency data. Uses Binance public API (no auth required) with CoinMarketCap fallback. Token-optimized responses for LLM applications.

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio pand40x-crypto-mcp node /absolute/path/to/crypto-mcp/build/index.js \
  --env COINMARKETCAP_API_KEYS="your_cmc_api_key_1,your_cmc_api_key_2"

How to use

This MCP server provides cryptocurrency data by querying Binance public endpoints and automatically falling back to CoinMarketCap (CMC) if Binance is unavailable or rate-limited. It exposes tools to fetch real-time prices, batch multiple prices in parallel, and retrieve historical candlestick data with pagination support. The data is returned in compact, token-efficient formats to minimize LLM usage. To interact with the server, use the available tools get_price, batch_prices, and get_history. The server is designed to be drop-in compatible with MCP clients, streaming results over stdio or your MCP client connection as defined by the MCP protocol.

How to install

Prerequisites:

  • Node.js (v14+)
  • npm (v6+)

Installation steps:

  1. Clone the repository or obtain the MCP server package.
  2. Navigate to the project directory.
  3. Install dependencies:
npm install
  1. Build the project if a build step exists:
npm run build
  1. Configure environment variables (see Configuration section) and run the server:
npm start
  1. If developing locally, you can run in development mode (hot reloading, etc.) if supported:
npm run dev

Configuration notes:

  • Ensure COINMARKETCAP_API_KEYS is set if you plan to use the CMC fallback.
  • Binance API keys are not required for public endpoints used by this server.
  • Ensure the MCP client references the correct path to the built server entry (see MCP Client Configuration in README).

Additional notes

Tips and common issues:

  • If CMC API keys expire or rate limits are hit, rotate keys by updating COINMARKETCAP_API_KEYS with a comma-separated list.
  • The get_history endpoint supports startTime and endTime; if endTime is omitted, the current time is used.
  • The batch_prices tool returns a count and an array of quotes; ensure your client handles missing data gracefully in edge cases.
  • For production deployments, consider setting a reasonable rate limit and caching strategy to minimize external API calls.
  • The server uses Binance public endpoints by default; no API keys are required for price data, but you may want to configure CMC keys for fallback scenarios.

Related MCP Servers

Sponsor this space

Reach thousands of developers ↗