incidents_list — threatcrush MCP Tool
incidents_list
(incidents list) is one of 20 tools on the
threatcrush
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call incidents_list from your client
- Claude Code threatcrush incidents_list run in your project directory
- Claude Desktop threatcrush incidents_list ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor threatcrush incidents_list ~/.cursor/mcp.json
- VS Code threatcrush incidents_list .vscode/mcp.json
- Zed threatcrush incidents_list ~/.config/zed/settings.json
- Windsurf threatcrush incidents_list ~/.codeium/windsurf/mcp_config.json
- Cline threatcrush incidents_list ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI threatcrush incidents_list ~/.gemini/settings.json
- Grok threatcrush incidents_list .mcp.json (in your project root)
- ChatGPT threatcrush incidents_list Settings → Connectors → Advanced → Developer mode
- Claude.ai threatcrush incidents_list Settings → Connectors → Add custom connector
- LangChain threatcrush incidents_list pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http threatcrush https://threatcrush.com/api/mcpOther tools on this server
- av_hash_lookup
- reputation_lookup
- reputation_bulk
- redeem_credit_code
- list_invites
- create_invite
- findings_list
- findings_get
- findings_triage
- incidents_get
- incidents_update
- incidents_raise
- webhooks_list
- webhooks_create
- webhooks_update
- webhooks_delete
- webhooks_test
- webhooks_rotate_secret
- webhooks_deliveries
This list was read from the server itself, by connecting to it and calling tools/list on 11 November 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.