Skip to main content
Glama
deenesjakoruzh
truss44

Crypto Price & Market Analysis MCP Server

by truss44
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Crypto Price & Market Analysis MCP Server

NPM Downloads

A Model Context Protocol (MCP) server that provides comprehensive cryptocurrency analysis using the CoinCap API. This server offers real-time price data, market analysis, and historical trends through an easy-to-use interface. Supports both STDIO and Streamable HTTP transports.

Requirements

  • Node.js 22.14+

  • CoinCap API key via COINCAP_API_KEY

Related MCP server: mcp-coincap-jj

What's New

  • BREAKING: CoinCap v2 API removed. Now uses v3 API exclusively. A COINCAP_API_KEY is required (free tier available at pro.coincap.io/dashboard)

  • Streamable HTTP transport added (while keeping STDIO compatibility)

  • Smithery CLI scripts to build and run the HTTP server

  • 6 new tools: assets-search, market-global, assets-compare, analysis-candlestick, price-convert, assets-info

  • Hierarchical tool naming: All tools organized into category-prefixed names (price-*, market-*, assets-*, analysis-*)

  • Output schemas: All tools now declare outputSchema with structuredContent for type-safe responses

  • MCP best practices: isError flag on validation errors, server description, and asset://{symbol} resource template

Usage

Add this configuration to your Claude Desktop config file:

  • MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json

  • Windows: %APPDATA%/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "mcp-crypto-price": {
      "command": "npx",
      "args": ["-y", "mcp-crypto-price"],
      "env": {
        "COINCAP_API_KEY": "YOUR_API_KEY_HERE"
      }
    }
  }
}

If your MCP client requires launching via cmd.exe on Windows:

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

Development scripts

pnpm dev          # Development (HTTP server with hot reload via Smithery CLI)
pnpm build         # Compile TypeScript → dist/
pnpm format        # Format source files with Prettier
pnpm lint          # Check for lint errors (ESLint + typescript-eslint)
pnpm lint:fix      # Auto-fix lint errors
pnpm types:check   # TypeScript type-check without emitting files
pnpm test          # Run all tests with Vitest
pnpm test:coverage # Run tests with coverage report (Vitest)
pnpm inspector     # Open MCP inspector for interactive debugging

Run as Streamable HTTP server

You can run the server over HTTP for environments that support MCP over HTTP streaming.

  • Dev server (recommended during development):

pnpm dev

  • Build and run the HTTP server:

# Build (outputs to dist/)
pnpm build

# Start the HTTP server
pnpm start:http

  • Build and run the STDIO server:

# Build (outputs to dist/)
pnpm build

# Start the STDIO server
pnpm start:stdio

The server listens on port 3000 by default (override with PORT). For clients that connect over HTTP (e.g. Smithery, Claude.ai), pass your API key as a query parameter:

http://localhost:3000/mcp?COINCAP_API_KEY=YOUR_API_KEY_HERE

For remote deployments:

https://mcp-crypto-price.codemonkeyinnovations.com/mcp?COINCAP_API_KEY=YOUR_API_KEY_HERE

Required: CoinCap API Key

This server uses the CoinCap v3 API, which requires an API key. A free tier is available.

  1. Sign up and get your API key at pro.coincap.io/dashboard

  2. Add the key to your MCP client configuration:

    • STDIO: via the COINCAP_API_KEY environment variable (see Usage examples above)

    • HTTP: via the COINCAP_API_KEY query parameter in the connection URL (e.g. /mcp?COINCAP_API_KEY=your_key)

Without a valid API key, all tools will return an error with instructions on how to obtain one.

Note for Smithery CLI users

This MCP server works directly via pnpm dlx (configs above) and does not require Smithery.

If you do use the Smithery CLI, authenticate with smithery auth login or by setting SMITHERY_API_KEY in your environment. Recent versions of the Smithery CLI do not support passing API keys via --key (or older --profile patterns).

Launch Claude Desktop to start using the crypto analysis tools.

Tools

price-get

