With this server, you can retrieve and analyze cryptocurrency data using the CoinCap API.
Get Current Price & 24h Stats: Fetch real-time cryptocurrency prices, 24-hour changes, trading volume, market cap, and rank.
Market Analysis: Obtain detailed market insights such as top exchanges by volume, price variations, volume distribution, and VWAP.
Historical Analysis: Analyze historical price data with customizable timeframes (5min to 1 day) and up to 30 days of data, including trends and volatility.
Provides real-time price data, market analysis, trading volume, market cap, and historical trends for Bitcoin through the CoinCap API.
Hosts the MCP server code repository at wazzan/mcp-coincap-jj, enabling version control and collaboration for the project.
Powers the MCP server runtime environment, allowing it to execute JavaScript/TypeScript code that interfaces with the CoinCap API.
Allows installation and distribution of the MCP server package via npm, with the package published as @bujaayjaay/mcp-coincap-jj.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-coincap-jj What's the current price of Bitcoin and its 24-hour change?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
This is a fork of the original mcp-crypto-price project by Tracey Russell
✅ What’s changed:
Updated to use the CoinCap v3 API (as v2 is being sunset).
Additional improvements and testing planned as time permits.
💡 Shoutout to Coin Cap for their “stake-to-API” subscription model—something I hope more API providers adopt. Subscription fatigue is real!
Package Note: This project is hosted on GitHub as
wazzan/mcp-coincap-jjbut published to npm as@bujaayjaay/mcp-coincap-jj
Related MCP server: Coin MCP Server
If you’re new to MCP servers, this guide provides step-by-step instructions to get you started.
I tested this on a Windows 11 VM to avoid cluttering my Mac—worked flawlessly!
Claude Desktop Config Locations:
MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%/Claude/claude_desktop_config.json
🟢 Windows Setup Guide (Same Steps for Any MCP Client)
Install Node.js: (https://nodejs.org/en)
Install Claude Desktop
Configure Claude Desktop:
Open the hamburger menu (top-left corner) → File → Settings → Developer → Edit Config
This opens the claude_desktop_config.json file location in Windows Explorer.
Edit it with your favorite editor and add the following configuration (make sure to include all closing braces!):
Note you can use these same instructions for any other MCP Client
{
"mcpServers": {
"mcp-coincap-jj": {
"command": "npx",
"args": [
"-y",
"@bujaayjaay/mcp-coincap-jj"
],
"env": {
"COINCAP_API_KEY": "INPUT_YOUR_API_KEY_HERE"
}
}
}
}For developers and contributors who want to work on the project locally:
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 Server Config for Local Testing (Windows Example)
If running locally with npx, use this configuration in Claude Desktop (or any 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": []
}
}
}🔧 Pro Tip: Using absolute paths on Windows ensures a smooth experience, especially when running multiple environments.
Although it takes away some of the personal learning experience, it’s a great quick start!
Ensure you have Smithery installed for your Claude Desktop app
Run the following command:
smithery install @bujaayjaay/mcp-coincap-jjYou'll be prompted to enter your CoinCap API key during setup
You now have to obtain an API Key from CoinCap to use the updated v3 API as v2 is being deprecated: (https://pro.coincap.io/api-docs/)
get-crypto-priceGets current price and 24h stats for any cryptocurrency, including:
Current price in USD
24-hour price change
Trading volume
Market cap
Market rank
get-market-analysisProvides detailed market analysis including:
Top 5 exchanges by volume
Price variations across exchanges
Volume distribution analysis
VWAP (Volume Weighted Average Price)
get-historical-analysisAnalyzes 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
"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"
This project is a fork of Tracey Russell's mcp-crypto-price,
Tracey’s project was inspired by Alex Andru’s coincap-mcp project.
This project is licensed under the MIT License
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
