io.github.RobelDev/logclaw-mcp-server
NPM · LOGCLAW-MCP-SERVER · SCANNED SEP 29
Connect AI coding tools to LogClaw incidents, logs, and anomaly detections.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 201 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 467 tokens (~77/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.RobelDev/logclaw-mcp-server server?
io.github.RobelDev/logclaw-mcp-server runs locally as an npm package, launched with npx -y logclaw-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · logclaw-mcp-server
claude mcp add robeldev-logclaw-mcp-server -- npx -y logclaw-mcp-server
{
"mcpServers": {
"robeldev-logclaw-mcp-server": {
"command": "npx",
"args": [
"-y",
"logclaw-mcp-server"
]
}
}
} {
"servers": {
"robeldev-logclaw-mcp-server": {
"command": "npx",
"args": [
"-y",
"logclaw-mcp-server"
]
}
}
} codex mcp add robeldev-logclaw-mcp-server -- npx -y logclaw-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"robeldev-logclaw-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"logclaw-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add robeldev-logclaw-mcp-server --command npx --arg -y --arg logclaw-mcp-server
mcp_servers:
robeldev-logclaw-mcp-server:
command: "npx"
args: ["-y", "logclaw-mcp-server"] {
"McpServers": {
"robeldev-logclaw-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"logclaw-mcp-server"
]
}
}
} assistant mcp add robeldev-logclaw-mcp-server -t stdio -c npx -a -y logclaw-mcp-server
{
"mcpServers": {
"robeldev-logclaw-mcp-server": {
"command": "npx",
"args": [
"-y",
"logclaw-mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 29 Sept 26 +1
- Stability: 0.97 → pass security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 −3
- Stability: pass → 0.80 functional
- 22 Sept 26 +1
- Stability: 0.97 → pass security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
- Security disclosure: unverified → pass ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 29 Sept 2026 · Analysed npm/logclaw-mcp-server@1.0.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
logclaw_get_anomalies ~82
Get recent anomaly detections. Anomalies are auto-detected using Z-score analysis on error rates. Returns score, detection mode, service.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default: 20, max: 100) |
| service | string | – | Filter by service name |
| severity | string | – | Filter by severity |
No output schema declared.
No examples provided.
logclaw_get_incident ~57
Get full incident details including root cause, causal chain, evidence logs, traces, timeline, blast radius, and suggested fix.
| Name | Type | Req | Description |
|---|---|---|---|
| incident_id | string | yes | Incident ID (e.g. "TICK-0037") |
No output schema declared.
No examples provided.
logclaw_list_incidents ~103
List and filter LogClaw incidents. Returns summaries with ID, title, severity, state, service, timestamps.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default: 20, max: 100) |
| search | string | – | Full-text search across title, service, description |
| service | string | – | Filter by service name |
| severity | string | – | Filter by severity level |
| state | string | – | Filter by incident state |
No output schema declared.
No examples provided.
logclaw_search_logs ~117
Search raw logs in LogClaw. Filter by service, level, time range, and query. Returns entries with timestamp, service, level, message, trace_id.
| Name | Type | Req | Description |
|---|---|---|---|
| level | string | – | Filter by log level |
| limit | number | – | Max results (default: 50, max: 200) |
| minutes_ago | number | – | Look back N minutes (default: 60) |
| query | string | – | Full-text search across log messages |
| service | string | – | Filter by service name |
No output schema declared.
No examples provided.
logclaw_service_health ~33
Check the health status of LogClaw pipeline services (ticketing agent, etc). Returns status and latency.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
logclaw_update_incident ~75
Transition an incident state (acknowledge, investigate, mitigate, resolve) or add a timeline note.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | State transition action |
| incident_id | string | yes | Incident ID (e.g. "TICK-0037") |
| note | string | – | Optional note for the timeline |
No output schema declared.
No examples provided.
What is the io.github.RobelDev/logclaw-mcp-server server?
io.github.RobelDev/logclaw-mcp-server is listed in the public MCP registry as io.github.RobelDev/logclaw-mcp-server. Connect AI coding tools to LogClaw incidents, logs, and anomaly detections. This page covers its npm package (logclaw-mcp-server).
Is the io.github.RobelDev/logclaw-mcp-server server safe to use?
io.github.RobelDev/logclaw-mcp-server scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 29 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.RobelDev/logclaw-mcp-server server expose?
io.github.RobelDev/logclaw-mcp-server exposes 6 tools: logclaw_list_incidents, logclaw_get_incident, logclaw_update_incident, logclaw_search_logs, logclaw_get_anomalies, logclaw_service_health. Their descriptions and schemas cost roughly 467 tokens of context every time the server is loaded.
Is the io.github.RobelDev/logclaw-mcp-server server still maintained?
io.github.RobelDev/logclaw-mcp-server is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.RobelDev/logclaw-mcp-server server under?
io.github.RobelDev/logclaw-mcp-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.