check_coverage — loophole tape MCP Tool Read-only
check_coverage
(check coverage) 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 check_coverage from your client
- Claude Code loophole tape check_coverage run in your project directory
- Claude Desktop loophole tape check_coverage ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor loophole tape check_coverage ~/.cursor/mcp.json
- VS Code loophole tape check_coverage .vscode/mcp.json
- Zed loophole tape check_coverage ~/.config/zed/settings.json
- Windsurf loophole tape check_coverage ~/.codeium/windsurf/mcp_config.json
- Cline loophole tape check_coverage ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI loophole tape check_coverage ~/.gemini/settings.json
- Grok loophole tape check_coverage .mcp.json (in your project root)
- ChatGPT loophole tape check_coverage Settings → Connectors → Advanced → Developer mode
- Claude.ai loophole tape check_coverage Settings → Connectors → Add custom connector
- LangChain loophole tape check_coverage pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http loophole-tape https://api.loopholetape.com/mcpOther tools on this server
- catalog
- health
- market_regime
- sample_mint
- radar
- watchlist_updates
- 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.