
Mcp Bitso
io.github.codesparPublished by GitHub account codesparv0.2.2Updated Oct 24, 2026
MCP server for Bitso — Latin American crypto exchange, trading, funding, withdrawals
Overview
A local MCP server for the Bitso Latin American crypto exchange that lets an assistant read market data and account details and place, cancel and withdraw funds
- What you can do
- Read market data: tickers and order books for trading pairs, plus executed trades and applicable fees. Manage orders: create buy or sell orders, look up orders by ID or client ID, list and filter orders, cancel one order or all open orders. Review the account: balances, ledger entries, fundings, withdrawals, KYC and verification status, and funding sources and destinations. Move funds: create crypto or fiat withdrawal requests.
- When to use it
- Useful when you want an assistant to monitor Bitso markets, inspect balances and order history, or place and cancel orders and request withdrawals through conversation instead of the exchange web interface.
- Requirements
- Runs locally via npx, so Node.js is needed. A Bitso account with API credentials is required: the API key and secret are passed as the environment variables BITSO_API_KEY and BITSO_API_SECRET, and requests are signed with HMAC-SHA256. Network access to Bitso is needed.
Installation
In SourceWeft
- Open Mcp Bitso in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@codespar/mcp-bitso
MCP server for Bitso — Latin American cryptocurrency exchange with trading, orders, and withdrawals
Quick Start
Claude Desktop
Add to ~/.config/claude/claude_desktop_config.json:
Claude Code
Cursor / VS Code
Add to .cursor/mcp.json or .vscode/mcp.json:
Tools (20)
Authentication
Bitso uses HMAC-SHA256 signed requests with an API key and secret.
Sandbox / Testing
Bitso provides a developer sandbox via the developer account.
Get your credentials
- Go to Bitso
- Create an account
- Navigate to API settings and generate key and secret
- Set the environment variables
Environment Variables
Roadmap
v0.2 (planned)
get_account_status— Get account verification statuslist_currencies— List available cryptocurrenciescreate_spei_withdrawal— Create a SPEI (Mexican bank) withdrawalget_phone_number— Get phone number associated with accountlist_open_orders— List all open orders
v0.3 (planned)
recurring_orders— Create and manage recurring buy/sell ordersadvanced_orders— Advanced order types (OCO, trailing stop)
Want to contribute? Open a PR or request a tool.
Links
Enterprise
Need governance, budget limits, and audit trails for agent payments? CodeSpar Enterprise adds policy engine, payment routing, and compliance templates on top of these MCP servers.
License
MIT
Source: packages/crypto/bitso/README.md at commit d0a519a
Tools
0Version history
1- v0.2.2LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts