Bitso MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BITSO_API_KEY | Yes | Your Bitso API key | |
| BITSO_API_SECRET | Yes | Your Bitso API secret |
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_withdrawalsD | – |
| get_withdrawalD | – |
| get_withdrawals_by_idsD | – |
| get_withdrawals_by_origin_idsD | – |
| list_fundingsD | – |
| get_fundingD | – |
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 6 tools
The tools have clear distinctions between funding and withdrawal operations, with specific 'get' and 'list' variants. However, the two 'get_withdrawals_by_*' tools could be confusing as they serve similar purposes (retrieving withdrawals by different ID types) without clear differentiation in their names or descriptions.
All tools follow a consistent verb_noun pattern with underscores, using 'get' for single retrievals and 'list' for collections. The naming is predictable and uniform across all six tools, with no deviations in style or convention.
Six tools is a reasonable number for a financial transaction server, covering core funding and withdrawal operations. It's slightly lean but appropriate for the apparent scope, though it might benefit from additional tools for actions like creating or updating transactions.
The toolset is severely incomplete for a financial platform, covering only read operations (get and list) for fundings and withdrawals. There are no tools for creating, updating, or deleting transactions, which are essential for a full CRUD lifecycle in this domain, leaving significant gaps that will hinder agent workflows.