Skip to main content
Glama
deenesjakoruzh
truss44

Crypto Price & Market Analysis MCP Server

by truss44
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

暗号通貨の価格と市場分析 MCP サーバー

鍛冶屋のバッジ NPMダウンロード

CoinCap APIを用いた包括的な暗号通貨分析を提供するモデルコンテキストプロトコル（MCP）サーバー。使いやすいインターフェースを通じて、リアルタイムの価格データ、市場分析、過去のトレンド情報を提供します。

使用法

この構成を Claude Desktop 構成ファイルに追加します。

  • 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"]
    }
  }
}

Related MCP server: mcp-coincap-jj

オプション: CoinCap APIキー

レート制限を高くするには、設定に API キーを追加します。

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

重要事項：CoinCapはv2 APIを廃止します。このMCPはv2とv3の両方のAPIをサポートしています。

  • COINCAP_API_KEY指定すると、最初に v3 API の使用を試み、必要に応じて v2 にフォールバックします。

  • APIキーがない場合、v2 APIが使用されます（これは最終的に廃止されます）

  • v2 APIは将来的に完全に無効化されるため、 pro.coincap.io/ dashboardからAPIキーを取得することをお勧めします。

暗号分析ツールの使用を開始するには、Claude Desktop を起動します。

ツール

暗号通貨の価格を取得する

以下を含むあらゆる暗号通貨の現在の価格と 24 時間の統計を取得します:

  • 現在の価格（米ドル）

  • 24時間の価格変動

  • 取引量

  • 時価総額

  • 市場ランク

市場分析を取得する

以下を含む詳細な市場分析を提供します:

  • 取引量上位5つの取引所

  • 取引所間の価格変動

  • ボリューム分布分析

  • VWAP（出来高加重平均価格）

履歴分析を取得する

以下の方法で過去の価格データを分析します。

  • カスタマイズ可能な時間間隔（5分～1日）

  • 最大30日間の履歴データのサポート

  • 価格動向分析

  • ボラティリティ指標

  • 高価格帯/低価格帯

サンプルプロンプト

  • 「ビットコインの現在の価格はいくらですか？」

  • 「ETHの市場分析を見せてください」

  • 「DOGEの7日間の価格履歴を教えてください」

  • 「BTC を取引するトップの取引所はどこですか？」

  • 「SOL の価格動向を 1 時間間隔で表示してください」

プロジェクトのインスピレーション

このプロジェクトは、Alex Andru のcoincap-mcpプロジェクトに触発されました。

ライセンス

このプロジェクトはMITライセンスの下でライセンスされています

Available Tools

3 tools
get-crypto-priceBInspect

Get current price and 24h stats for a cryptocurrency

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

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided, so description must carry full burden. Only states output is price and 24h stats, but omits details like update frequency, data source, or behavior on invalid symbol.

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?

Single sentence, no unnecessary words, front-loaded with verb and resource.

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

Completeness3/5

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

Given simple tool (1 param, no output schema, no annotations), description is adequate for basic understanding but lacks detail on what '24h stats' includes (e.g., change, volume).

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?

Schema description coverage is 100%, baseline 3. Description adds no extra detail beyond 'gets crypto price for given symbol'; schema already specifies symbol as string with examples.

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

Purpose5/5

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

Description clearly states verb 'get', resource 'current price and 24h stats', and scope 'cryptocurrency'. Easily distinguished from siblings 'historical-analysis' and 'market-analysis'.

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 on when to use this tool vs alternatives (e.g., for historical data use get-historical-analysis). No exclusions or prerequisites mentioned.

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

get-historical-analysisBInspect

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

B3.2/5.0
Behavior2/5

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

No annotations provided. The description does not disclose behavioral traits such as data source (e.g., real-time vs delayed), caching, rate limits, or whether the analysis includes derived metrics like moving averages.

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?

Single sentence, front-loaded with action and key qualifier. No wasted words, but could benefit from a second sentence to enhance completeness without harming conciseness.

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

Completeness3/5

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

No output schema, so the agent cannot infer return format or fields. Description lacks details on data scope (e.g., OHLCV, volume) and pagination. Adequate for a simple analysis tool but incomplete.

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?

With 100% schema coverage, parameters are documented. The description adds 'customizable timeframe' but does not elaborate on default behavior or mutually exclusive options beyond schema.

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

Purpose5/5

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

The description clearly states the tool retrieves historical price analysis with customizable timeframe. It distinguishes from 'get-crypto-price' (current price) and 'get-market-analysis' (broader market).

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 explicit guidance on when to use this tool versus siblings. The description does not specify context like trend analysis vs point-in-time price, nor any prerequisites or exclusions.

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

get-market-analysisBInspect

Get detailed market analysis including top exchanges and volume distribution

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

TDQS

B3.4/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 full responsibility. It only mentions 'detailed' analysis without disclosing behavioral traits like rate limits, authentication needs, or mutability. The description adds minimal value beyond the tool name.

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 one sentence long and front-loaded with the main purpose. It is efficient but could be slightly more informative without being verbose.

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

Completeness3/5

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

Given the tool's simplicity (one param, no output schema, no annotations), the description minimally covers purpose but lacks context on when to use or what to expect. It is adequate but not complete for an autonomous agent.

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 parameter 'symbol' is fully described in the schema with coverage at 100%. The description repeats 'e.g., BTC, ETH' which is already in the schema, adding no new semantic information. Baseline score of 3 is appropriate.

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

Purpose5/5

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

The description clearly states the tool retrieves 'detailed market analysis' and specifies included data like 'top exchanges and volume distribution'. It distinguishes itself from siblings 'get-crypto-price' (price only) and 'get-historical-analysis' (historical data).

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

Usage Guidelines3/5

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

The description implies use for market analysis but does not explicitly state when to use it versus alternatives. No guidance on prerequisites or exclusions is provided.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 3 tool updatesv1.0.0
    • First observedget-crypto-price
    • First observedget-historical-analysis
    • First observedget-market-analysis
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.2/5.0

Scored across 3 tools

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
ResponsivenessResponsive

Resources

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
    68 npm
    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.
    13 npm
    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