LeashIndex Get the report

Index / messaging

HOTLIKESHOP

io-github-tuanone123-hotlikeshop-mcp declares 32 capabilities across 32 tools, with 3 critical issues.

71/100 exposureHigh exposure

Manifest recorded 2026-10-11 from tools/list on https://hotlikeshop.com/api/mcp, published in the official MCP registry as io.github.tuanone123/hotlikeshop-mcp 1.0.0. The date changes only when the manifest does. Not verified by a maintainer.

Issues

These describe what this server's manifest declares. A product can provide controls that MCP has no way to express — token revocation, an admin console, audit logs — and this page cannot see them. The absence of a declaration is not evidence that a control is absent.

critical · no-revocation · All 32 tools

32 of 32 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.

critical · irreversible-uncapped · 1 of 32 tools

1 tool is classified as irreversible and declares no limit.

critical · uncapped-spend · 1 of 32 tools

1 tool is classified as moving money and declares no dollar limit. A cap on the number of payments does not bound their amount.

high · no-expiry · All 32 tools

32 of 32 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.

high · no-audit-trail · All 32 tools

32 of 32 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.

high · uncapped-write · 9 of 32 tools

9 tools can modify data and declare no limit.

low · uncapped-read · 22 of 32 tools

22 tools can read data and declare no limit.

Declared capabilities

How each tool was read. declared means the server's own annotation said so — self-reported and unverified. inferred is from the tool's name. assumed means nothing indicated either way.

ToolRead asBasis
search_productsread inferred
get_productread inferred
list_categoriesread inferred
list_category_productsread inferred
get_2faread inferred
check_live_facebookread inferred
check_health_bulkread inferred
deep_inspectread inferred
recommend_productswrite assumed
topup_guideread inferred
how_to_startread inferred
best_sellersread inferred
latest_productsread inferred
compare_productsread inferred
similar_productswrite assumed
get_my_balanceread inferred
quote_orderwrite assumed
buy_productpay inferred
check_order_statusread inferred
submit_complaintwrite inferred
list_ordersread inferred
get_mail_coderead inferred
create_usdt_depositwrite inferred
verify_usdt_depositread inferred
create_binance_depositwrite inferred
verify_binance_depositread inferred
wallet_historyread inferred
gamefi_statusread inferred
daily_checkinwrite assumed
spin_wheelwrite assumed
list_questsread inferred
claim_questwrite assumed
Answering this question about your own agent? The self-serve stack report applies the same reading to your own stack or server and gives you a dated document you can hand to a customer's security review. It is generated in your browser, with nobody to wait for. Buying one does not change this page, its score or its place in the index — see Independence.
Maintain this server? If this page misreads your manifest, or your server has changed, submit its current tools/list response and it will be re-scored and dated. Corrections are published alongside the original, not in place of it.