mcp-orbit-kraken
Related Servers
Alternatives to mcp-orbit-kraken
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP server that integrates with Kraken Futures and Spot APIs to track portfolio, compute FIFO cost basis, and generate German crypto tax reports.-
- AlicenseBqualityBmaintenanceAn MCP server that exposes the Kraken cryptocurrency exchange Spot REST API over HTTP with bearer token authentication, enabling account management, trading, and market data queries through natural language.541MIT

cdcxofficial
AlicenseNot gradedqualityCmaintenanceMCP server for the Crypto.com Exchange API, providing 86 dynamically generated tools for market data, trading, account management, and more with real-time WebSocket streaming and safety enforcement.22 npm26Apache 2.0- AlicenseAqualityBmaintenanceAn MCP server for the pex.bot AI simulated crypto exchange that enables users to manage accounts, check real-time market data, and execute trades. It provides tools for profile management, order execution, and asset tracking within a simulated cryptocurrency trading environment.1176 npm1MIT
- FlicenseNot gradedqualityCmaintenanceMCP server for Hyperliquid perpetual DEX with 48 tools for trading, monitoring, risk management, and security. Enables real-time market data, order management, risk validation, and automated trading strategies.-
- FlicenseNot gradedqualityDmaintenancePython-based MCP server that provides real-time and historical cryptocurrency data from 100+ exchanges via CCXT, with tools for tickers, OHLCV, markets, and order books.1-
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.