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

  • 윈도우 : %APPDATA%/Claude/claude_desktop_config.json

지엑스피1

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을 실행하여 암호화 분석 도구를 사용해보세요.

도구

get-crypto-price

다음을 포함한 모든 암호화폐의 현재 가격과 24시간 통계를 가져옵니다.

  • 현재 가격 (USD)

  • 24시간 가격 변경

  • 거래량

  • 시가총액

  • 시장 순위

시장 분석 받기

다음을 포함한 자세한 시장 분석을 제공합니다.

  • 거래량 기준 상위 5개 거래소

  • 거래소별 가격 변동

  • 체적 분포 분석

  • VWAP(거래량 가중 평균 가격)

역사적 분석 얻기

다음을 사용하여 과거 가격 데이터를 분석합니다.

  • 사용자 정의 가능한 시간 간격(5분~1일)

  • 최대 30일 동안의 과거 데이터 지원

  • 가격 추세 분석

  • 변동성 지표

  • 높은/낮은 가격 범위

샘플 프롬프트

  • "비트코인의 현재 가격은 얼마인가요?"

  • "ETH 시장 분석을 보여주세요"

  • "DOGE의 7일 가격 내역을 알려주세요"

  • "BTC를 거래하는 주요 거래소는 어디인가요?"

  • "1시간 간격으로 SOL 가격 추세를 보여주세요"

프로젝트 영감

이 프로젝트는 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