Skip to main content
Glama
bitpanda-labs

Bitpanda Developer API MCP Server

Official
by bitpanda-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Bitpanda Developer API MCP Server

No user-submitted related servers found.

    Related Servers

    • Trading 212 MCP Server

      NigelVanHattum
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes Trading 212 trading account, instruments, orders, history, and pies as MCP tools. Allows placing and canceling real orders (defaults to demo/paper environment).
      Apache 2.0

    • Binance MCP

      UpperMoon0
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables secure access to Binance public market data and authenticated account information through a compact set of MCP tools, with optional trading operations that can be explicitly enabled.
      MIT

    • crypto_mcp

      DressPD
      F
      license
      C
      quality
      D
      maintenance
      Provides cryptocurrency market data (prices, symbols) and a gated demo trading flow via MCP tools, with safety defaults like dry-run and confirmation gates.
      6
      -

    • mcp-cryptocompare

      pipeworx-io
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables fetching cryptocurrency prices, historical OHLC data, and news via CryptoCompare API through an MCP gateway.
      4 npm
      MIT

    • Indodax MCP Server

      adhinugroho1711
      F
      license
      Not graded
      quality
      D
      maintenance
      Exposes Indodax's Private and Public REST APIs as MCP tools, enabling AI agents to manage cryptocurrency trading and account information. It supports tasks like checking market prices, viewing account balances, and executing or canceling buy and sell orders.
      -
    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 7 tools

    Disambiguation5/5

    Each tool targets a distinct resource or operation: asset metadata, portfolio snapshot, single price, price list, trade history, transaction history, and wallet balances. No two tools have overlapping purposes.

    Naming Consistency5/5

    Tool names follow a consistent pattern: 'get_' for retrieving a single entity (asset, portfolio, price) and 'list_' for enumerating collections (prices, trades, transactions, wallets). This makes the set predictable and easy to navigate.

    Tool Count5/5

    7 tools is well-scoped for a cryptocurrency exchange API. It covers essential read operations (asset data, portfolio, prices, trades, transactions, wallets) without unnecessary bloat, and each tool serves a clear purpose.

    Completeness4/5

    The tool surface covers the primary read-only needs: asset info, portfolio, prices, transactions, and wallets. Minor gaps exist, such as lack of order placement or deposit/withdrawal operations, but these are likely out of scope for a 'Developer API' focused on data retrieval.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources