HOTLIKESHOP MCP

Search the public catalog by keyword in the product name; returns id, name, price (VND), stock, category and url. Read-only, no api_key required. WHEN TO USE: the user already has a search term or product name. PREFER INSTEAD: list_categories + list_category_products to browse without a keyword, best_sellers for "popular", latest_products for "new", get_product for the full detail of one id. Not f

Get the full public detail of ONE product by its numeric id: name, price (VND), stock, category, long description and url. Read-only, no api_key required. WHEN TO USE: after search_products / list_category_products / best_sellers gave you an id and the user wants the full description of that single item. PREFER INSTEAD: compare_products to evaluate 2-5 ids at once, similar_products to find alterna

List every public category with its id, name and in-stock product count. Read-only, takes no parameters, no api_key required. WHEN TO USE: call this FIRST to discover the category taxonomy and get the category_id values required by list_category_products, best_sellers, latest_products and recommend_products. PREFER INSTEAD: search_products when the user already has a keyword, or how_to_start for o

No parameter schema on file.

List in-stock public products inside ONE category by category_id: id, name, price (VND), stock. Read-only, no api_key required. PREREQUISITE: get category_id from list_categories first. WHEN TO USE: browse everything in a chosen category. PREFER INSTEAD: search_products for keyword search across all categories, best_sellers to rank a category by sales, recommend_products to filter by budget, lates

Generate the current 2FA/TOTP code (6 digits) from a Base32 secret key (Google Authenticator style). Computed on the server in-memory only, never stored or logged. Free, no api_key required. WHEN TO USE: the user has an authenticator secret key (from an account they bought or own) and needs the live TOTP code now. PREFER INSTEAD: get_mail_code for email OTP/verification codes delivered to a mail-b

Check whether ONE Facebook UID (numeric) is live or dead via the public profile-picture endpoint (server-side). Read-only, free, no api_key required. Facebook blocks datacenter IPs, so if it cannot verify it returns status "needs_proxy" — pass your own "proxy" to check reliably. WHEN TO USE: a single Facebook UID. PREFER INSTEAD: check_health_bulk for many accounts at once or for Instagram/Telegra

Bulk live/dead check for MANY accounts at once (max 20 per call): Facebook UID (numeric) or Instagram/Telegram/TikTok usernames. Returns per-item status + a summary. Read-only, free, no api_key required. IG/FB items that cannot be verified (datacenter IP blocked) are moved to "skipped" — pass your own "proxy" to check them reliably. WHEN TO USE: a list of 2-20 accounts, or any non-Facebook platfor

Deep profile lookup for ONE social account (server-side, best-effort, public data only): Instagram/TikTok → followers, bio, verified, media; Telegram → title, members; Facebook UID → live/dead + avatar. Read-only, free, no api_key required. IG/FB block datacenter IPs → if it cannot read it returns status "needs_proxy"; pass your own "proxy" to read reliably. WHEN TO USE: you want rich detail about

Recommend in-stock public products by budget and/or keyword/category, cheapest first, with a simple combo suggestion. Read-only, no api_key required, public fields only (price VND). WHEN TO USE: the user has a budget or a vague need ("something under 50k for Facebook"). PREFER INSTEAD: search_products for an exact keyword, best_sellers for popularity, latest_products for newest, list_category_prod

Explain how to add funds (deposit) to a hotlikeshop account and list the active deposit methods/networks + min/max. Info only — this tool never moves money. Read-only. WHEN TO USE: call this FIRST, before create_usdt_deposit or create_binance_deposit, to see which networks are enabled; pass api_key to also show current balance & the shortfall vs a target amount. PREFER INSTEAD: how_to_start for fu

Onboarding guide for NEW users: how to start buying on hotlikeshop through this MCP (create account -> get api_key -> top up -> search & buy). Read-only, no api_key required. WHEN TO USE: the very FIRST call for a new / international user, or whenever someone lacks an api_key or asks "how does this work". Lists which tools are free vs. which need an api_key. PREFER INSTEAD: topup_guide for deposit

