A
licenseNot graded
qualityD
maintenanceProvides comprehensive cryptocurrency analysis using the CoinCap API, offering real-time price data, market analysis across exchanges, and historical price trends for any cryptocurrency.
385
MIT
coincap-mcp
by QuantGeekDev
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., "@coincap-mcpwhat's the current price of ethereum?"
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.
Coincap MCP
What does this server do?
Allows you to query crypto information from coincap's public API - no API keys or registration required
Related MCP server: CoinCap MCP Server
🚀 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
{
"mcpServers": {
"mongodb": {
"command": "npx",
"args": ["coincap-mcp"]
}
}
}Installing via Smithery
To install Coincap for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install coincap-mcp --client claudePrerequisites
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
{
"mcpServers": {
"coincap-mcp": {
"command": "/path/to/coincap-mcp/build/index.js"
}
}
}Development
Install dependencies:
npm installBuild the server:
npm run buildFor development with auto-rebuild:
npm run watch📜 License
This project is licensed under the MIT License - see the LICENSE file for details.
Available Tools
3 toolsbitcoin_priceB
Get realtime bitcoin price
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
B3.2/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden for behavioral disclosure. While 'Get realtime bitcoin price' implies a read-only operation, it doesn't specify data source, update frequency, rate limits, authentication requirements, or error conditions. The description is minimal and lacks important behavioral context.
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?
The description is extremely concise at just three words, front-loaded with the core functionality. Every word earns its place: 'Get' specifies the action, 'realtime' provides important temporal context, and 'bitcoin price' identifies the 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?
For a simple price lookup tool with no parameters and no output schema, the description is minimally adequate. However, without annotations and with sibling tools that might overlap in functionality, more context about what makes this tool distinct would be beneficial. The description doesn't specify return format, currency, or data source.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has 0 parameters with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't discuss parameters since none exist, and the empty input schema is correctly documented.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose with a specific verb ('Get') and resource ('bitcoin price'), and includes the qualifier 'realtime' which distinguishes it from historical or aggregated price tools. However, it doesn't explicitly differentiate from sibling tools like 'get_crypto_price' which might also provide bitcoin prices.
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?
The description provides no guidance on when to use this tool versus alternatives like 'get_crypto_price' or 'list_assets'. It doesn't mention any prerequisites, limitations, or specific contexts where this tool is preferred over siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_crypto_priceC
Get realtime crypto price on crypto
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Name of the crypto coin |
TDQS
C2.6/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 burden. It mentions 'realtime' which hints at freshness, but doesn't disclose behavioral traits like rate limits, data sources, error handling, or what 'realtime' means operationally. It's minimal for a tool with no annotation coverage.
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 a single, short sentence that's front-loaded with the core purpose. However, it's slightly redundant ('on crypto') and could be more polished, but it earns its place efficiently.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no annotations and no output schema, the description is incomplete. It doesn't explain return values, error cases, or operational constraints. For a tool fetching real-time data, more context on behavior and output is needed.
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%, with the parameter 'name' documented as 'Name of the crypto coin'. The description adds no additional meaning beyond this, such as format examples or valid coin names. Baseline 3 is appropriate since the schema does the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose3/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states the tool 'Get realtime crypto price on crypto' which identifies the verb ('get') and resource ('crypto price'), but it's vague about scope and duplicates 'crypto' awkwardly. It doesn't clearly differentiate from sibling tools like 'bitcoin_price' or 'list_assets'.
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 is provided on when to use this tool versus alternatives like 'bitcoin_price' (specific to Bitcoin) or 'list_assets' (which might list multiple assets). The description implies real-time pricing but doesn't specify contexts or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_assetsB
Get all available crypto assets
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
B3.1/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Get all available crypto assets' but doesn't explain what 'available' means (e.g., supported by the API, currently tradable), whether it's a read-only operation, if there are rate limits, or what the response format looks like. This leaves significant gaps for a tool with zero annotation coverage.
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?
The description is a single, efficient sentence with no wasted words. It's appropriately sized for a simple tool and front-loads the key information directly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimal. It states what the tool does but lacks context on usage versus siblings, behavioral details like response format or constraints, and doesn't leverage the opportunity to provide more guidance. For a tool in a server with sibling tools, this is inadequate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has 0 parameters, and the schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and a baseline score of 4 is appropriate for a parameterless tool where the schema fully covers the input structure.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Get') and resource ('all available crypto assets'), providing a specific purpose. However, it doesn't differentiate from sibling tools like 'bitcoin_price' or 'get_crypto_price' which appear to be more specific price-fetching tools, so it doesn't fully distinguish from alternatives.
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?
The description provides no guidance on when to use this tool versus the sibling tools ('bitcoin_price' and 'get_crypto_price'). It doesn't specify if this is for listing assets versus getting prices, or any prerequisites or exclusions for usage.
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. Dates show when Glama detected each change.
3 tool updates
v1.0.0- Added
bitcoin_price - Added
get_crypto_price - Added
list_assets
TDQS
C2.7/5.0
Disambiguation2/5
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.
Naming Consistency3/5
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.
Tool Count3/5
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.
Completeness2/5
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.
Maintenance
ActivityInactive
ResponsivenessSyncing
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Live and historical cryptocurrency prices via CoinGecko free API.
Free, keyless live cryptocurrency prices, market cap, and 24h change via CoinGecko.
CoinGecko-backed live prices, market caps, DeFi metrics — no per-user API key needed.
Related MCP Servers
- FlicenseAqualityDmaintenanceProvides access to cryptocurrency market data through the CoinCap API v3, enabling users to retrieve real-time prices, exchange rates, market information, and detailed data for various cryptocurrencies.5-
- FlicenseCqualityCmaintenanceProvides access to CoinCap's cryptocurrency market data and technical analysis tools via MCP, supporting assets, exchanges, markets, and more.38317-
- AlicenseNot gradedqualityDmaintenanceProvides real-time cryptocurrency data from CoinGecko, including prices, market data, historical data, and coin search.11MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/QuantGeekDev/coincap-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server