wallet_history — HOTLIKESHOP MCP Tool
wallet_history
(wallet history) is one of 32 tools on the
HOTLIKESHOP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call wallet_history from your client
- Claude Code HOTLIKESHOP wallet_history run in your project directory
- Claude Desktop HOTLIKESHOP wallet_history ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor HOTLIKESHOP wallet_history ~/.cursor/mcp.json
- VS Code HOTLIKESHOP wallet_history .vscode/mcp.json
- Zed HOTLIKESHOP wallet_history ~/.config/zed/settings.json
- Windsurf HOTLIKESHOP wallet_history ~/.codeium/windsurf/mcp_config.json
- Cline HOTLIKESHOP wallet_history ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI HOTLIKESHOP wallet_history ~/.gemini/settings.json
- Grok HOTLIKESHOP wallet_history .mcp.json (in your project root)
- ChatGPT HOTLIKESHOP wallet_history Settings → Connectors → Advanced → Developer mode
- Claude.ai HOTLIKESHOP wallet_history Settings → Connectors → Add custom connector
- LangChain HOTLIKESHOP wallet_history pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http hotlikeshop-mcp https://hotlikeshop.com/api/mcp
Other tools on this server
- search_products
- get_product
- list_categories
- list_category_products
- get_2fa
- check_live_facebook
- check_health_bulk
- deep_inspect
- recommend_products
- topup_guide
- how_to_start
- best_sellers
- latest_products
- compare_products
- similar_products
- get_my_balance
- quote_order
- buy_product
- check_order_status
- submit_complaint
- list_orders
- get_mail_code
- create_usdt_deposit
- verify_usdt_deposit
- create_binance_deposit
- verify_binance_deposit
- gamefi_status
- daily_checkin
- spin_wheel
- list_quests
- claim_quest
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.