LeashIndex Get the report

Index / data

io.github.gosadu/loophole-tape

io-github-gosadu-loophole-tape declares 34 capabilities across 34 tools, with 3 critical issues.

75/100 exposureHigh exposure

Manifest recorded 2026-10-11 from tools/list on https://api.loopholetape.com/mcp, published in the official MCP registry as io.github.gosadu/loophole-tape 0.6.1. 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 34 tools

34 of 34 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 · 3 of 34 tools

3 tools are classified as irreversible and declare no limit.

critical · uncapped-spend · 3 of 34 tools

3 tools are classified as moving money and declare no dollar limit. A cap on the number of payments does not bound their amount.

high · no-expiry · All 34 tools

34 of 34 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 34 tools

34 of 34 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 · 1 of 34 tools

1 tool can modify data and declares no limit.

low · uncapped-read · 30 of 34 tools

30 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
token_checkread declared
catalogread declared
healthread declared
market_regimeread declared
sample_mintread declared
new_launches_freeread declared
check_coverageread declared
watchlist_updatesread declared
check_pumpfun_riskread declared
check_watchlist_riskread declared
verdictread declared
mint_risk_cardread declared
pumpfun_recent_launchesread declared
recent_rugsread declared
recent_graduationsread declared
creator_reputationread declared
wallet_profileread declared
rhc_regimeread declared
rhc_recent_launchesread declared
buy_api_keypay inferred
buy_datasetpay inferred
launches_sinceread declared
buy_trial_keypay inferred
rhc_curve_cardread declared
rhc_curve_tradesread declared
launches_screenedread declared
check_batch_riskread declared
mint_holdersread declared
mint_flowread declared
mint_outcomeread declared
mint_outcome_batchread declared
rhc_swap_build_checkedread declared
swap_build_checkedread declared
subscribe_alertswrite 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.