# io.github.sebastienrousseau/rlg-mcp (oci · ghcr.io/sebastienrousseau/rlg-mcp:0.0.12)

MCP server exposing rlg log streams to LLM agents via JSON-RPC 2.0 over stdio.

- Trust score: 54/100 (low)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- oci · `ghcr.io/sebastienrousseau/rlg-mcp:0.0.12`: 54/100 (this document), [markdown](https://verifymcp.io/servers/sebastienrousseau-rlg-mcp/ghcr-io-sebastienrousseau-rlg-mcp-0-0-12.md), [page](https://verifymcp.io/servers/sebastienrousseau-rlg-mcp/ghcr-io-sebastienrousseau-rlg-mcp-0-0-12)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/sebastienrousseau/rlg-mcp:0.0.12`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Supply Chain Security**: 0/100
  - Malware scan not yet available for this package.
  - Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT OR Apache-2.0).
  - Actively maintained (last published 25 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 87/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 554 tokens (~110/item across 5 items; 4 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

**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.

## Install

### 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.12. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add sebastienrousseau-rlg-mcp -- docker run --rm -i ghcr.io/sebastienrousseau/rlg-mcp:0.0.12
```

### Cursor

```json
{
  "mcpServers": {
    "sebastienrousseau-rlg-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/sebastienrousseau/rlg-mcp:0.0.12"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "sebastienrousseau-rlg-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/sebastienrousseau/rlg-mcp:0.0.12"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add sebastienrousseau-rlg-mcp -- docker run --rm -i ghcr.io/sebastienrousseau/rlg-mcp:0.0.12
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sebastienrousseau-rlg-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/sebastienrousseau/rlg-mcp:0.0.12"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  sebastienrousseau-rlg-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/sebastienrousseau/rlg-mcp:0.0.12"]
```

### Netclaw

```json
{
  "McpServers": {
    "sebastienrousseau-rlg-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/sebastienrousseau/rlg-mcp:0.0.12"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "sebastienrousseau-rlg-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/sebastienrousseau/rlg-mcp:0.0.12"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 54, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 53, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 52, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 51, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 50, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 49, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 48, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-06 (score 47, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (4)

### `tail_log` (~119 tokens)

Tail rlg log file

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.

Input parameters:

- `n` (integer): How many of the most recent parseable records to return (default 100).
- `path` (string, required): Filesystem path to an rlg log file (Logfmt/JSON records, one per line).

### `filter_log` (~169 tokens)

Filter rlg log records

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.

Input parameters:

- `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, required): Filesystem path to an rlg log file to read.

### `summarize_errors` (~81 tokens)

Summarize rlg errors by component

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.

Input parameters:

- `path` (string, required): Filesystem path to an rlg log file to scan for ERROR-and-above records.

### `tail_logs_glob` (~158 tokens)

Tail rlg logs across a glob

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.

Input parameters:

- `glob_pattern` (string, required): 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).

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/sebastienrousseau-rlg-mcp/ghcr-io-sebastienrousseau-rlg-mcp-0-0-12#diagnostics

## Score history

- 2026-09-21: 54
- 2026-09-20: 53
- 2026-09-19: 53
- 2026-09-18: 52
- 2026-09-17: 52
- 2026-09-16: 51
- 2026-09-15: 51
- 2026-09-14: 50
- 2026-09-13: 50
- 2026-09-12: 50
- 2026-09-11: 49
- 2026-09-10: 49
- 2026-09-09: 48
- 2026-09-08: 48
- 2026-09-07: 47
- 2026-09-06: 47
- 2026-09-05: 46
- 2026-09-04: 46
- 2026-09-03: 45
- 2026-09-02: 42
- 2026-09-01: 42
- 2026-08-31: 42
- 2026-08-30: 42
- 2026-08-29: 42
- 2026-08-28: 42
- 2026-08-27: 42
- 2026-08-26: 42

## Common questions

### 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:0.0.12).

### Is the io.github.sebastienrousseau/rlg-mcp server safe to use?

io.github.sebastienrousseau/rlg-mcp scores 54 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: tail_log, filter_log, summarize_errors, 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 21 September 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.

## Links

- Repository: https://github.com/sebastienrousseau/rlg
- Changelog RSS feed: https://verifymcp.io/servers/sebastienrousseau-rlg-mcp/ghcr-io-sebastienrousseau-rlg-mcp-0-0-12.xml
- Changelog JSON feed: https://verifymcp.io/servers/sebastienrousseau-rlg-mcp/ghcr-io-sebastienrousseau-rlg-mcp-0-0-12.json
- HTML version of this page: https://verifymcp.io/servers/sebastienrousseau-rlg-mcp/ghcr-io-sebastienrousseau-rlg-mcp-0-0-12