io.github.rog0x/log
NPM · @ROG0X/MCP-LOG-TOOLS
Log parse, filter, analyze for AI agents
Available components
Last scanned (14 hours ago)
Scores higher than 75% 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 228 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 575 tokens (~115/item across 5 items; 5 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 0
- Stability: pass → 0.97 functional
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 0
- Stability: pass → 0.97 functional
- 25 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 24 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 20 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 19 Oct 26 0
- Security disclosure: fail → unverified ▼ 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 6 Nov 2026 · Analysed npm/@rog0x/mcp-log-tools@1.0.2
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 →
analyze_logs ~69
Analyze log patterns: top 10 most frequent errors, error rate over time, request volume per hour, slowest endpoints (from access logs), and anomaly detection (sudden spikes/drops).
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Raw log content to analyze |
| format | string | – | Log format |
No output schema declared.
No examples provided.
filter_logs ~172
Filter log entries by level, date range, keyword, regex pattern, or source. Returns matched entries and level counts.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Raw log content to filter |
| date_from | string | – | Start date (ISO 8601) for date range filter |
| date_to | string | – | End date (ISO 8601) for date range filter |
| format | string | – | Log format |
| keyword | string | – | Keyword to search for (case-insensitive) |
| levels | array | – | Filter by log levels, e.g. ['ERROR', 'WARN'] |
| limit | number | – | Maximum number of matched entries to return |
| regex_pattern | string | – | Regex pattern to match against log messages |
| source | string | – | Filter by source/logger name (partial match) |
No output schema declared.
No examples provided.
format_logs ~131
Convert logs between formats (JSON, plain text, CSV, table). Supports colorization by level, field extraction, and summary report generation.
| Name | Type | Req | Description |
|---|---|---|---|
| colorize | boolean | – | Apply ANSI color codes based on log level |
| content | string | yes | Raw log content to format |
| include_fields | boolean | – | Include extracted fields in plain text output |
| input_format | string | – | Input log format |
| max_message_length | number | – | Truncate messages longer than this |
| output_format | string | – | Desired output format |
| summary | boolean | – | Generate a summary report instead of formatted output |
No output schema declared.
No examples provided.
log_stats ~77
Compute log statistics: total lines, lines per level, date range, unique IPs, top user agents, status code distribution, throughput, and more.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Raw log content to compute statistics for |
| format | string | – | Log format |
| rendered | boolean | – | Return human-readable rendered output instead of JSON |
No output schema declared.
No examples provided.
parse_logs ~126
Parse log content in common formats (JSON, Apache/Nginx, syslog, structured, or custom regex). Returns structured entries with timestamp, level, message, source, and extracted fields.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Raw log content to parse |
| custom_pattern | string | – | Custom regex pattern with named groups: (?<timestamp>), (?<level>), (?<message>), (?<source>) |
| format | string | – | Log format to use for parsing. Use 'auto' to detect automatically. |
| limit | number | – | Maximum number of entries to return |
No output schema declared.
No examples provided.
How do I install the io.github.rog0x/log MCP server?
io.github.rog0x/log runs locally as an npm package, launched with npx -y @rog0x/mcp-log-tools. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @rog0x/mcp-log-tools
claude mcp add rog0x-log -- npx -y @rog0x/mcp-log-tools
What is the io.github.rog0x/log MCP server?
io.github.rog0x/log is an MCP server listed in the public MCP registry as io.github.rog0x/log. Log parse, filter, analyze for AI agents. This page covers its npm package (@rog0x/mcp-log-tools).
Is the io.github.rog0x/log MCP server safe to use?
io.github.rog0x/log scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 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.rog0x/log MCP server expose?
io.github.rog0x/log exposes 5 tools: parse_logs, filter_logs, analyze_logs, format_logs, log_stats. Their descriptions and schemas cost roughly 575 tokens of context every time the server is loaded.
Is the io.github.rog0x/log MCP server still maintained?
io.github.rog0x/log is still listed as active in the MCP registry. We last reached this channel on 6 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.rog0x/log MCP server under?
io.github.rog0x/log 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 io.github.rog0x/log MCP server?
VerifyMCP ran 16 checks on io.github.rog0x/log, 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.