npm:logclaw-mcp-server

Item: npm:logclaw-mcp-server
Rating: 75
Author: wmcp.sh

https://www.npmjs.com/package/logclaw-mcp-server

75/100 · MCP Trust Grade · checked 3h ago · MCP 1.0.6

What it offers — 8 tools · Database

logclaw_list_incidents

List and filter LogClaw incidents. Returns summaries with ID, title, severity, state, service, timestamps.

logclaw_get_incident

Get full incident details including root cause, causal chain, evidence logs, traces, timeline, blast radius, and suggested fix.

logclaw_update_incident

Transition an incident state (acknowledge, investigate, mitigate, resolve) or add a timeline note.

logclaw_search_logs

Search raw logs in LogClaw. Filter by service, level, time range, and query. Returns entries with timestamp, service, level, message, trace_id.

logclaw_get_anomalies

Get recent anomaly detections. Anomalies are auto-detected using Z-score analysis on error rates. Returns score, detection mode, service.

logclaw_service_health

Check the health status of LogClaw pipeline services (ticketing agent, etc). Returns status and latency.

logclaw_bulk_update

Update multiple incidents at once. Acknowledge, investigate, mitigate, or resolve several incidents in a single call.

logclaw_export_incidents

Export incidents in CSV, markdown table, or JSON format for easy copy-paste or sharing.

Spec / packaging20%100

✓ depends on an MCP SDK
✓ declares a bin entry (runnable server)
✓ 8 tool(s) detected in source

Security (OWASP MCP)30%25

⚠ references sensitive file paths / env secrets
scanned 5 source files

Maintenance / popularity20%100

published within 90 days
7 published versions

Tool hygiene15%95

✓ ships TypeScript types
2 runtime deps

Transparency / provenance15%90

✓ public repository linked
✓ MIT license
20 weekly downloads

Findings

WARNMCP08 References sensitive file paths / environment secrets.

INFO Static analysis of npm package logclaw-mcp-server@1.0.6 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.

Grade another server

We re-grade npm:logclaw-mcp-server on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — npm:logclaw-mcp-server grade C

Share on X Open card image

https://wmcp.sh/mcp/grade/npm%3Alogclaw-mcp-server

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

Markdown (for your README)

[![MCP Trust Grade C](https://wmcp.sh/mcp/grade/npm%3Alogclaw-mcp-server/badge.svg)](https://wmcp.sh/mcp/grade/npm%3Alogclaw-mcp-server)

HTML

<a href="https://wmcp.sh/mcp/grade/npm%3Alogclaw-mcp-server"><img src="https://wmcp.sh/mcp/grade/npm%3Alogclaw-mcp-server/badge.svg" alt="MCP Trust Grade C · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust

How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.