MCP servers observed by Lowdown
io.github.gosadu/loophole-tape MCP server: daily status and tool changes
Answered initialize and tools/list on all 4 checks recorded in the last 30 days (2026-11-10 to 2026-11-19) (Lowdown checks this server every 3 days); 34 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; no tool definition change in 3 compared days; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.gosadu/loophole-tape
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.gosadu/loophole-tape?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-19: the server answered initialize and tools/list.
- Observed days in the last 30: 4
- Answered initialize and tools/list: 4
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 4 observed days. Lowdown checks without credentials.
Did its tools change recently?
No change in tool schemas, descriptions or names across 3 compared days.
What tools does it list?
34 tools on 2026-11-19:
buy_api_keybuy_datasetbuy_trial_keycatalogcheck_batch_riskcheck_coveragecheck_pumpfun_riskcheck_watchlist_riskcreator_reputationhealthlaunches_screenedlaunches_sincemarket_regimemint_flowmint_holdersmint_outcomemint_outcome_batchmint_risk_cardnew_launches_freepumpfun_recent_launchesrecent_graduationsrecent_rugsrhc_curve_cardrhc_curve_tradesrhc_recent_launchesrhc_regimerhc_swap_build_checkedsample_mintsubscribe_alertsswap_build_checkedtoken_checkverdictwallet_profilewatchlist_updates
MCP Registry declaration
- Registry name:
io.github.gosadu/loophole-tape - Declared version: 0.6.1
- Status: active
- Declared hosts:
api.loopholetape.com
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:io.github.gosadu/loophole-tape", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.gosadu/loophole-tape?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).