io.github.vola-trebla/ndjson-local-log-triage-mcp

MCPcommunity
v0.2.0io.github.vola-treblaUnknownUpdated 1mo agonpmGitHub

Streams NDJSON log triage: query patterns, detect anomalies, summarize timelines without full load.

Your service just crashed. The log file is 2GB. Your AI agent can't help. MCP server that stream-parses NDJSON log files without loading them into memory — filter by pattern, detect error spikes via Z-score analysis, summarize severity timelines by time window. A service crashes at 3am. The log file is and it's 2GB. You ask your agent to find what caused the spike in errors around 03:17. The…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1mo agoLast update
Package
Authorio.github.vola-trebla
LicenseUnknown
Version0.2.0
Sourcemcp-registry
npmndjson-local-log-triage-mcp
GitHubvola-trebla/ndjson-local-log-triage-mcp
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/25
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/10
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
—npm provenance (Sigstore)+0/5
→ Publish from GitHub Actions with the --provenance flag
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface4 tools · none privileged
Security scan✓ Cleanv0.2.0 · 20d ago
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Your service just crashed. The log file is 2GB. Your AI agent can't help. MCP server that stream-parses NDJSON log files without loading them into memory — filter by pattern, detect error spikes via Z-score analysis, summarize severity timelines by time window. A service crashes at 3am. The log file is and it's 2GB. You ask your agent to find what caused the spike in errors around 03:17. The agent can't read 2GB. It can't even try. streams the file line by line — never loading it into memory —…

Keywords
mcp