HOTLIKESHOP
REMOTE · HOTLIKESHOP.COM · SCANNED SEP 20
Search & buy MMO/social accounts, proxies & digital services from HOTLIKESHOP in your AI chat.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 32 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 7068 tokens (~220/item across 32 items; 32 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 32 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 33 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the HOTLIKESHOP MCP server?
HOTLIKESHOP is a hosted endpoint at https://hotlikeshop.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · hotlikeshop.com
claude mcp add --transport http tuanone123-hotlikeshop-mcp 'https://hotlikeshop.com/api/mcp'
{
"mcpServers": {
"tuanone123-hotlikeshop-mcp": {
"url": "https://hotlikeshop.com/api/mcp"
}
}
} {
"servers": {
"tuanone123-hotlikeshop-mcp": {
"type": "http",
"url": "https://hotlikeshop.com/api/mcp"
}
}
} [mcp_servers.tuanone123-hotlikeshop-mcp] url = "https://hotlikeshop.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tuanone123-hotlikeshop-mcp": {
"type": "remote",
"url": "https://hotlikeshop.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add tuanone123-hotlikeshop-mcp --url 'https://hotlikeshop.com/api/mcp' --transport streamable-http
mcp_servers:
tuanone123-hotlikeshop-mcp:
url: "https://hotlikeshop.com/api/mcp" {
"McpServers": {
"tuanone123-hotlikeshop-mcp": {
"Transport": "http",
"Url": "https://hotlikeshop.com/api/mcp"
}
}
} assistant mcp add tuanone123-hotlikeshop-mcp -t streamable-http -u 'https://hotlikeshop.com/api/mcp'
{
"mcpServers": {
"tuanone123-hotlikeshop-mcp": {
"type": "http",
"url": "https://hotlikeshop.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 0
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “reload_order” was removed ▼ security
- Tool “best_sellers” rewrote its description, which is the text the model reads security
- Tool “buy_product” rewrote its description, which is the text the model reads security
- Tool “check_health_bulk” rewrote its description, which is the text the model reads security
- Tool “check_live_facebook” rewrote its description, which is the text the model reads security
- Tool “check_order_status” rewrote its description, which is the text the model reads security
- Tool “claim_quest” rewrote its description, which is the text the model reads security
- Tool “compare_products” rewrote its description, which is the text the model reads security
- Tool “create_binance_deposit” rewrote its description, which is the text the model reads security
- Tool “create_usdt_deposit” rewrote its description, which is the text the model reads security
- Tool “daily_checkin” rewrote its description, which is the text the model reads security
- Tool “deep_inspect” rewrote its description, which is the text the model reads security
- Tool “gamefi_status” rewrote its description, which is the text the model reads security
- Tool “get_2fa” rewrote its description, which is the text the model reads security
- Tool “get_mail_code” rewrote its description, which is the text the model reads security
- Tool “get_my_balance” rewrote its description, which is the text the model reads security
- Tool “get_product” rewrote its description, which is the text the model reads security
- Tool “how_to_start” rewrote its description, which is the text the model reads security
- Tool “latest_products” rewrote its description, which is the text the model reads security
- Tool “list_categories” rewrote its description, which is the text the model reads security
- Tool “list_category_products” rewrote its description, which is the text the model reads security
- Tool “list_orders” rewrote its description, which is the text the model reads security
- Tool “list_quests” rewrote its description, which is the text the model reads security
- Tool “quote_order” rewrote its description, which is the text the model reads security
- Tool “recommend_products” rewrote its description, which is the text the model reads security
- Tool “search_products” rewrote its description, which is the text the model reads security
- Tool “similar_products” rewrote its description, which is the text the model reads security
- Tool “spin_wheel” rewrote its description, which is the text the model reads security
- Tool “submit_complaint” rewrote its description, which is the text the model reads security
- Tool “topup_guide” rewrote its description, which is the text the model reads security
- Tool “verify_binance_deposit” rewrote its description, which is the text the model reads security
- Tool “verify_usdt_deposit” rewrote its description, which is the text the model reads security
- Tool “wallet_history” rewrote its description, which is the text the model reads security
- Schema quality: 150 → 220 ▼ functional
- “check_order_status” added an optional parameter “refresh” cosmetic
- 10 Sept 26 0
- Schema quality: 2859 → 4963 ▼ functional
- New tool “claim_quest” functional
- New tool “create_binance_deposit” functional
- New tool “create_usdt_deposit” functional
- New tool “daily_checkin” functional
- New tool “gamefi_status” functional
- New tool “get_mail_code” functional
- New tool “list_orders” functional
- New tool “list_quests” functional
- New tool “reload_order” functional
- New tool “spin_wheel” functional
- New tool “submit_complaint” functional
- New tool “verify_binance_deposit” functional
- New tool “verify_usdt_deposit” functional
- New tool “wallet_history” functional
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://hotlikeshop.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hotlikeshop.com | CN=WE1,O=Google Trust Services,C=US | 18 Aug 2026 | 16 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | c59e455620953fe7134af4ba536ff271 |
| SANs: hotlikeshop.com, *.hotlikeshop.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of hotlikeshop.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| hotlikeshop.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hotlikeshop.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://hotlikeshop.com/api/mcp | HTTPS enforced | 301 | https://hotlikeshop.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
best_sellers ~210
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 (from list_categories) or a keyword. Danh sách sản phẩm BÁN CHẠY còn hàng (đã bán nhiều nhất trước); chỉ trả field công khai (giá VND + số đã bán).
| Name | Type | Req | Description |
|---|---|---|---|
| category_id | integer | – | Limit to a category id (optional). Giới hạn theo danh mục (tùy chọn). |
| keyword | string | – | Keyword in product name (optional). Từ khóa trong tên SP (tùy chọn). |
| limit | integer | – | Max results (default 10, max 20). |
No output schema declared.
No examples provided.
buy_product ~210
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. AFTERWARDS: check_order_status for delivery (set refresh=true if it looks stuck), get_mail_code for OTP, submit_complaint if faulty. Bước 2: đặt mua thật bằng confirm_token (TRỪ TIỀN THẬT & giao hàng); chỉ gọi sau khi người dùng đã đồng ý giá đã báo.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Your shop account API key (must match the one used in quote_order). |
| confirm_token | string | yes | The confirm_token returned by quote_order (valid ~5 minutes, single use). |
No output schema declared.
No examples provided.
check_health_bulk ~340
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 platform. PREFER INSTEAD: check_live_facebook for a single Facebook UID, deep_inspect for one detailed profile. Kiểm tra sống/chết HÀNG LOẠT (tối đa 20/lần): UID Facebook hoặc username IG/TG/TikTok; mục IG/FB không check được bị đưa vào "skipped" — truyền "proxy" riêng để check chuẩn.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | List of UIDs (Facebook) or usernames (IG/TG/TikTok). Danh sách UID/username (tối đa 20). Cũng chấp nhận 1 chuỗi ngăn cách bởi dấu phẩy/xuống dòng. |
| platform | string | – | Platform to check. Nền tảng cần kiểm tra (mặc định facebook). |
| proxy | string | – | Optional (recommended for IG/FB): YOUR own proxy, this request only, never shared. http(s)://user:pass@host:port or socks5://host:port. Tùy chọn (nên có cho IG/FB): proxy CỦA BẠN, chỉ request này. |
No output schema declared.
No examples provided.
check_live_facebook ~264
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/Telegram/TikTok, deep_inspect for a detailed profile (followers, bio, media). Kiểm tra 1 UID Facebook (số) sống/chết; FB chặn IP máy chủ nên nếu không check được sẽ trả "needs_proxy" — truyền "proxy" riêng để check chuẩn.
| Name | Type | Req | Description |
|---|---|---|---|
| proxy | string | – | Optional: YOUR own proxy for this request only (never shared). Format: http(s)://user:pass@host:port or socks5://host:port. Tùy chọn: proxy CỦA BẠN, chỉ áp cho request này (không chia sẻ). Dạng http(… |
| uid | string | yes | Facebook numeric UID. UID Facebook (chỉ gồm chữ số). |
No output schema declared.
No examples provided.
check_order_status ~284
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 after ~5-10s. PREREQUISITE: an order_code (from buy_product or list_orders). WHEN TO USE: the user wants the current state or the delivered data of a specific order; set refresh=true only to nudge a stuck order. PREFER INSTEAD: list_orders to find the order_code first, get_mail_code for the email OTP, submit_complaint if the delivered item is faulty. Kiểm tra trạng thái & nội dung đã giao của 1 đơn theo order_code (cần api_key); truyền refresh=true để ép giao lại nếu đơn treo — không tính phí.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Your shop account API key. |
| order_code | string | yes | The order code returned by buy_product. |
| refresh | boolean | – | Set true to re-trigger delivery when the order looks stuck/undelivered (async; safe, never charges). Default false = plain read-only status check. |
No output schema declared.
No examples provided.
claim_quest ~190
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 quest_key is claimable, daily_checkin / spin_wheel for those specific rewards. Requires api_key. Nhận thưởng 1 nhiệm vụ đã hoàn thành (dùng quest_key từ list_quests).
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Your shop account API key. |
| quest_key | string | yes | The quest key to claim (from list_quests), e.g. daily_checkin, daily_buy1, weekly_spend50k. |
No output schema declared.
No examples provided.
compare_products ~188
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 comparable items, search_products / list_category_products to find ids. So sánh 2–5 sản phẩm cạnh nhau để khách chốt nhanh; chỉ field công khai (giá VND).
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | yes | Danh sách 2–5 product id cần so sánh, vd [943, 1004]. Cũng chấp nhận chuỗi "943,1004". |
No output schema declared.
No examples provided.
create_binance_deposit ~196
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. PREFER INSTEAD: create_usdt_deposit for on-chain USDT transfers. Tạo đơn nạp Binance Pay — hệ thống trả Pay ID nhận tiền + số USDT kèm số lẻ; chuyển lại NGUYÊN VĂN.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_usd | number | yes | Whole-number USD amount to deposit (the system assigns a unique cents suffix). |
| api_key | string | yes | Your shop account API key. |
No output schema declared.
No examples provided.
create_usdt_deposit ~290
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-chain USDT. AFTERWARDS: once they send, call verify_usdt_deposit with order_code + claim_token. PREFER INSTEAD: create_binance_deposit for users paying inside the Binance app. Tạo đơn nạp USDT — hệ thống tự sinh ĐỊA CHỈ VÍ và SỐ TIỀN kèm số lẻ độc nhất; chuyển lại NGUYÊN VĂN, KHÔNG tự chế/sửa ví.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_usd | number | yes | Whole-number USD amount to deposit (decimals are ignored — the system assigns a unique cents suffix). |
| api_key | string | yes | Your shop account API key. |
| network | string | – | USDT network: trc20 | bep20 | polygon | arbitrum | base (default trc20). Only networks with a configured wallet work — check topup_guide. |
No output schema declared.
No examples provided.
daily_checkin ~166
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: gamefi_status to first see if it is available, spin_wheel to use the earned spin, claim_quest for quest rewards. Requires api_key. Điểm danh hằng ngày nhận thưởng (mỗi ngày 1 lần).
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Your shop account API key. |
No output schema declared.
No examples provided.
deep_inspect ~313
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 one profile. PREFER INSTEAD: check_health_bulk to sweep many accounts for live/dead only, check_live_facebook for a quick single-UID liveness check. Xem SÂU 1 tài khoản MXH (chỉ đọc công khai); IG/FB chặn IP máy chủ → nếu không xem được trả "needs_proxy", truyền "proxy" riêng để xem chuẩn.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | Username/handle (IG/TG/TikTok) or numeric UID (Facebook). Also accepts a full profile URL. Username hoặc UID (FB); chấp nhận cả link profile. |
| platform | string | yes | Platform. Nền tảng cần xem. |
| proxy | string | – | Optional (recommended for IG/FB): YOUR own proxy, this request only, never shared. http(s)://user:pass@host:port or socks5://host:port. Tùy chọn (nên có cho IG/FB): proxy CỦA BẠN, chỉ request này. |
No output schema declared.
No examples provided.
gamefi_status ~184
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: all rewards credit the SHOPPING balance (spendable in-shop, NOT withdrawable). Requires api_key. Tổng quan phần thưởng miễn phí: điểm danh, vòng quay, nhiệm vụ có thể nhận (thưởng vào số dư mua hàng, không rút được).
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Your shop account API key. |
| lang | string | – | Language for labels: "vi" or "en" (default en). |
No output schema declared.
No examples provided.
get_2fa ~177
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-bundled order. Requires a valid Base32 secret. Sinh mã 2FA/TOTP hiện tại (6 số) từ khóa bí mật Base32; tính cục bộ, không lưu, không gửi đi đâu.
| Name | Type | Req | Description |
|---|---|---|---|
| secret | string | yes | Base32 secret key (spaces allowed). Khóa bí mật Base32 (cho phép có dấu cách). |
No output schema declared.
No examples provided.
get_mail_code ~192
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 authenticator (TOTP) codes, check_order_status to see the delivered credentials themselves. Lấy mã OTP/xác minh mới nhất cho đơn tài khoản có kèm mail (Hotmail/Outlook qua refresh_token, mail.tm qua email+mật khẩu); cần api_key + order_code.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Your shop account API key. |
| order_code | string | yes | The order code of the mail-bundled account order. |
No output schema declared.
No examples provided.
get_my_balance ~152
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ạng tài khoản (cần api_key); trả balance (VND), level, discount.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Your shop account API key. Khóa API tài khoản shop của bạn (Trang cá nhân → API). |
No output schema declared.
No examples provided.
get_product ~157
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 alternatives. Requires a known product id (not a name). Not for buying — pass the id to quote_order. Xem chi tiết 1 sản phẩm công khai theo id (kèm mô tả); chỉ đọc, không cần api_key.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Product id. |
No output schema declared.
No examples provided.
how_to_start ~197
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 specifics, quote_order + buy_product to actually purchase, search_products to browse. Pass lang="en" (default) or lang="vi". Hướng dẫn bắt đầu cho người mới: tạo tài khoản -> lấy api_key -> nạp tiền -> tìm & mua.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Optional: "en" (default) or "vi". Ngôn ngữ hướng dẫn: "en" (mặc định) hoặc "vi". |
No output schema declared.
No examples provided.
latest_products ~196
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 keyword. Danh sách sản phẩm MỚI còn hàng (thêm gần đây nhất trước); chỉ trả field công khai (giá VND).
| Name | Type | Req | Description |
|---|---|---|---|
| category_id | integer | – | Limit to a category id (optional). Giới hạn theo danh mục (tùy chọn). |
| keyword | string | – | Keyword in product name (optional). Từ khóa trong tên SP (tùy chọn). |
| limit | integer | – | Max results (default 10, max 20). |
No output schema declared.
No examples provided.
list_categories ~123
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 onboarding. This only lists categories — it does not return individual products. Liệt kê danh mục công khai kèm số sản phẩm; dùng để lấy category_id.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_category_products ~157
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, latest_products for newest. Not for buying — pass a chosen id to quote_order. Liệt kê sản phẩm công khai trong 1 danh mục theo category_id.
| Name | Type | Req | Description |
|---|---|---|---|
| category_id | integer | yes | Category id. |
| limit | integer | – | Max results (default 30, max 100). |
No output schema declared.
No examples provided.
list_orders ~201
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_history for money movements (top-ups/refunds), not order details. Liệt kê lịch sử đơn (order_code, sản phẩm, số lượng, tổng tiền, trạng thái, ngày) — cần api_key; dùng để tìm order_code rồi gọi check_order_status / get_mail_code.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Your shop account API key. |
| limit | integer | – | Orders per page (default 20, max 100). |
| page | integer | – | Page number (default 1). |
No output schema declared.
No examples provided.
list_quests ~162
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 (check-in + wheel + quests). Requires api_key. Danh sách nhiệm vụ ngày/tuần kèm tiến độ + phần thưởng.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Your shop account API key. |
| lang | string | – | Language for titles: "vi" or "en" (default en). |
No output schema declared.
No examples provided.
quote_order ~205
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, check_order_status for an order that already exists (not for pricing a new one). Bước 1 khi mua: báo giá TRƯỚC khi mua, trả confirm_token; KHÔNG trừ tiền. Luôn hỏi người dùng xác nhận rồi mới gọi buy_product.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Your shop account API key. |
| product_id | integer | yes | Product id (from search_products / get_product). |
| quantity | integer | – | Quantity to buy (default 1). |
No output schema declared.
No examples provided.
recommend_products ~258
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_products to see a whole category. Optionally scope with category_id from list_categories. Gợi ý sản phẩm CÒN HÀNG theo ngân sách và/hoặc từ khóa/danh mục (rẻ trước) kèm gợi ý combo; chỉ trả field công khai (giá VND).
| Name | Type | Req | Description |
|---|---|---|---|
| budget | integer | – | Max unit price in VND (optional). Ngân sách/giá tối đa mỗi SP (VND, tùy chọn). |
| category_id | integer | – | Limit to a category id (optional). Giới hạn theo danh mục (tùy chọn). |
| keyword | string | – | Keyword in product name (optional). Từ khóa trong tên SP (tùy chọn). |
| limit | integer | – | Max results (default 8, max 20). |
No output schema declared.
No examples provided.
search_products ~159
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 for buying — pass a found id to quote_order. Tìm sản phẩm công khai theo tên; chỉ đọc, không cần api_key.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (default 20, max 50). |
| query | string | yes | Keyword / từ khóa (product name). |
No output schema declared.
No examples provided.
similar_products ~192
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_products for keyword search, recommend_products for budget-based picks, list_category_products to browse the whole category. Cho 1 product id, trả các SP TƯƠNG TỰ còn hàng (cùng danh mục, ưu tiên bán chạy; bù SP mới khác danh mục nếu ít).
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Product id gốc để tìm SP tương tự, vd 943. |
| limit | integer | – | Max results (default 8, max 20). |
No output schema declared.
No examples provided.
spin_wheel ~151
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. Winnings credit the SHOPPING balance (not withdrawable). Requires api_key. Quay vòng quay may mắn 1 lượt (cần còn lượt quay).
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Your shop account API key. |
No output schema declared.
No examples provided.
submit_complaint ~296
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 / login-fails / short quantity. PREFER INSTEAD: check_order_status with refresh=true first if it merely looks stuck (undelivered), then check_order_status to track the case afterwards. Gửi khiếu nại/bảo hành-hoàn tiền cho 1 đơn (cần api_key); shop xử lý ≤3 ngày, quá hạn TỰ ĐỘNG HOÀN; mỗi đơn chỉ khiếu nại 1 lần; theo dõi bằng check_order_status.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Your shop account API key. |
| description | string | – | Optional details describing the problem (which items failed, error message, etc.). |
| order_code | string | yes | The order code you want to complain about (must belong to your account). |
| reason | string | yes | Short reason for the complaint, e.g. "Sai sản phẩm", "Không đăng nhập được", "Die/khóa", "Thiếu số lượng", "Khác". |
No output schema declared.
No examples provided.
topup_guide ~282
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 full new-user onboarding, get_my_balance if you only need the balance number. Pass lang="en" for an English guide. Hướng dẫn nạp tiền (chỉ thông tin, KHÔNG thanh toán); truyền api_key để kèm số dư & phần còn thiếu, kèm quy đổi USD.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | integer | – | Optional: amount you want to spend (VND) to compute shortfall. Tùy chọn: số tiền cần (VND) để tính phần còn thiếu. |
| api_key | string | – | Optional: your shop api_key to also show current balance & shortfall (with USD conversion). Tùy chọn: api_key để hiện số dư & phần còn thiếu. |
| lang | string | – | Optional: "en" for English guide, otherwise Vietnamese. Tùy chọn: "en" để nhận hướng dẫn tiếng Anh. |
No output schema declared.
No examples provided.
verify_binance_deposit ~181
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_deposit for on-chain USDT deposits, get_my_balance/wallet_history to inspect balance afterwards. Kiểm tra & xác nhận đơn nạp Binance Pay — khớp thì cộng tiền (an toàn khi gọi lại nhiều lần).
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Your shop account API key. |
| merchant_trade_no | string | yes | merchant_trade_no from create_binance_deposit. |
No output schema declared.
No examples provided.
verify_usdt_deposit ~259
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 specific transaction. PREFER INSTEAD: verify_binance_deposit for Binance Pay deposits, get_my_balance/wallet_history to inspect balance afterwards. Kiểm tra & xác nhận đơn nạp USDT — quét blockchain, khớp thì cộng tiền (an toàn khi gọi lại nhiều lần).
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Your shop account API key. |
| claim_token | string | yes | claim_token from create_usdt_deposit (single-order secret). |
| method | string | – | Verification mode: "amount" (default, auto-scan by unique amount) or "hash". |
| order_code | string | yes | order_code from create_usdt_deposit. |
| tx_hash | string | – | Transaction hash (only when method="hash"). |
No output schema declared.
No examples provided.
wallet_history ~188
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: get_my_balance for just the current number, list_orders for purchase/order details rather than money entries. Requires api_key. Xem lịch sử biến động số dư (nạp/tiêu/hoàn) kèm số dư sau mỗi giao dịch.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Your shop account API key. |
| page | integer | – | Page number (default 1, 20 rows per page). |
No output schema declared.
No examples provided.
What is the HOTLIKESHOP MCP server?
HOTLIKESHOP is an MCP server listed in the public MCP registry as io.github.tuanone123/hotlikeshop-mcp. Search & buy MMO/social accounts, proxies & digital services from HOTLIKESHOP in your AI chat. This page covers its hosted endpoint (https://hotlikeshop.com/api/mcp).
Is the HOTLIKESHOP MCP server safe to use?
HOTLIKESHOP scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the HOTLIKESHOP MCP server expose?
HOTLIKESHOP exposes 32 tools: search_products, get_product, list_categories, list_category_products, get_2fa, and 27 more. Their descriptions and schemas cost roughly 6,720 tokens of context every time the server is loaded.
Does the HOTLIKESHOP MCP server require authentication?
No. We connected to HOTLIKESHOP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the HOTLIKESHOP MCP server still maintained?
HOTLIKESHOP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.