mcp-orbit-kraken
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KRAKEN_API_KEY | No | Kraken API key (required for private endpoints) | |
| KRAKEN_DB_PATH | No | SQLite database path for grid trading (default: data/grids.db) | data/grids.db |
| KRAKEN_PRIVATE_KEY | No | Kraken API private key (required for private endpoints) | |
| GRID_WEBHOOK_SECRET | No | Secret for grid check webhook authentication | |
| GRID_CHECK_WEBHOOK_URL | No | Webhook URL for grid monitoring (default: http://localhost:3001) | http://localhost:3001 |
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 | {} |
| prompts | {} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| kraken_add_orderC | Execute a buy or sell order for cryptocurrency on the Kraken exchange |
| kraken_cancel_orderB | Cancel an active order on Kraken using its unique identifier |
| kraken_cancel_all_ordersA | Execute a command to cancel all open orders in the trading account |
| kraken_query_ordersA | Retrieve detailed information about specific orders, including their execution status |
| kraken_edit_orderB | Modify an existing order by updating price, volume, or other execution parameters |
| kraken_cancel_all_orders_afterA | Schedule a time window after which all open orders will be cancelled automatically |
| kraken_get_server_timeA | Fetch the current time according to the Kraken server |
| kraken_get_system_statusB | Retrieve the current operational status of the Kraken platform |
| kraken_get_asset_infoB | Get detailed information about supported assets, including precision and margin availability |
| kraken_get_tradable_asset_pairsB | List tradable asset pairs. For filtering cached results, use "altname" (e.g., "BTCEUR") or "wsname" (e.g., "BTC/EUR") fields. |
| kraken_get_ticker_infoB | Retrieve ticker information including bid/ask, last trade, and volume data |
| kraken_get_ohlc_dataB | Obtain open, high, low, close (OHLC) candlestick data for a specific asset pair |
| kraken_get_order_bookA | Fetch the current order book depth for an asset pair |
| kraken_get_recent_tradesB | Retrieve the most recent public trades for an asset pair |
| kraken_get_recent_spreadsB | List recent bid-ask spreads for an asset pair to analyze market depth |
| kraken_get_account_balanceA | Get the current account balance for all assets on Kraken exchange |
| kraken_get_extended_balanceB | Retrieve extended balance information, including credit and hold details |
| kraken_get_deposit_methodsB | Retrieve available deposit methods for a specific asset |
| kraken_get_deposit_addressesC | Get deposit addresses for an asset using a selected method |
| kraken_get_deposit_statusA | Check the status of recent deposit transfers for an asset |
| kraken_get_withdrawal_methodsB | Retrieve available withdrawal methods for a specific asset |
| kraken_withdraw_fundsB | Initiate a withdrawal of funds to a preconfigured address |
| kraken_get_withdrawal_addressesA | List configured withdrawal addresses for a given asset and method |
| kraken_get_withdrawal_infoA | Get withdrawal fee and limit information for a requested transfer |
| kraken_get_withdrawal_statusC | Check the status of recent withdrawals for a specific asset |
| kraken_cancel_withdrawalB | Cancel a pending withdrawal using its reference ID |
| kraken_get_trades_historyB | Retrieve the history of trades and executed orders for analysis or reporting |
| kraken_get_websockets_tokenA | Retrieve a token for accessing the Websockets API to enable real-time data streams |
| kraken_wallet_transferA | Initiate a transfer of funds between Kraken wallets (e.g., spot to futures) |
| grid_planA | Pure price-level calculation for a grid. No side-effects, no DB writes. Returns computed levels with price, side (buy/sell/null), and volume for each level. |
| grid_stateB | CRUD store for grid configurations. Actions: save (upsert), get (load one), list (all summaries), delete. |
| grid_logA | Append-only audit log for grid events. append: Write a new log entry (event + optional data). read: Retrieve all log entries for a grid in chronological order. |
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 32 tools
Most tools are distinct by resource and action, but pairs like kraken_get_recent_trades (public market data) and kraken_get_trades_history (account trades) could be confused. Account balance vs extended balance are also similar, though their descriptions clarify the difference.
The kraken_* tools consistently use verb_noun snake_case, but the grid_state, grid_plan, and grid_log tools deviate with noun-only names. This creates a minor but noticeable inconsistency in the overall naming pattern.
With 32 tools, the server is over the comfortable range and becomes unwieldy for agents to select from. While the coverage is comprehensive, the sheer number makes it harder to navigate and increases cognitive load.
The server covers market data, trading operations, account balances, funding (deposits/withdrawals), system status, and grid strategy utilities. This provides full lifecycle coverage for crypto exchange workflows with no obvious missing operations.