crypto_mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DRY_RUN | No | Dry run mode: 'true' or 'false' | true |
| MCP_MAX_LIMIT | No | Maximum limit for list operations | |
| GEMINI_API_KEY | No | Google Gemini API key for NL routing (optional) | |
| BINANCE_API_KEY | No | Binance API key | |
| MCP_CONTEXT_MODE | No | Context mode: 'shared' or 'request' | shared |
| EXCHANGES_ENABLED | No | Comma-separated list of enabled exchanges | binance |
| MCP_DEFAULT_LIMIT | No | Default limit for list operations | |
| BINANCE_API_SECRET | No | Binance API secret | |
| BINANCE_API_BASE_URL | No | Binance API base URL | |
| REQUIRE_CONFIRMATION_ABOVE_USD | No | Minimum order notional in USD to require confirmation |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| healthD | – |
| list_exchangesD | – |
| get_priceD | – |
| list_exchange_symbolsD | – |
| submit_demo_orderD | – |
| confirm_pending_orderD | – |
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 6 tools
Each tool has a clearly distinct purpose: health for server status, list_exchanges for exchange discovery, get_price for market data, list_exchange_symbols for symbol discovery, and the two order tools for demo order submission and confirmation. No two tools appear to overlap in functionality.
Most tool names follow a verb_noun pattern with snake_case (list_exchanges, get_price, submit_demo_order), but 'health' is a bare noun that deviates from this pattern. Overall, the naming is consistent and predictable.
Six tools is a well-scoped size for a crypto demo trading server, covering health, market data, and order lifecycle without unnecessary bloat. The count fits comfortably within the ideal range.
The tool set covers market data (price, symbols) and demo order submission/confirmation, but lacks common trading operations like order cancellation, order status retrieval, or balance queries. These gaps could hinder agents trying to manage orders beyond the basic submission flow.