Connect AI coding tools to LogClaw incidents, logs, and anomaly detections.
Connect your AI coding tools to LogClaw incidents, logs, and anomalies via the Model Context Protocol. Works with Claude Code, Cursor, Windsurf, and any MCP-compatible client. Variable | Required | Description | ----------|----------|-------------| | Yes | Your LogClaw project API key | | No | Auth proxy endpoint (default: ) | ------|-------------| | List and filter incidents by severity, state,…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
logclaw_list_incidentsNo description publishedThis tool published no description. Forge does not invent one.
logclaw_get_incidentNo description publishedThis tool published no description. Forge does not invent one.
logclaw_update_incidentNo description publishedThis tool published no description. Forge does not invent one.
logclaw_search_logsNo description publishedThis tool published no description. Forge does not invent one.
logclaw_get_anomaliesNo description publishedThis tool published no description. Forge does not invent one.
logclaw_service_healthNo description publishedThis tool published no description. Forge does not invent one.
logclaw_bulk_updateNo description publishedThis tool published no description. Forge does not invent one.
logclaw_export_incidentsNo description publishedThis tool published no description. Forge does not invent one.
0 of 8 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Connect your AI coding tools to LogClaw incidents, logs, and anomalies via the Model Context Protocol. Works with Claude Code, Cursor, Windsurf, and any MCP-compatible client. Variable | Required | Description | ----------|----------|-------------| | Yes | Your LogClaw project API key | | No | Auth proxy endpoint (default: ) | ------|-------------| | List and filter incidents by severity, state, service, or search query | | Get full incident details — root cause, causal chain, evidence logs,…
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This package was last scanned before Forge began storing the resolved tree. The next scan will record it.