Gets current price and 24h stats for any cryptocurrency, including:

  • Current price in USD

  • 24-hour price change

  • Trading volume

  • Market cap

  • Market rank

price-convert

Converts a cryptocurrency amount into any fiat currency:

  • Uses real-time price data and USD-based exchange rates

  • Parameters: symbol (e.g. BTC), amount (default 1), currency (default usd)

  • Example: 2.5 BTC in EUR

market-analysis

Provides detailed market analysis including:

  • Top 5 exchanges by volume

  • Price variations across exchanges

  • Volume distribution analysis

  • VWAP (Volume Weighted Average Price)

market-global

Provides an overview of the entire cryptocurrency market:

  • Total market capitalization across all assets

  • 24-hour trading volume

  • Number of active cryptocurrencies

  • Bitcoin dominance percentage

  • Top gainers and losers

market-rates

Returns USD-based conversion rates for fiat currencies and cryptocurrencies:

  • All fiat currency rates (USD base)

  • Top 10 cryptocurrency rates

  • Optional slug parameter (e.g. euro, bitcoin) for a single rate lookup

market-exchanges

Lists top cryptocurrency exchanges ranked by 24h volume:

  • Exchange name, rank, and 24h volume in USD

  • Number of trading pairs and market share percentage

  • Optional exchangeId parameter (e.g. binance) for single exchange details

  • Optional limit parameter (1–50, default 10)

assets-top

Lists top cryptocurrencies ranked by market cap, including:

  • Current price in USD

  • 24-hour price change

  • Market cap and rank

  • Configurable result count (1–50, default 10)

assets-search

Searches for cryptocurrencies by name or symbol with fuzzy matching:

  • Returns matching assets with symbol, name, price, and rank

  • Configurable result count (1–50, default 10)

  • Example: search "bit" returns Bitcoin, Bitcoin Cash, BitTorrent, etc.

assets-info

Returns detailed metadata for a single cryptocurrency:

  • ID, rank, symbol, and name

  • Price, 24h change, market cap, and volume

  • Circulating supply and max supply

  • VWAP (24h)

assets-compare

Compares 2–5 cryptocurrencies side by side:

  • Price, 24h change, market cap, volume, and rank for each asset

  • Comma-separated symbols (e.g. BTC,ETH,SOL)

  • Highlights best performer by 24h change

analysis-historical

Analyzes historical price data with:

  • Customizable time intervals (5min to 1 day)

  • Support for up to 30 days of historical data

  • Price trend analysis

  • Volatility metrics

  • High/low price ranges

analysis-technical

Returns the latest technical indicators for any cryptocurrency:

  • SMA (Simple Moving Average) with period

  • EMA (Exponential Moving Average) with period

  • RSI (Relative Strength Index) with Overbought/Oversold/Neutral signal

  • MACD with signal line, histogram, and Bullish/Bearish label

  • VWAP (Volume Weighted Average Price, 24h)

analysis-candlestick

Retrieves OHLCV candlestick data for a cryptocurrency:

  • Open, high, low, close, and volume for each candle

  • Configurable interval (5m, 15m, 30m, 1h, 2h, 6h, 12h, 1d)

  • Supports 1–30 days of historical candles

Resources

The server exposes the following MCP resources:

  • info://server — Server name and version metadata

  • asset://{symbol} — Cryptocurrency asset information by symbol (e.g. asset://BTC), returned as JSON

Prompts

The server exposes the following MCP prompts that clients can invoke:

Prompt

Args

Description

analyze-crypto

symbol

Comprehensive analysis: price, market, historical trends

compare-cryptocurrencies

symbols

Compare 2-5 cryptos side-by-side

market-overview

—

Global market snapshot: metrics, top assets, top exchanges

crypto-conversion

symbol, amount?, currency?

Convert crypto amount to fiat

exchange-analysis

symbol

Exchange landscape analysis for a crypto

technical-analysis

symbol

Full technical analysis: indicators, candles, trends

crypto-screener

query

Search and screen cryptos for opportunities

