btse-account-setup — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited btse-account-setup (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
api_secret and is shown only onceSame steps at https://btse.com
# Configure the default account
btse-mcp config
# Configure a named account (e.g. a separate testnet account)
btse-mcp config --account-id testnetYou will be prompted for:
Credentials are stored encrypted at ~/.config/btse-mcp/accounts.enc using a Fernet key at ~/.config/btse-mcp/key (chmod 600 on Unix).
# Test the default account
btse-mcp test
# Test a named account
btse-mcp test testnetA successful test prints the current BTC-PERP last price and mark price.
Common failures:
| Error | Cause | Fix |
|---|---|---|
| Connection FAILED: HTTP 401 | Wrong API key or secret | Re-run btse-mcp config |
| Connection FAILED: HTTP 403 | Key missing Read permission | Add Read permission in BTSE API settings |
| Unexpected response | Wrong testnet setting | Check with btse-mcp list and reconfigure |
# List all configured accounts (shows testnet/live flag)
btse-mcp list
# Delete an account
btse-mcp delete testnetAll tools accept an optional account_id parameter:
btse_get_price(symbol="BTC-PERP", account_id="testnet")
btse_account_overview(account_id="live-main")Default is "default" when account_id is omitted.
Important: If you reconfigure an account with btse-mcp config, restart the MCP server (restart Claude Desktop / Cursor) for the new credentials to take effect. The server caches clients per account for the lifetime of the process.
Before any order tool, confirm the environment:
btse_get_price(symbol="BTC-PERP")If the price looks wrong for the intended environment, stop and reconfigure.
Use btse_transfer to move funds between spot and futures wallets, or between margin wallets.
Always confirm these details with the user before calling the tool:
from_wallet — source wallet nameto_wallet — destination wallet nameamount — how much to movecurrency — defaults to USDTCommon wallet names:
| Wallet | Description |
|---|---|
SPOT | Spot wallet |
CROSS@ | Cross-margin futures wallet |
ISOLATED@BTC-PERP-USDT | Isolated margin wallet for BTC-PERP |
ISOLATED@ETH-PERP-USDT | Isolated margin wallet for ETH-PERP |
Example — move 500 USDT from spot to cross futures:
btse_transfer(
from_wallet="SPOT",
to_wallet="CROSS@",
amount=500,
currency="USDT"
)Requires Transfer permission on the API key. If the call returns HTTP 403, the key needs the Transfer permission added in BTSE → Account → API settings.
Use btse_list_accounts() to confirm which account you're operating on before transferring.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.