Claude.ai LogTriage scan_log_for_attacks
How to: Claude.ai LogTriage scan_log_for_attacks
Add LogTriage to Claude.ai
-
01
Open Settings → Connectors → Add custom connector and merge this in. Keep any servers already there.
https://api.logtriage.app/mcp-
02
Save the file and restart Claude.ai.
-
03
Ask for something scan_log_for_attacks does. Claude.ai lists the server's tools on connect and calls scan_log_for_attacks itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that LogTriage's identifier in your config matches the one above exactly.
Claude on the web takes a remote URL and completes OAuth in the browser. For a packaged server use Claude Desktop or Claude Code instead. Claude.ai docs
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 14 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.