Sample Prompts

  • "What's the current price of Bitcoin?"

  • "Show me market analysis for ETH"

  • "Give me the 7-day price history for DOGE"

  • "What are the top exchanges trading BTC?"

  • "Show me the price trends for SOL with 1-hour intervals"

  • "What are the technical indicators for ETH right now?"

  • "What's the current EUR to USD exchange rate?"

  • "Which crypto exchanges have the highest 24h volume?"

  • "Search for cryptocurrencies matching 'sol'"

  • "Give me a global overview of the crypto market"

  • "Compare BTC, ETH, and SOL side by side"

  • "Show me 1-hour candlestick data for BTC over the last 3 days"

  • "Convert 2.5 BTC to EUR"

  • "Get detailed info about the Ethereum asset"

  • "Generate a comprehensive analysis of a cryptocurrency covering price, market, and historical trends"

  • "Find all cryptocurrencies with 'bit' in their name and show me their current prices"

  • "What's the market cap ranking and circulating supply of Cardano?"

  • "Compare the top 3 stablecoins and show which has the highest volume"

  • "Show me how Bitcoin has performed over the past 30 days with daily candles"

  • "Convert 100 SOL to GBP and show the exchange rate"

  • "Give me a full market snapshot: global metrics, top gainers, and BTC dominance"

  • "What are the best and worst performing cryptos in the last 24 hours?"

  • "Show me 15-minute candlestick data for ETH over the last 2 days"

  • "Compare DeFi tokens: UNI, AAVE, COMP, and MKR"

  • "What's the VWAP and max supply of Bitcoin?"

  • "Search for layer-2 tokens and compare the top results"

License

This project is licensed under the MIT License

Available Tools

3 tools
get-crypto-priceCInspect

Get current price and 24h stats for a cryptocurrency

ParametersJSON Schema
NameRequiredDescriptionDefault
symbolYesCryptocurrency symbol (e.g., BTC, ETH)

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'Get current price and 24h stats', which implies a read-only operation, but fails to detail critical aspects like rate limits, error handling, data sources, or response format. This leaves significant gaps in understanding how the tool behaves in practice.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's function without unnecessary words. It is front-loaded with the core purpose, making it easy to parse and understand quickly, with zero wasted content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete for effective tool use. It does not explain what the return values include (e.g., price units, 24h stats details) or address potential complexities like handling invalid symbols. For a tool with no structured behavioral data, more context is needed to ensure reliable agent invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with the 'symbol' parameter well-documented. The description adds no additional meaning beyond the schema, such as examples of valid symbols or constraints. Given the high schema coverage, the baseline score of 3 is appropriate, as the schema handles the parameter documentation adequately.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Get') and resource ('current price and 24h stats for a cryptocurrency'), making the purpose specific and understandable. However, it does not explicitly differentiate from sibling tools like 'get-historical-analysis' or 'get-market-analysis', which likely provide different types of cryptocurrency data, preventing a score of 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, such as the sibling tools 'get-historical-analysis' or 'get-market-analysis'. It lacks explicit context, exclusions, or prerequisites, leaving usage decisions ambiguous for an AI agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get-historical-analysisCInspect

Get historical price analysis with customizable timeframe

ParametersJSON Schema
NameRequiredDescriptionDefault
daysNoNumber of days to analyze (1-30)
intervalNoTime interval (m5, m15, m30, h1, h2, h6, h12, d1)h1
symbolYesCryptocurrency symbol (e.g., BTC, ETH)

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states what the tool does but doesn't mention critical aspects like whether this is a read-only operation, potential rate limits, authentication requirements, or what the analysis output includes. For a tool with no annotations, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose with no wasted words. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (3 parameters, no annotations, no output schema), the description is insufficient. It doesn't explain what the analysis returns, how the parameters interact, or any behavioral constraints. For a tool that presumably returns analytical data, the lack of output information is a notable gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description mentions 'customizable timeframe' which loosely relates to the 'days' and 'interval' parameters, but it doesn't add meaningful semantics beyond what the schema already provides. With 100% schema description coverage, the baseline is 3, and the description doesn't compensate with additional insights about parameter usage or interactions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb ('Get') and resource ('historical price analysis'), and it adds the customizable timeframe aspect. However, it doesn't explicitly distinguish this tool from its siblings (get-crypto-price and get-market-analysis), which would be needed for a score of 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus its siblings (get-crypto-price and get-market-analysis). It mentions 'customizable timeframe' but doesn't specify scenarios or alternatives, leaving the agent without context for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get-market-analysisCInspect

Get detailed market analysis including top exchanges and volume distribution

ParametersJSON Schema
NameRequiredDescriptionDefault
symbolYesCryptocurrency symbol (e.g., BTC, ETH)

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves analysis but doesn't mention whether it's a read-only operation, requires authentication, has rate limits, or what the output format looks like. For a tool with no annotations, this leaves significant gaps in understanding its behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the purpose without unnecessary details. It avoids redundancy and waste, though it could be slightly more structured by explicitly separating key components like scope or limitations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of market analysis, no annotations, and no output schema, the description is incomplete. It doesn't explain what 'detailed market analysis' entails beyond top exchanges and volume distribution, nor does it cover behavioral aspects like data freshness or error handling, leaving the agent with insufficient context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with the 'symbol' parameter clearly documented. The description adds no additional parameter details beyond what the schema provides, such as examples of analysis outputs or constraints. With high schema coverage, the baseline score of 3 is appropriate as the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Get' and the resource 'detailed market analysis', specifying it includes 'top exchanges and volume distribution'. This distinguishes it from sibling tools like 'get-crypto-price' (price only) and 'get-historical-analysis' (historical trends), though it doesn't explicitly mention how it differs from them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like 'get-crypto-price' or 'get-historical-analysis'. The description implies usage for market analysis details but doesn't specify scenarios, prerequisites, or exclusions, leaving the agent to infer context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.2/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: get-crypto-price focuses on current price and 24-hour stats, get-historical-analysis covers historical price data with customizable timeframes, and get-market-analysis provides detailed market insights like top exchanges and volume distribution. There is no overlap or ambiguity between these tools.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with hyphens (get-crypto-price, get-historical-analysis, get-market-analysis). The naming is predictable and readable throughout the set.

Tool Count3/5

With only 3 tools, the set feels thin for a server described as 'Crypto Price & Market Analysis.' While the tools cover key areas, more comprehensive analysis might require additional operations like trend prediction, exchange comparisons, or portfolio tracking, suggesting a borderline under-scoping.

Completeness3/5

The tools cover current price, historical analysis, and market analysis, which are core to the domain, but there are notable gaps. For example, there is no tool for comparing multiple cryptocurrencies, fetching real-time alerts, or performing predictive analytics, which could limit agent workflows in a full market analysis context.

Maintenance

ActivityActive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • mcp-coincap-jj

    wazzan
    A
    license
    A
    quality
    B
    maintenance
    A Model Context Protocol (MCP) server that provides comprehensive cryptocurrency analysis using the CoinCap API. This server offers real-time price data, market analysis, and historical trends through an easy-to-use interface. Updated to use Coin Cap API v3
    3
    71
    1
    MIT

  • Realtime Crypto MCP Server

    smhnkmr
    A
    license
    Not graded
    quality
    D
    maintenance
    A server that provides real-time cryptocurrency data through the Model Context Protocol, allowing access to detailed exchange information and current cryptocurrency rates from the CoinCap API.
    16
    1
    MIT

  • My HTTP MCP Server

    joheiss
    F
    license
    Not graded
    quality
    D
    maintenance
    A Model Context Protocol server that provides cryptocurrency data tools and resources via an HTTP endpoint. It enables users to fetch real-time market data from Binance, track activity logs, and generate cryptocurrency executive summaries.

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/truss44/mcp-crypto-price'

If you have feedback or need assistance with the MCP directory API, please join our Discord server