List best-selling in-stock public products (most sold first), public fields only (price VND + units sold). Read-only, no api_key required. WHEN TO USE: the user wants "popular / hot / most bought" items. PREFER INSTEAD: latest_products for "new arrivals", search_products for a keyword, recommend_products for a budget, list_category_products for a full category. Optionally scope with category_id (f

List newest in-stock public products (recently added first), public fields only (price VND). Read-only, no api_key required. WHEN TO USE: the user wants "new arrivals / just added". PREFER INSTEAD: best_sellers for "popular", search_products for a keyword, recommend_products for a budget, list_category_products for a full category. Optionally scope with category_id (from list_categories) or a keyw

Compare 2–5 public products side by side (price, stock, min/max, sold, category) with a quick summary (cheapest / most stock / best seller). Read-only, no api_key required, public fields only (price VND). PREREQUISITE: you already have 2-5 product ids. WHEN TO USE: help the user pick between specific candidates. PREFER INSTEAD: get_product for one id in depth, similar_products to first discover co

Given ONE product id, list similar in-stock public products (same category, best-selling first; fills with newest from other categories if few). Read-only, no api_key required, public fields only (price VND + units sold). PREREQUISITE: a known product id. WHEN TO USE: suggest alternatives / cross-sell around an item the user is viewing, then optionally compare_products. PREFER INSTEAD: search_prod

Get your account balance, level and discount (requires your shop api_key). Read-only, spends nothing. WHEN TO USE: the user asks "how much do I have" or you need to confirm funds before quote_order / buy_product. PREFER INSTEAD: wallet_history for the full ledger of top-ups/spends/refunds, topup_guide to add funds, quote_order to price a specific purchase. Requires a valid api_key. Xem số dư & hạn

STEP 1 of buying: get a price quote for a product BEFORE purchasing. Returns unit price, discount, total to pay (VND), your balance, stock, and a confirm_token (single-use, valid ~5 min). SPENDS NOTHING. Requires api_key + product_id. WHEN TO USE: always call this first, then show the total to the user and get explicit approval before buy_product. PREFER INSTEAD: get_my_balance to only check funds

STEP 2 of buying: place the order using the confirm_token from quote_order. IRREVERSIBLE — this SPENDS real balance and delivers the product; returns order_code + the delivered content. PREREQUISITE: a fresh confirm_token from quote_order (same api_key). WHEN TO USE: only AFTER the user has explicitly approved the exact total shown by quote_order. Do NOT call speculatively or to re-price. AFTERWAR

Check the status and delivered content (account credentials) of ONE of your orders by order_code (requires your api_key). Read-only by default — spends nothing. OPTIONAL refresh=true: if the order looks stuck/undelivered (pending/failed), re-triggers delivery from the system (async, safe — never charges money, never touches a completed/refunded order) then returns the current status; poll again af

File a complaint / warranty-refund request for ONE delivered order (requires your api_key). Opens a support case; the shop reviews within 3 days and if unresolved in time the order is auto-refunded. NOT idempotent — one complaint per order, so confirm with the user before calling. PREREQUISITE: an order_code that was delivered and is genuinely faulty. WHEN TO USE: the bought item is wrong / dead /

List your recent orders (order history), paginated, with order_code, product, quantity, total paid, status and date (requires your api_key). Read-only, spends nothing. WHEN TO USE: the user wants their purchase history or you need to find an order_code. AFTERWARDS: check_order_status (with refresh=true to nudge a stuck order) / get_mail_code for a specific order_code. PREFER INSTEAD: wallet_histor

Get the latest email OTP / verification code for a purchased mail-bundled account order. Supports Hotmail/Outlook via OAuth (refresh_token) and mail.tm (email + password). Read-only. PREREQUISITE: api_key + an order_code whose delivered account includes an inbox. WHEN TO USE: the user needs the verification code sent to the email that came with their order. PREFER INSTEAD: get_2fa for authenticato

Create a USDT deposit order to top up your balance. The SERVER generates the real receiving wallet address and a unique amount (with cents) — relay them to the user VERBATIM, never invent or edit a wallet address. Supports TRC20 / BEP20 / Polygon / Arbitrum / Base. PREREQUISITE: api_key; call topup_guide FIRST to see which networks are active + min/max. WHEN TO USE: the user wants to deposit on-ch

Check / confirm a USDT deposit created by create_usdt_deposit. Scans the blockchain for a matching transfer and credits your balance when found. Idempotent — safe to poll every ~15s, credits only once. PREREQUISITE: order_code + claim_token from create_usdt_deposit. WHEN TO USE: after the user has sent the USDT, to confirm and credit it; optionally pass method="hash" + tx_hash to verify by a speci

Create a Binance Pay deposit order to top up your balance. The SERVER returns the shop receive Pay ID (and QR) plus a unique USDT amount (with cents) — relay them VERBATIM, never invent them. PREREQUISITE: api_key AND Binance Pay must be enabled (check topup_guide first). WHEN TO USE: the user will pay inside the official Binance app. AFTERWARDS: call verify_binance_deposit with merchant_trade_no.

Check / confirm a Binance Pay deposit created by create_binance_deposit. Reads the shop Binance Pay history for a matching transfer and credits your balance when found. Idempotent — safe to poll every ~12s, credits only once. PREREQUISITE: merchant_trade_no from create_binance_deposit. WHEN TO USE: after the user has paid via Binance Pay, to confirm and credit it. PREFER INSTEAD: verify_usdt_depos

Get the balance ledger for the account: every top-up (bank/USDT/Binance Pay + bonuses, check-in, missions, wheel, reviews, affiliate) and every spend (purchases) / refund, with the running balance after each entry, plus totals in/out. Paginated (20/page, newest first). Read-only, spends nothing. WHEN TO USE: the user wants a history of money movements or to audit where funds went. PREFER INSTEAD:

One-shot overview of all FREE balance rewards the account can grab right now: daily check-in (available today? streak, reward range), lucky-wheel spins available, and the quest board (how many quests are complete & claimable). Read-only. WHEN TO USE: call this FIRST whenever the user asks about rewards/free balance, then use daily_checkin / spin_wheel / list_quests + claim_quest to collect. Note:

Perform the once-a-day check-in and collect the reward (random 200-1,000đ base + streak milestone bonuses at 7/30 days, sometimes x2 combo). Idempotent — if already checked in today it just says so (no double credit). Each check-in also grants +1 lucky-wheel spin. Reward credits the SHOPPING balance (not withdrawable). WHEN TO USE: the user wants to claim today's free check-in. PREFER INSTEAD: gam

Spin the lucky wheel once and return the prize won + new balance. Consumes exactly one spin server-side (NOT free to repeat — each call uses a spin). PREREQUISITE: available spins, earned from check-ins/deposits/purchases (see gamefi_status). WHEN TO USE: the user has spins and wants to use one. PREFER INSTEAD: daily_checkin to earn a spin first, gamefi_status to see how many spins remain. Winning

List the daily & weekly quest board with progress: each quest key, title, reward, current/target progress, whether it is complete and whether it is already claimed. Read-only, spends nothing. WHEN TO USE: the user wants to see quests or you need a quest_key. AFTERWARDS: call claim_quest on any quest that is complete but not yet claimed. PREFER INSTEAD: gamefi_status for a combined rewards summary

Claim the reward for ONE completed quest. Server verifies completion from real data; idempotent — one claim per quest per period (a second call will not double-credit). Reward credits the SHOPPING balance (not withdrawable). PREREQUISITE: a quest_key that is complete-but-unclaimed, from list_quests or gamefi_status. WHEN TO USE: collect a finished quest. PREFER INSTEAD: list_quests to find which q