Skip to main content
Glama
aderik

bitvavo-mcp

by aderik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to bitvavo-mcp

No user-submitted related servers found.

    Related Servers

    • CryptoPilot MCP

      cryptopilot-tools
      A
      license
      A
      quality
      D
      maintenance
      Connects Claude Desktop to crypto and brokerage portfolio data via Coinbase and SnapTrade, providing read-only tools to inspect accounts, holdings, prices, and provider health.
      5
      MIT

    • t212-mcp-server

      paulaigue
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides read-only access to Trading 212 accounts, enabling AI assistants to retrieve portfolio positions, account summaries, instrument data, and transaction history.
      20 npm
      5
      MIT

    • OKX MCP Server

      mbarinov
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to interact with OKX trading accounts through read-only access to retrieve portfolio information, trading positions, order history, and account analytics. Provides secure, local processing of trading data without storing sensitive information or enabling trade execution.
      5
      21 npm
      4
      MIT

    • market-mcp

      konstantinmk
      A
      license
      A
      quality
      C
      maintenance
      Enables Claude to read Moscow Exchange market data and T-Invest brokerage account data, including quotes, candles, order books, dividends, portfolio, and operations. It is read-only and does not place orders.
      7
      MIT

    • Binance MCP Server

      Lubodi-Code
      A
      license
      A
      quality
      D
      maintenance
      Enables Claude to query Binance Spot market data, account balances, and execute trades via natural language, with withdrawals disabled by default for security.
      11
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: ping checks connectivity, get_balance lists balances, get_portfolio_value computes total value, and so on. A few pairs like get_trades vs get_transactions (live vs local) and get_balance vs get_portfolio_value (per-asset vs total) overlap conceptually, but the descriptions clarify the boundaries.

    Naming Consistency4/5

    The naming is predominantly verb_noun with get_ prefix for data retrieval, import_transactions for ingestion, and ping for health checks. The deviation from get_ is minor and standard, and all names use snake_case consistently, making the set predictable and readable.

    Tool Count5/5

    14 tools is well within the ideal 3-15 range and appropriately scoped for a cryptocurrency exchange server. Each tool covers a distinct aspect such as market data, balances, history, or analytics, with no redundant or missing obvious tools.

    Completeness3/5

    The server covers market data, balances, deposits/withdrawals, trades, and local transaction history for P&L, which is substantial. However, it lacks core order management operations like place/cancel order or fetching a single order by ID, leaving a notable gap for a trading-focused exchange MCP.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources