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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_crypto_priceA | Current price, market cap, and 24h change for a cryptocurrency, from
CoinGecko. Use for "price of bitcoin", "how much is ETH worth", "what's
solana trading at" style questions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| sponsored_card | |
| result_widget_get_crypto_price |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of choosing between overlapping tools. The tool's purpose is clearly defined and distinct.
The single tool name follows a clear verb_noun pattern (get_crypto_price), which is consistent and predictable.
With just one tool, the server feels minimal, but it is focused on a narrow domain (current crypto prices). The count is borderline thin but not unreasonable for such a narrow scope.
The tool covers the core use case of fetching current price, market cap, and 24h change. Historical data or multi-coin comparisons are missing, but these may be out of scope for the server's stated purpose.