Ein Model Context Protocol (MCP)-Server, der mithilfe der CoinCap-API umfassende Kryptowährungsanalysen ermöglicht. Dieser Server bietet Echtzeit-Preisdaten, Marktanalysen und historische Trends über eine benutzerfreundliche Oberfläche.
Dies ist ein Fork des ursprünglichen mcp-crypto-price- Projekts von Tracey Russell
✅ Was hat sich geändert:
Aktualisiert, um die CoinCap v3-API zu verwenden (da v2 eingestellt wird).
Weitere Verbesserungen und Tests sind geplant, wenn die Zeit es erlaubt.
💡 Ein großes Lob an Coin Cap für ihr „Stake-to-API“-Abonnementmodell – ich hoffe, dass mehr API-Anbieter dieses Modell übernehmen. Die Abo-Müdigkeit ist real!
Pakethinweis : Dieses Projekt wird auf GitHub als
wazzan/mcp-coincap-jjgehostet, aber auf npm als@bujaayjaay/mcp-coincap-jjveröffentlicht.
Related MCP server: Coin MCP Server
Wenn Sie mit MCP-Servern noch nicht vertraut sind, bietet Ihnen dieses Handbuch schrittweise Anweisungen für den Einstieg.
Ich habe dies auf einer Windows 11-VM getestet, um eine Überlastung meines Macs zu vermeiden – hat einwandfrei funktioniert!
Claude Desktop-Konfigurationsstandorte:
MacOS : ~/Library/Application Support/Claude/claude_desktop_config.json
Windows : %APPDATA%/Claude/claude_desktop_config.json
🟢 Windows-Setup-Anleitung (dieselben Schritte für jeden MCP-Client)
Installieren Sie Node.js: ( https://nodejs.org/en )
Installieren Sie Claude Desktop
Claude Desktop konfigurieren:
Öffnen Sie das Hamburger-Menü (oben links) → Datei → Einstellungen → Entwickler → Konfiguration bearbeiten
Dadurch wird der Speicherort der Datei claude_desktop_config.json im Windows Explorer geöffnet.
Bearbeiten Sie es mit Ihrem bevorzugten Editor und fügen Sie die folgende Konfiguration hinzu (achten Sie darauf, alle schließenden Klammern einzuschließen!):
Beachten Sie, dass Sie dieselben Anweisungen für jeden anderen MCP-Client verwenden können.
{
"mcpServers": {
"mcp-coincap-jj": {
"command": "npx",
"args": [
"-y",
"@bujaayjaay/mcp-coincap-jj"
],
"env": {
"COINCAP_API_KEY": "INPUT_YOUR_API_KEY_HERE"
}
}
}
}Für Entwickler und Mitwirkende, die lokal am Projekt arbeiten möchten:
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 locallyMCP-Serverkonfiguration für lokale Tests (Windows-Beispiel)
Wenn Sie lokal mit npx arbeiten, verwenden Sie diese Konfiguration in Claude Desktop (oder einem beliebigen MCP-Client):
{
"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": []
}
}
}🔧 Profi-Tipp: Die Verwendung absoluter Pfade unter Windows sorgt für ein reibungsloses Erlebnis, insbesondere beim Ausführen mehrerer Umgebungen.
Obwohl dadurch ein Teil der persönlichen Lernerfahrung verloren geht, ist es ein toller Schnellstart!
Stellen Sie sicher, dass Smithery für Ihre Claude Desktop-App installiert ist
Führen Sie den folgenden Befehl aus:
smithery install @bujaayjaay/mcp-coincap-jjSie werden während der Einrichtung aufgefordert, Ihren CoinCap-API-Schlüssel einzugeben
Sie müssen jetzt einen API-Schlüssel von CoinCap erhalten, um die aktualisierte API v3 zu verwenden, da v2 veraltet ist: ( https://pro.coincap.io/api-docs/ )
get-crypto-priceRuft den aktuellen Preis und 24-Stunden-Statistiken für jede Kryptowährung ab, einschließlich:
Aktueller Preis in USD
24-Stunden-Preisänderung
Handelsvolumen
Marktkapitalisierung
Marktrang
get-market-analysisBietet eine detaillierte Marktanalyse, einschließlich:
Top 5 Börsen nach Volumen
Preisschwankungen zwischen den Börsen
Volumenverteilungsanalyse
VWAP (volumengewichteter Durchschnittspreis)
get-historical-analysisAnalysiert historische Preisdaten mit:
Anpassbare Zeitintervalle (5 Minuten bis 1 Tag)
Unterstützung für bis zu 30 Tage historische Daten
Preistrendanalyse
Volatilitätsmetriken
Hohe/niedrige Preisspannen
„Wie hoch ist der aktuelle Preis von Bitcoin?“
„Zeigen Sie mir eine Marktanalyse für ETH“
„Geben Sie mir den 7-Tage-Preisverlauf für DOGE“
„Welche sind die wichtigsten Börsen, an denen BTC gehandelt wird?“
„Zeigen Sie mir die Preisentwicklung für SOL im 1-Stunden-Takt“
Dieses Projekt ist ein Fork von Tracey Russells mcp-crypto-price ,
Traceys Projekt wurde von Alex Andrus Coincap-MCP- Projekt inspiriert.
Dieses Projekt ist unter der MIT-Lizenz lizenziert
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
