MCP Bitpanda Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BITPANDA_API_KEY | Yes | Your Bitpanda API Key for accessing the Bitpanda API |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_tradesA | Lists all user's trades from the Bitpanda API. Newest trades come first. Response is cursor paginated. |
| list_asset_walletsB | Lists all user's asset wallets grouped by asset type from the Bitpanda API. |
| list_fiat_walletsB | Lists all user's fiat wallets from the Bitpanda API. |
| list_fiat_transactionsA | Lists all user's fiat transactions from the Bitpanda API. Newest fiat transactions come first. Response is cursor paginated. |
| list_crypto_walletsB | Lists all user's crypto wallets from the Bitpanda API. |
| list_crypto_transactionsA | Lists all user's crypto transactions from the Bitpanda API. Newest crypto transactions come first. Response is cursor paginated. |
| list_commodity_transactionsA | Lists all user's commodity transactions from the Bitpanda API. Newest commodity transactions come first. Response is cursor paginated. |
| get_asset_infoC | Retrieves detailed information for a specific asset by its symbol. |
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 8 tools
The tools are mostly distinct, focusing on different resource types like assets, wallets, transactions, and trades. However, there is some potential overlap between 'list_trades' and the transaction tools (commodity, crypto, fiat), as trades might be a subset or related to transactions, which could cause minor confusion without additional context.
All tool names follow a consistent verb_noun pattern with 'get_' or 'list_' prefixes, using snake_case throughout. This predictability makes it easy for agents to understand and select tools based on their naming conventions.
With 8 tools, the server is well-scoped for a Bitpanda API integration, covering key areas like asset information, wallets, transactions, and trades. Each tool serves a clear purpose without being overly broad or too limited for the domain.
The tools provide good read/list coverage for assets, wallets, transactions, and trades, but there are notable gaps in CRUD operations. For example, there are no tools for creating, updating, or deleting resources (e.g., executing trades or modifying wallets), which limits the server's functionality to querying only.