watchlist_updates — loophole tape MCP Tool
watchlist_updates
(watchlist updates) is one of 31 tools on the
loophole tape
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call watchlist_updates from your client
- Claude Code loophole tape watchlist_updates run in your project directory
- Claude Desktop loophole tape watchlist_updates ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor loophole tape watchlist_updates ~/.cursor/mcp.json
- VS Code loophole tape watchlist_updates .vscode/mcp.json
- Zed loophole tape watchlist_updates ~/.config/zed/settings.json
- Windsurf loophole tape watchlist_updates ~/.codeium/windsurf/mcp_config.json
- Cline loophole tape watchlist_updates ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI loophole tape watchlist_updates ~/.gemini/settings.json
- Grok loophole tape watchlist_updates .mcp.json (in your project root)
- ChatGPT loophole tape watchlist_updates Settings → Connectors → Advanced → Developer mode
- Claude.ai loophole tape watchlist_updates Settings → Connectors → Add custom connector
- LangChain loophole tape watchlist_updates pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http loophole-tape https://api.loopholetape.com/mcp
Other tools on this server
- catalog
- health
- market_regime
- sample_mint
- radar
- check_coverage
- check_pumpfun_risk
- check_watchlist_risk
- verdict
- mint_risk_card
- recent_launches
- recent_rugs
- recent_graduations
- creator_reputation
- wallet_profile
- rhc_regime
- rhc_recent_launches
- buy_api_key
- buy_dataset
- launches_since
- buy_trial_key
- rhc_curve_card
- rhc_curve_trades
- launches_screened
- check_batch_risk
- mint_holders
- mint_flow
- mint_outcome
- mint_outcome_batch
- subscribe_alerts
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.