io.github.sebastienrousseau/rlg-mcp
OCI · GHCR.IO/SEBASTIENROUSSEAU/RLG-MCP
MCP server exposing rlg log streams to LLM agents via JSON-RPC 2.0 over stdio.
Available components
Last scanned (8 hours ago)
Scores higher than 97% of OCI 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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency48
- 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 OR Apache-2.0).Pass
- Actively maintained (last published 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 640 tokens (~128/item across 5 items; 4 tools + 1 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 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.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 6 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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 Nov 26 0
- Package version: 0.0.15 → 0.0.16 functional
- 31 Oct 26 +1
- Stability: 0.97 → pass security
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 26 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.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 0
- Provenance: unverified → fail ▼ security
- 20 Oct 26 +1
- Provenance: fail → unverified ▼ security
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 oci/ghcr.io/sebastienrousseau/rlg-mcp@0.0.16
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
filter_log ~169
Select rlg records by minimum severity and/or component and render them in any rlg LogFormat. Use this to narrow a log to what matters (e.g. WARN-and-above for one service); use `tail_log` for a raw recent slice and `summarize_errors` when you only need per-component error totals.
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | – | Keep only records whose component matches this exact value. Omit to keep all components. |
| format | string | – | rlg LogFormat name to render matched records in (e.g. Logfmt, JSON). Defaults to Logfmt. |
| min_level | string | – | Keep only records at or above this severity. Omit to keep all levels. |
| path | string | yes | Filesystem path to an rlg log file to read. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | How many records are returned. |
| records | array | yes | The records, oldest first, one rendered record each. |
No examples provided.
summarize_errors ~81
Group ERROR-and-above rlg records by component and count them, giving a quick error taxonomy for triage. Use this for an at-a-glance failure breakdown; use `filter_log` when you need the underlying records rather than counts.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Filesystem path to an rlg log file to scan for ERROR-and-above records. |
| Name | Type | Req | Description |
|---|---|---|---|
| by_component | object | yes | The count per component, sorted by component name. |
| total | integer | yes | How many ERROR-and-above records the file holds. |
No examples provided.
tail_log ~119
Return the last N parseable rlg (RustLogs) records from a log file, newest last. Use this to glance at the most recent activity in a log; use `filter_log` when you need to select records by level or component, and `summarize_errors` for an aggregated error count.
| Name | Type | Req | Description |
|---|---|---|---|
| n | integer | – | How many of the most recent parseable records to return (default 100). |
| path | string | yes | Filesystem path to an rlg log file (Logfmt/JSON records, one per line). |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | How many records are returned. |
| records | array | yes | The records, oldest first, one rendered record each. |
No examples provided.
tail_logs_glob ~158
Return the last N parseable rlg records across every file matching a glob pattern (e.g. `/var/log/**/*.log`), newest last, optionally filtered to a minimum level. Use this to tail many rotated or per-service log files at once; use `tail_log` for a single file and `summarize_errors` for per-component error totals.
| Name | Type | Req | Description |
|---|---|---|---|
| glob_pattern | string | yes | Glob pattern matching one or more rlg log files, e.g. `/var/log/**/*.log`. |
| level | string | – | Keep only records at or above this severity. Omit to keep all levels. |
| lines | integer | – | How many of the most recent parseable records to return across all matched files (default 100). |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | How many records are returned. |
| records | array | yes | The records, oldest first, one rendered record each. |
No examples provided.
How do I install the io.github.sebastienrousseau/rlg-mcp server?
io.github.sebastienrousseau/rlg-mcp runs locally as a container image, launched with docker run --rm -i ghcr.io/sebastienrousseau/rlg-mcp:0.0.16. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/sebastienrousseau/rlg-mcp
claude mcp add sebastienrousseau-rlg-mcp -- docker run --rm -i ghcr.io/sebastienrousseau/rlg-mcp:0.0.16
What is the io.github.sebastienrousseau/rlg-mcp server?
io.github.sebastienrousseau/rlg-mcp is listed in the public MCP registry as io.github.sebastienrousseau/rlg-mcp. MCP server exposing rlg log streams to LLM agents via JSON-RPC 2.0 over stdio. This page covers its container image (ghcr.io/sebastienrousseau/rlg-mcp).
Is the io.github.sebastienrousseau/rlg-mcp server safe to use?
io.github.sebastienrousseau/rlg-mcp scores 57 out of 100 on VerifyMCP. 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.sebastienrousseau/rlg-mcp server expose?
io.github.sebastienrousseau/rlg-mcp exposes 4 tools: filter_log, summarize_errors, tail_log, tail_logs_glob. Their descriptions and schemas cost roughly 527 tokens of context every time the server is loaded.
Is the io.github.sebastienrousseau/rlg-mcp server still maintained?
io.github.sebastienrousseau/rlg-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.sebastienrousseau/rlg-mcp server under?
io.github.sebastienrousseau/rlg-mcp declares the MIT OR Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.