forget — Abuseipdb MCP Tool
forget
(forget) is one of 39 tools on the
Abuseipdb
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call forget from your client
- Claude Code Abuseipdb forget run in your project directory
- Claude Desktop Abuseipdb forget ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Abuseipdb forget ~/.cursor/mcp.json
- VS Code Abuseipdb forget .vscode/mcp.json
- Zed Abuseipdb forget ~/.config/zed/settings.json
- Windsurf Abuseipdb forget ~/.codeium/windsurf/mcp_config.json
- Cline Abuseipdb forget ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Abuseipdb forget ~/.gemini/settings.json
- Grok Abuseipdb forget .mcp.json (in your project root)
- ChatGPT Abuseipdb forget Settings → Connectors → Advanced → Developer mode
- Claude.ai Abuseipdb forget Settings → Connectors → Add custom connector
- LangChain Abuseipdb forget pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http abuseipdb https://gateway.pipeworx.io/abuseipdb/mcp
Other tools on this server
- ask_pipeworx
- ask_pipeworx_beta
- ask_pipeworx_grounded
- search_within
- deep_research
- discover_tools
- resolve_entity
- compare_entities
- subscribe
- unsubscribe
- list_subscriptions
- recent_alerts
- entity_profile
- recent_changes
- validate_claim
- company_facts
- scan_dependency
- bet_research
- polymarket_arbitrage
- polymarket_edges
- polymarket_kalshi_spread
- polymarket_fill_risk
- polymarket_edge_tracker
- kalshi_weather_edge
- resolution_audit
- resolution_diff
- release_calendar_markets
- pipeworx_trending
- suggest_questions
- generate_llms_txt
- ai_visibility_check
- scan_competitor_ai_presence
- pipeworx_feedback
- remember
- recall
- check_ip
- report_ip
- get_blacklist
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.