Coinmarket MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COINMARKET_API_KEY | Yes | CoinMarketCap API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_currency_listingsB | Get latest cryptocurrency listings |
| get_quotesC | Get cryptocurrency quotes |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Latest cryptocurrency listings from coinmarket | Cryptocurrency listings |
| Cryptocurrency quotes | Cryptocurrency quotes |
TDQS
Scored across 2 tools
The two tools both retrieve cryptocurrency market data, and the vague descriptions make it unclear whether get_quotes is for individual coins or a different listing format. Agents may struggle to choose between them for a given request.
Both tools follow a consistent get_<object> pattern with clear verb-noun structure. The naming is predictable and easy to understand.
With only 2 tools, the server feels minimal but not entirely insufficient for basic market data retrieval. The scope is limited, but the count is borderline, not extreme.
The server lacks obvious capabilities such as historical data, currency conversion, or detailed metadata lookups, making it incomplete for a comprehensive cryptocurrency market server. Only the most basic listing and quote operations are covered.