Jarroba Tools · Logs
NPM · @JARROBA/MCP-LOGS
Lets your AI read a CI log far too big for its context. 12 tools, takes a file path.
Available components
Last scanned (16 hours ago)
Scores higher than 95% 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 Security100
- 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
- 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Invarato/jarroba-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2402 tokens (~200/item across 12 items; 12 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 93% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 16 Nov 26 0
- Package version: 0.1.9 → 0.3.1 functional
- 15 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.3.0 → 0.3.1 functional
- 13 Nov 26 0
- Stability: 0.97 → pass security
- 12 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.
- 10 Nov 26 +6
- Source repository: unverified → pass ▲ security
- 9 Nov 26 −5
- Provenance: pass → unverified ▼ security
- 7 Nov 26 −2
- Stability: pass → 0.80 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 21 Nov 2026 · Analysed npm/@jarroba/mcp-logs@0.3.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Invarato/jarroba-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Invarato/jarroba-mcp/.github/workflows/publish.yml@refs/tags/v0.3.1 |
| Rekor log index | 3865451272 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:450592d57d40511c37aa19defbcb2aed19b4560e0b4ba82bc122c2829f73b16ebe17d7fe2d5edc4cabf31c28f9930e09953cb76e0a80afac1897024e0 |
Background: How many MCP packages publish verified provenance →
Dependencies 3 packages
| Packages resolved | 3 |
|---|---|
| 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 →
log_analyze ~238
Understand a log without reading it: detected format, number of EVENTS (a 40-line stack trace counts as one), breakdown by level, time range, the errors with their ROOT CAUSE resolved, and the most frequent patterns. Accepts a file PATH — that is how you look at a log that does not fit in your context, such as a CI log of hundreds of MB. Logs WRAPPED by whatever collected them (Docker json-file, CRI/Kubernetes `P`/`F` lines, `journalctl -o json`, OpenTelemetry OTLP JSON, AWS CloudTrail) are unwrapped first and the pieces the runtime split are joined back, so a stack trace spread over 40 records is one event; `wrapper` says which.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Force the format instead of detecting it |
| from | string | – | Which end to read if the file is over 32 MB |
| path | string | – | Path to the log file. Use this for big logs: they do not fit in a tool call. |
| text | string | – | The log as text. Alternative to `path`. |
No output schema declared.
No examples provided.
log_around ~237
What ELSE happened around a moment in time. Given an instant — the spike log_trends returned, or the time of an alert — find the patterns that cluster there and do not appear the same way in the rest of the log. Correlation is NOT causation, and what settles it is order: what started BEFORE comes first and is a candidate explanation; what came after is usually a consequence. Background noise is filtered out even when a narrow window lands on one of its bursts.
| Name | Type | Req | Description |
|---|---|---|---|
| at | string | yes | Reference instant, in ISO 8601 (e.g. "2026-08-27T10:40:00Z") |
| format | string | – | Force the format instead of detecting it |
| from | string | – | Which end to read if the file is over 32 MB |
| limit | integer | – | – |
| path | string | – | Path to the log file. Use this for big logs: they do not fit in a tool call. |
| radiusSeconds | integer | – | How far to look on each side |
| text | string | – | The log as text. Alternative to `path`. |
No output schema declared.
No examples provided.
log_convert ~190
Convert a log from one format to another through OpenTelemetry's Logs Data Model: JSON, logfmt, syslog RFC 5424, CSV, OpenTelemetry or Elastic Common Schema. Tells you UP FRONT what the conversion loses — syslog only has eight severities and a text body, so coming down to it from JSON drops fields.
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | – | CSV only: which fields become columns |
| format | string | – | Force the format instead of detecting it |
| from | string | – | Which end to read if the file is over 32 MB |
| host | string | – | – |
| path | string | – | Path to the log file. Use this for big logs: they do not fit in a tool call. |
| service | string | – | – |
| target | string | yes | Output format |
| text | string | – | The log as text. Alternative to `path`. |
No output schema declared.
No examples provided.
log_distinguish ~297
What sets a group of events APART from the rest of the log: the field=value pairs over-represented in the selection. E.g. of 300 errors, 92% have `version=2.4.1` against 4% of everything else — the deploy that broke it, found without reading 300 errors. Select by minimum level (default: errors), by text, or by one field=value; that selector is left out of the answer, since it would trivially top it. Fields that are unique per event (request ids, trace ids) are skipped: they identify, they do not distinguish. A difference in proportions, not causation.
| Name | Type | Req | Description |
|---|---|---|---|
| contains | string | – | Select events whose raw text contains this (case-insensitive) |
| field | string | – | Select events with this field… |
| format | string | – | Force the format instead of detecting it |
| from | string | – | Which end to read if the file is over 32 MB |
| limit | integer | – | – |
| minLevel | string | – | Select events at this level or above (default "error" if nothing else is given) |
| path | string | – | Path to the log file. Use this for big logs: they do not fit in a tool call. |
| text | string | – | The log as text. Alternative to `path`. |
| value | string | – | …equal to this value |
No output schema declared.
No examples provided.
log_lint ~169
Check whether the log is WELL WRITTEN — not what happened in the system: secrets or personal data printed, one line flooding the file, timestamps with no time zone (which make two machines impossible to correlate), the clock going backwards, everything at the same level, no request id, payload dumps, and orphan stack traces with no error line. Every finding comes with its count and a sample; secrets are masked.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Force the format instead of detecting it |
| from | string | – | Which end to read if the file is over 32 MB |
| path | string | – | Path to the log file. Use this for big logs: they do not fit in a tool call. |
| text | string | – | The log as text. Alternative to `path`. |
No output schema declared.
No examples provided.
log_patterns ~184
Group log lines into TEMPLATES (Drain algorithm): "connected to 10.0.0.1" and "connected to 10.0.0.7" are the same message. Turns a million lines into a few hundred readable things, each with its count, worst level and time range. Also returns the RARE ones (seen once or twice), which in a production log are usually what you were looking for.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Force the format instead of detecting it |
| from | string | – | Which end to read if the file is over 32 MB |
| limit | integer | – | How many patterns to return |
| path | string | – | Path to the log file. Use this for big logs: they do not fit in a tool call. |
| text | string | – | The log as text. Alternative to `path`. |
No output schema declared.
No examples provided.
log_profile_check ~107
Validate a Jarroba Tools LOG PROFILE (the `logprofile: 1` JSON that configures the log tools: format, server time zone, own-code prefixes, rules and AI budget). Returns ALL errors at once, each with the exact field (`rules[2].pattern`) and what was expected, so you can fix them in one pass instead of one at a time. Format documented in `public/logprofile.md`.
| Name | Type | Req | Description |
|---|---|---|---|
| profile | string | yes | The profile as JSON |
No output schema declared.
No examples provided.
log_profile_suggest ~183
Propose a LOG PROFILE from a real log: infers the format, the own-code prefix (read from the stack traces, which is where it is demonstrated) and a starting set of rules covering the most frequent errors and whatever floods the file. What it does NOT propose is the server time zone: that is not in the log, and inventing it shifts the entire timeline without anyone noticing. Accepts a file path.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Force the format instead of detecting it |
| from | string | – | Which end to read if the file is over 32 MB |
| name | string | – | Name for the profile |
| path | string | – | Path to the log file. Use this for big logs: they do not fit in a tool call. |
| text | string | – | The log as text. Alternative to `path`. |
No output schema declared.
No examples provided.
log_reduce ~206
Cut a log down to a CHARACTER budget while keeping what matters: errors with their full stack trace, the window of what happened just before, and anything that appears only once or twice. Repeats are collapsed with their count ([xN]) and gaps are marked ([...N]). Use it to hand a big log to a model without spending the context on the same line repeated.
| Name | Type | Req | Description |
|---|---|---|---|
| context | integer | – | Events kept before each error |
| format | string | – | Force the format instead of detecting it |
| from | string | – | Which end to read if the file is over 32 MB |
| fullTraces | boolean | – | false collapses each stack trace to its one-line summary |
| maxChars | integer | – | Character budget for the output |
| path | string | – | Path to the log file. Use this for big logs: they do not fit in a tool call. |
| text | string | – | The log as text. Alternative to `path`. |
No output schema declared.
No examples provided.
log_rotation ~155
Put a folder or a list of rotated logs into TIME ORDER, split into series. Rotation numbering runs BACKWARDS against time: `app.log.3.gz` is older than `app.log.1.gz`, and plain `app.log` is the newest; alphabetically `app.log.10` sorts before `app.log.9` while in time it comes after. Use this BEFORE reading several logs of one service, or you will read them backwards. Returns the paths already ordered, ready to feed to log_analyze one by one.
| Name | Type | Req | Description |
|---|---|---|---|
| directory | string | – | Folder to look in (does not recurse). Alternative to `names`. |
| names | array | – | List of file names or paths, in any order |
No output schema declared.
No examples provided.
log_stacktrace ~131
Read an exception stack trace (Java/JVM, Python, Node, Go, .NET, Rust, Ruby or PHP) and answer the only question anyone asks it: WHERE TO LOOK. Follows the "Caused by" chain to the root cause, separates your code from the framework, and points at your first frame. Infers which package is yours from the trace itself if you do not say.
| Name | Type | Req | Description |
|---|---|---|---|
| myPrefixes | array | – | Prefixes of your own code, e.g. ["com.acme.", "src/"] |
| trace | string | yes | The stack trace, pasted as-is |
No output schema declared.
No examples provided.
log_trends ~238
Answer WHEN IT STARTED, which is what a log is really asked. Compares each pattern against ITSELF rather than against total volume — in a busy service everything rises at 9am and nothing has happened — and returns three different things: what SPIKED relative to its own normal and at what time; what is NEW, which did not exist before and is usually what a deploy left behind; and what STOPPED APPEARING, which raises no counter and is often the worse news.
| Name | Type | Req | Description |
|---|---|---|---|
| bucketSeconds | integer | – | Width of the time bucket; by default chosen from the log's own range |
| format | string | – | Force the format instead of detecting it |
| from | string | – | Which end to read if the file is over 32 MB |
| limit | integer | – | How many findings to return |
| minRatio | number | – | How many times its own normal counts as a spike |
| path | string | – | Path to the log file. Use this for big logs: they do not fit in a tool call. |
| text | string | – | The log as text. Alternative to `path`. |
No output schema declared.
No examples provided.
How do I install the Jarroba Tools · Logs MCP server?
Jarroba Tools · Logs runs locally as an npm package, launched with npx -y @jarroba/mcp-logs. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @jarroba/mcp-logs
claude mcp add invarato-jarroba-tools-logs -- npx -y @jarroba/mcp-logs
What is the Jarroba Tools · Logs MCP server?
Jarroba Tools · Logs is an MCP server listed in the public MCP registry as io.github.Invarato/jarroba-tools-logs. Lets your AI read a CI log far too big for its context. 12 tools, takes a file path. This page covers its npm package (@jarroba/mcp-logs).
Is the Jarroba Tools · Logs MCP server safe to use?
Jarroba Tools · Logs scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Jarroba Tools · Logs MCP server expose?
Jarroba Tools · Logs exposes 12 tools: log_analyze, log_reduce, log_patterns, log_stacktrace, log_lint, and 7 more. Their descriptions and schemas cost roughly 2,335 tokens of context every time the server is loaded.
Is the Jarroba Tools · Logs MCP server still maintained?
Jarroba Tools · Logs is still listed as active in the MCP registry. We last reached this channel on 21 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 Jarroba Tools · Logs MCP server under?
Jarroba Tools · Logs declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Jarroba Tools · Logs MCP server?
VerifyMCP ran 16 checks on Jarroba Tools · Logs, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.