io.github.rog0x/log
NPM · @ROG0X/MCP-LOG-TOOLS · SCANNED AUG 3
Log parse, filter, analyze for AI agents
Available components
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 →
Supply Chain Security86
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. 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 133 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- 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 Management23
- Stability observed for 7 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @rog0x/mcp-log-tools
claude mcp add rog0x-log -- npx -y @rog0x/mcp-log-tools
codex mcp add rog0x-log -- npx -y @rog0x/mcp-log-tools
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"rog0x-log": {
"type": "local",
"command": [
"npx",
"-y",
"@rog0x/mcp-log-tools"
],
"enabled": true
}
}
} openclaw mcp add rog0x-log --command npx --arg -y --arg @rog0x/mcp-log-tools
mcp_servers:
rog0x-log:
command: "npx"
args: ["-y", "@rog0x/mcp-log-tools"] {
"mcpServers": {
"rog0x-log": {
"command": "npx",
"args": [
"-y",
"@rog0x/mcp-log-tools"
]
}
}
} 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.
- 2 Aug 26 +42
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Schema quality: unverified → good ▲ functional
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- Stability: unverified → 0.20 ▲ functional
- Licence: MIT functional
- 1 Aug 26 +5
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → pass ▲ functional
- 31 Jul 26 −7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 28 Jul 26 +22
- Security disclosure: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: unverified functional
- First check of Schema quality: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- 27 Jul 26 24
First indexed and scored.
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 3 Aug 2026 · Analysed npm/@rog0x/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 94 packages
94 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.