# io.github.diyaluo/data-report-mcp (oci · ghcr.io/diyaluo/data-report-mcp)

Local-first CSV/XLSX analysis report MCP server (stats, Excel charts, Markdown), no upload.

- Trust score: 31/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-24

## Components

- oci · `ghcr.io/diyaluo/data-report-mcp`: 31/100 (this document), [markdown](https://verifymcp.io/servers/diyaluo-data-report-mcp/ghcr-io-diyaluo-data-report-mcp.md), [page](https://verifymcp.io/servers/diyaluo-data-report-mcp/ghcr-io-diyaluo-data-report-mcp)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/diyaluo/data-report-mcp`
- Version: `v0.1.0`
- 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-10-24.

- **Supply Chain Security**: 0/100
  - 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.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 6/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 5 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 249 tokens (~124/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (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.diyaluo/data-report-mcp server?

io.github.diyaluo/data-report-mcp runs locally as a container image, launched with docker run --rm -i ghcr.io/diyaluo/data-report-mcp:v0.1.0. 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 diyaluo-data-report-mcp -- docker run --rm -i ghcr.io/diyaluo/data-report-mcp:v0.1.0
```

### Cursor

```json
{
  "mcpServers": {
    "diyaluo-data-report-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/diyaluo/data-report-mcp:v0.1.0"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "diyaluo-data-report-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/diyaluo/data-report-mcp:v0.1.0"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add diyaluo-data-report-mcp -- docker run --rm -i ghcr.io/diyaluo/data-report-mcp:v0.1.0
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "diyaluo-data-report-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/diyaluo/data-report-mcp:v0.1.0"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  diyaluo-data-report-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/diyaluo/data-report-mcp:v0.1.0"]
```

### Netclaw

```json
{
  "McpServers": {
    "diyaluo-data-report-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/diyaluo/data-report-mcp:v0.1.0"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "diyaluo-data-report-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/diyaluo/data-report-mcp:v0.1.0"
      ]
    }
  }
}
```

## 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-10-24 (score 31, +1)

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

### 2026-10-22 (score 30, +1)

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

### 2026-10-19 (score 29, +1)

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

### 2026-10-18 (score 28)

First indexed and scored.

## MCP tools (2)

### `health` (~18 tokens)

Service health + free-tier limits. No auth required.

### `analyze_table` (~231 tokens)

Analyze a CSV/XLSX table fully locally: infer numeric/categorical
    columns, compute shape, missing rate, duplicates, min/max/mean/median/sum/
    stddev, top frequencies for text columns and pairwise correlations
    (|r|>=0.5), and return a Chinese Markdown insights report. Optionally a
    base64 Excel workbook with native interactive bar charts.

    Args:
        file_base64: raw CSV/XLSX content as base64 (preferred).
        file_url:    direct HTTPS URL to a .csv/.xlsx (alternative).
        filename:    original filename (used only to decide csv vs xlsx).
        charts:      max category columns to chart in the xlsx workbook.
        return_xlsx: when true, include the generated workbook as base64.
        api_key:     paid key to bypass the anonymous monthly quota.

Input parameters:

- `api_key`
- `charts` (integer)
- `file_base64`
- `file_url`
- `filename` (string)
- `return_xlsx` (boolean)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/diyaluo-data-report-mcp/ghcr-io-diyaluo-data-report-mcp#diagnostics

## Score history

- 2026-10-24: 31
- 2026-10-23: 30
- 2026-10-22: 30
- 2026-10-21: 29
- 2026-10-20: 29
- 2026-10-19: 29
- 2026-10-18: 28

## Common questions

### What is the io.github.diyaluo/data-report-mcp server?

io.github.diyaluo/data-report-mcp is listed in the public MCP registry as io.github.diyaluo/data-report-mcp. Local-first CSV/XLSX analysis report MCP server (stats, Excel charts, Markdown), no upload. This page covers its container image (ghcr.io/diyaluo/data-report-mcp).

### Is the io.github.diyaluo/data-report-mcp server safe to use?

io.github.diyaluo/data-report-mcp scores 31 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.diyaluo/data-report-mcp server expose?

io.github.diyaluo/data-report-mcp exposes 2 tools: health, analyze_table. Their descriptions and schemas cost roughly 249 tokens of context every time the server is loaded.

### Is the io.github.diyaluo/data-report-mcp server still maintained?

io.github.diyaluo/data-report-mcp is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- GitHub Container Registry: https://ghcr.io/diyaluo/data-report-mcp
- Changelog RSS feed: https://verifymcp.io/servers/diyaluo-data-report-mcp/ghcr-io-diyaluo-data-report-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/diyaluo-data-report-mcp/ghcr-io-diyaluo-data-report-mcp.json
- HTML version of this page: https://verifymcp.io/servers/diyaluo-data-report-mcp/ghcr-io-diyaluo-data-report-mcp