CoinCap APIを用いた包括的な暗号通貨分析を提供するモデルコンテキストプロトコル（MCP）サーバー。使いやすいインターフェースを通じて、リアルタイムの価格データ、市場分析、過去のトレンド情報を提供します。
これは、Tracey Russellによるオリジナルのmcp-crypto-priceプロジェクトのフォークです。
✅ 変更点:
CoinCap v3 API を使用するように更新されました (v2 は廃止されるため)。
時間の許す限り、追加の改善とテストが計画されています。
💡 Coin Capの「ステーク・ツー・API」サブスクリプションモデルに敬意を表します。もっと多くのAPIプロバイダーに採用してもらえることを願っています。サブスクリプション疲れは現実です！
パッケージノート: このプロジェクトは GitHub で
wazzan/mcp-coincap-jjとしてホストされていますが、npm では@bujaayjaay/mcp-coincap-jjとして公開されています。
Related MCP server: Coin MCP Server
MCP サーバーを初めて使用する場合は、このガイドで開始するための手順を段階的に説明します。
Mac が乱雑にならないように Windows 11 VM でテストしましたが、問題なく動作しました。
Claude デスクトップ構成の場所:
MacOS : ~/Library/Application Support/Claude/claude_desktop_config.json
Windows : %APPDATA%/Claude/claude_desktop_config.json
🟢 Windows セットアップ ガイド (どの MCP クライアントでも同じ手順)
Node.js をインストールします: ( https://nodejs.org/en )
Claude Desktopをインストールする
Claude デスクトップを設定します。
ハンバーガーメニュー（左上隅）を開く → ファイル → 設定 → 開発者 → 設定の編集
これにより、Windows エクスプローラーで claude_desktop_config.json ファイルの場所が開きます。
お気に入りのエディターで編集し、次の構成を追加します (すべての閉じ括弧を含めるようにしてください)。
他のMCPクライアントにも同じ手順を使用できます。
{
"mcpServers": {
"mcp-coincap-jj": {
"command": "npx",
"args": [
"-y",
"@bujaayjaay/mcp-coincap-jj"
],
"env": {
"COINCAP_API_KEY": "INPUT_YOUR_API_KEY_HERE"
}
}
}
}ローカルでプロジェクトに取り組みたい開発者および貢献者向け:
npm install @bujaayjaay/mcp-coincap-jjgit clone https://github.com/wazzan/mcp-coincap-jj.git
cd mcp-coincap-jj
npm install # Install dependencies
npm run build # Compile TypeScript code
npm test # Run tests to verify everything works
npm start # Starts the MCP server locallyローカルテスト用の MCP サーバー構成 (Windows の例)
npx を使用してローカルで実行する場合は、Claude Desktop (または任意の MCP クライアント) で次の構成を使用します。
{
"mcpServers": {
"mcp-coincap-jj": {
"command": "cmd.exe",
"args": [
"/c",
"C:\\Program Files\\nodejs\\npx.cmd",
"C:\\Users\\YOUR-WINDOWS-USERNAME\\repos\\github\\mcp-coincap-jj"
],
"env": {
"COINCAP_API_KEY": "YOUR_API_KEY_HERE"
},
"disabled": false,
"alwaysAllow": []
}
}
}🔧 プロのヒント: Windows で絶対パスを使用すると、特に複数の環境を実行する場合にスムーズなエクスペリエンスが保証されます。
個人的な学習経験は多少失われますが、すぐに始めるには最適です。
ClaudeデスクトップアプリにSmitheryがインストールされていることを確認してください
次のコマンドを実行します。
smithery install @bujaayjaay/mcp-coincap-jjセットアップ中にCoinCap APIキーを入力するよう求められます
v2 は廃止されるため、更新された v3 API を使用するには、CoinCap から API キーを取得する必要があります: ( https://pro.coincap.io/api-docs/ )
get-crypto-price以下を含むあらゆる暗号通貨の現在の価格と 24 時間の統計を取得します:
現在の価格（米ドル）
24時間の価格変動
取引量
時価総額
市場ランク
get-market-analysis以下を含む詳細な市場分析を提供します:
取引量上位5つの取引所
取引所間の価格変動
ボリューム分布分析
VWAP（出来高加重平均価格）
get-historical-analysis以下の方法で過去の価格データを分析します。
カスタマイズ可能な時間間隔（5分～1日）
最大30日間の履歴データのサポート
価格動向分析
ボラティリティ指標
高価格帯/低価格帯
「ビットコインの現在の価格はいくらですか？」
「ETHの市場分析を見せてください」
「DOGEの7日間の価格履歴を教えてください」
「BTC を取引するトップの取引所はどこですか？」
「SOL の価格動向を 1 時間間隔で表示してください」
このプロジェクトはTracey Russellのmcp-crypto-priceのフォークです。
Tracey のプロジェクトは、Alex Andru のcoincap-mcpプロジェクトに触発されました。
このプロジェクトはMITライセンスの下でライセンスされています
Get current price and 24h stats for a cryptocurrency
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes | Cryptocurrency symbol (e.g., BTC, ETH) |
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.
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.
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.
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.
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.
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 price analysis with customizable timeframe
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes | Cryptocurrency symbol (e.g., BTC, ETH) | |
| interval | No | Time interval (m5, m15, m30, h1, h2, h6, h12, d1) | h1 |
| days | No | Number of days to analyze (1-30) |
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.
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.
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.
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.
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.
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 detailed market analysis including top exchanges and volume distribution
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes | Cryptocurrency symbol (e.g., BTC, ETH) |
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.
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.
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.
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.
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.
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.
Each tool targets a distinct aspect: current price, historical analysis, and market analysis. No overlap in purpose.
All tools follow a consistent 'get-' prefix with snake_case descriptors, e.g., get-crypto-price, get-historical-analysis.
Three tools is an ideal size for a focused crypto data server, covering essential operations without bloat.
Covers current price, historical trends, and market depth. Minor gap: no tool to list supported cryptocurrencies, but core workflows are complete.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Unlock the power of real-time cryptocurrency data with our Crypto Price Insights MCP server.
A Model Context Protocol (MCP) server for Selise Blocks Cloud integration
MCP server giving AI agents one-connection access to crypto & DeFi data: DeFi protocol TVL, stableco
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/wazzan/mcp-coincap-jj'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
