get_attack_evidence — Mitigant MCP Tool Read-only
get_attack_evidence
(get attack evidence) is one of 12 tools on the
Mitigant
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_attack_evidence from your client
- Claude Code Mitigant get_attack_evidence run in your project directory
- Claude Desktop Mitigant get_attack_evidence ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Mitigant get_attack_evidence ~/.cursor/mcp.json
- VS Code Mitigant get_attack_evidence .vscode/mcp.json
- Zed Mitigant get_attack_evidence ~/.config/zed/settings.json
- Windsurf Mitigant get_attack_evidence ~/.codeium/windsurf/mcp_config.json
- Cline Mitigant get_attack_evidence ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Mitigant get_attack_evidence ~/.gemini/settings.json
- Grok Mitigant get_attack_evidence .mcp.json (in your project root)
- ChatGPT Mitigant get_attack_evidence Settings → Connectors → Advanced → Developer mode
- Claude.ai Mitigant get_attack_evidence Settings → Connectors → Add custom connector
- LangChain Mitigant get_attack_evidence pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mitigant-mcp https://mcp.mitigant.io/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 5 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.