crypto-price-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_priceA | Fetch the current price of a specified cryptocurrency from each exchange. Examples: BTC, ETH, SOL, etc. Supported exchanges: binance, coinbase, kraken, bitflyer, gmo, bybit, okx, bitget |
| get_top_rankingA | Fetch the 24-hour volume ranking for a specified exchange. Supported exchanges: binance, coinbase, kraken, bitflyer, gmo, bybit, okx, bitget |
| compare_pricesA | Compare the price of a specified asset across all exchanges, showing the lowest and highest prices. Examples: BTC, ETH, SOL, etc. |
| get_pairsA | Fetch all tradable pairs available on a specified exchange. Supported exchanges: binance, coinbase, kraken, bitflyer, gmo, bybit, okx, bitget |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Most tools are clearly distinct, but get_price and compare_prices overlap: both retrieve current prices, with compare_prices adding cross-exchange comparison and min/max output. The descriptions help clarify the difference, but an agent could still be uncertain which tool to use for a single-exchange price query.
Tool names mostly follow a get_ prefix pattern: get_top_ranking, get_price, get_pairs. compare_prices deviates slightly but is still readable and consistent with snake_case naming. Overall the pattern is predictable.
Four tools is well-scoped for a crypto price MCP server. Each tool covers a distinct core need: price lookup, price comparison, tradable pairs, and volume ranking, without unnecessary bloat.
The tool surface covers the primary price-checking workflow: retrieving prices, comparing prices across exchanges, discovering pairs, and checking volume rankings. Historical price data or market cap information would be nice additions, but their absence does not create a serious dead end for the stated purpose.