coincap-mcp
# Coincap MCP
[](https://smithery.ai/server/coincap-mcp)
## What does this server do?
Allows you to query crypto information from coincap's public API - no API keys or registration required
## 🚀 Quick Start
To get started, add this configuration to your Claude Desktop config file:
**MacOS**: `~/Library/Application\ Support/Claude/claude_desktop_config.json`
**Windows**: `%APPDATA%/Claude/claude_desktop_config.json`
```json
{
"mcpServers": {
"mongodb": {
"command": "npx",
"args": ["coincap-mcp"]
}
}
}
```
### Installing via Smithery
To install Coincap for Claude Desktop automatically via [Smithery](https://smithery.ai/server/coincap-mcp):
```bash
npx -y @smithery/cli install coincap-mcp --client claude
```
### Prerequisites
- Node.js 18+
- npx
Then, launch Claude Desktop and you're ready to go!
## Sample Prompts
- What is the price of bitcoin?
- What are the available crypto assets?
- What is the market cap of ethereum?
## Tools
#### Bitcoin Price Tool
Gets price for Bitcoin specifically, it's a simple example of a primitive API call tool
#### Get Crypto Price Tool
Gets price for any cryptocurrency available on coincap API. It's a good example of how to get mandatory parameter data for your tool calls
#### List Assets
Gets a list of all crypto assets available in coincap API
## Development - local build
To build it locally:
On MacOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
On Windows: `%APPDATA%/Claude/claude_desktop_config.json`
```json
{
"mcpServers": {
"coincap-mcp": {
"command": "/path/to/coincap-mcp/build/index.js"
}
}
}
```
## Development
Install dependencies:
```bash
npm install
```
Build the server:
```bash
npm run build
```
For development with auto-rebuild:
```bash
npm run watch
```
## 📜 License
This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
TDQS
Scored across 3 tools
Two tools (bitcoin_price and get_crypto_price) have overlapping purposes, both focused on fetching crypto prices, which creates ambiguity. The descriptions do not clearly differentiate them, making it likely an agent could misselect between them. The third tool (list_assets) is distinct, but the overlap between the first two significantly reduces clarity.
The naming is mixed, with two tools using a verb_noun pattern (get_crypto_price, list_assets) and one using a noun_verb pattern (bitcoin_price). While readable, this inconsistency in verb placement and specificity (bitcoin vs. crypto) deviates from a predictable convention. The patterns are not chaotic but lack uniformity.
With 3 tools, the count is borderline thin for a crypto data server, as it may lack comprehensive coverage for common operations like historical data or multiple asset queries. However, it is reasonable for a minimal or focused scope, though it feels slightly under-scoped for typical crypto API use cases.
The tool set has significant gaps for a crypto data domain, such as missing operations for historical price data, market cap info, volume, or specific asset details beyond listing. The overlap in price tools does not add functionality, and agents may struggle with incomplete workflows like tracking trends or comparing assets over time.