io.github.vola-trebla/ndjson-local-log-triage-mcp
NPM · NDJSON-LOCAL-LOG-TRIAGE-MCP
Streams NDJSON log triage: query patterns, detect anomalies, summarize timelines without full load.
Available components
Last scanned (7 hours ago)
Scores higher than 81% of npm servers
Category Monitoring and Observability
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
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 168 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 522 tokens (~130/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 −1
- Stability: pass → 0.90 functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Stability: pass → 0.97 functional
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.83 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Analysed npm/ndjson-local-log-triage-mcp@0.2.0
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 | 30 |
| 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 →
correlate_request ~129
Reconstruct a distributed trace by collecting all log events matching a trace/request ID across multiple NDJSON files, sorted chronologically.
| Name | Type | Req | Description |
|---|---|---|---|
| idField | string | – | Field name containing the trace/request ID |
| lineStartPattern | string | – | Regex that marks new log line start — enables multiline stack trace buffering |
| logFiles | array | yes | Array of absolute paths to NDJSON log files |
| serviceField | string | – | Field name for service/component name |
| timestampField | string | – | Field name for ISO timestamp |
| traceId | string | yes | Trace/request ID value to search for |
No output schema declared.
No examples provided.
detect_error_anomalies ~135
Z-score frequency analysis to find sudden error spikes by time window.
| Name | Type | Req | Description |
|---|---|---|---|
| errorValues | array | – | Level values to treat as errors |
| levelField | string | – | Field containing log level |
| lineStartPattern | string | – | Regex that marks new log line start — enables multiline stack trace buffering |
| logFile | string | yes | Absolute path to the NDJSON log file |
| timestampField | string | – | Field containing ISO timestamp |
| windowMinutes | integer | – | Aggregation window size in minutes |
| zScoreThreshold | number | – | Z-score threshold above which a window is flagged as anomalous |
No output schema declared.
No examples provided.
query_log_pattern ~118
Filter NDJSON log file by field/value pattern, return top N matching entries.
| Name | Type | Req | Description |
|---|---|---|---|
| field | string | yes | JSON field name to filter on (e.g. 'level', 'service') |
| limit | integer | – | Max entries to return |
| lineStartPattern | string | – | Regex that marks new log line start (e.g. "^{") — enables multiline stack trace reconstruction |
| logFile | string | yes | Absolute path to the NDJSON log file |
| value | string | yes | Value to match (case-insensitive substring) |
No output schema declared.
No examples provided.
summarize_log_timeline ~140
Chronological severity aggregation — errors, warnings, and info counts per time window.
| Name | Type | Req | Description |
|---|---|---|---|
| adaptive | boolean | – | Auto-scale bucket size to actual event density — samples first 1000 events to choose ms/s/min granularity and zooms in on the peak error window |
| levelField | string | – | Field containing log level |
| lineStartPattern | string | – | Regex that marks new log line start — enables multiline stack trace buffering |
| logFile | string | yes | Absolute path to the NDJSON log file |
| timestampField | string | – | Field containing ISO timestamp |
| windowMinutes | integer | – | Aggregation window size in minutes |
No output schema declared.
No examples provided.
How do I install the io.github.vola-trebla/ndjson-local-log-triage-mcp server?
io.github.vola-trebla/ndjson-local-log-triage-mcp runs locally as an npm package, launched with npx -y ndjson-local-log-triage-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · ndjson-local-log-triage-mcp
claude mcp add vola-trebla-ndjson-local-log-triage-mcp -- npx -y ndjson-local-log-triage-mcp
What is the io.github.vola-trebla/ndjson-local-log-triage-mcp server?
io.github.vola-trebla/ndjson-local-log-triage-mcp is listed in the public MCP registry as io.github.vola-trebla/ndjson-local-log-triage-mcp. Streams NDJSON log triage: query patterns, detect anomalies, summarize timelines without full load. This page covers its npm package (ndjson-local-log-triage-mcp).
Is the io.github.vola-trebla/ndjson-local-log-triage-mcp server safe to use?
io.github.vola-trebla/ndjson-local-log-triage-mcp scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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.vola-trebla/ndjson-local-log-triage-mcp server expose?
io.github.vola-trebla/ndjson-local-log-triage-mcp exposes 4 tools: query_log_pattern, detect_error_anomalies, summarize_log_timeline, correlate_request. Their descriptions and schemas cost roughly 522 tokens of context every time the server is loaded.
Is the io.github.vola-trebla/ndjson-local-log-triage-mcp server still maintained?
io.github.vola-trebla/ndjson-local-log-triage-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 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.vola-trebla/ndjson-local-log-triage-mcp server under?
io.github.vola-trebla/ndjson-local-log-triage-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.