mcp-crypto-price

This MCP server provides cryptocurrency price data, market analysis, and historical trends by interfacing with the CoinCap API. It exposes three primary tools: get-crypto-price, which returns the current price in USD along with 24-hour changes, trading volume, market cap, and market rank; get-market-analysis, which offers insights such as the top exchanges by volume, price variations across exchanges, volume distribution, and VWAP; and get-historical-analysis, which analyzes historical price data with configurable intervals (from 5 minutes up to 1 day) and supports up to 30 days of history, including trend and volatility metrics. The server can operate over STDIO or as a streamable HTTP endpoint, enabling integration with clients like Claude Desktop or Smithery.

To use, run the server via npx as configured in the MCP settings. You can optionally pass a CoinCap API key to boost rate limits; if provided, the server will prefer the v3 API and fall back to v2 if needed. There are also Windows-specific configurations available that wrap the npx call inside cmd.exe if your MCP client requires it. When running over HTTP streaming, start the HTTP server (npm run start:http) or use the development server (npm run dev) to obtain the server URL for clients supporting streaming MCP. The server supports the CoinCap API key through the COINCAP_API_KEY environment variable.

Example workflows include asking for the current price of Bitcoin, requesting market analysis for ETH, or obtaining a 7-day price history for DOGE. For enhanced access, provide an API key and opt into the HTTP streaming transport for real-time data feeds.

Prerequisites:

• Node.js (recommended LTS) and npm installed on your system
• Internet access to fetch the MCP server via npx

Installation steps:

1. Verify Node.js and npm are installed

   • node -v
   • npm -v

2. Run the MCP server using npx (no global install required):

   npx -y mcp-crypto-price

   This will fetch and run the mcp-crypto-price server directly via NPX.

3. (Optional) Provide a CoinCap API key to increase rate limits

   • Create or obtain a COINCAP_API_KEY from pro.coincap.io/dashboard

   • Run with environment variable, for example:

     COINCAP_API_KEY=YOUR_API_KEY_HERE npx -y mcp-crypto-price

4. (Optional) Run the HTTP streaming variant (if supported by your environment):

   npm run dev npm run start:http

Notes:

• You can wrap the npx execution in a Windows cmd shell if your MCP client requires cmd.exe, for example:

  { "mcpServers": { "mcp-crypto-price": { "command": "cmd", "args": ["/c", "npx", "-y", "mcp-crypto-price"] } } }

• This MCP server supports both v2 and v3 CoinCap APIs depending on whether COINCAP_API_KEY is provided.

Tips and common considerations:

• If you intend to use higher rate limits, obtain a COINCAP_API_KEY. The server will attempt v3 first when a key is present and will fall back to v2 if necessary.
• The server supports Streamable HTTP transport in addition to the traditional STDIO transport. Use the HTTP variant (start:http) for environments that support MCP over HTTP streaming.
• CoinCap is phasing out v2; without an API key, the server will use v2 by default and v3 is preferred when a key is present.
• This repository emphasizes verified commits and SSH signing. If you enable SSH signing locally, configure git to sign commits and distribute the signing key to GitHub.
• The tools provided are:
  • get-crypto-price: current price, 24h change, volume, market cap, rank
  • get-market-analysis: top exchanges by volume, cross-exchange price variations, VWAP
  • get-historical-analysis: configurable intervals, up to 30 days history, trend and volatility metrics
• When integrating with clients, start by retrieving the server URL printed by the dev/build commands and use that URL for HTTP clients that support streaming MCP.