# io.github.CloudCorpRecords/evalsnap (oci · ghcr.io/cloudcorprecords/evalsnap)

Snapshot diff for agent and tool outputs: changed cases, score regressions, pass/fail verdict.

- Trust score: 40/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@reneturcios/evalsnap`: 68/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-evalsnap/reneturcios-evalsnap.md), [page](https://verifymcp.io/servers/cloudcorprecords-evalsnap/reneturcios-evalsnap)
- oci · `ghcr.io/cloudcorprecords/evalsnap`: 40/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-evalsnap/ghcr-io-cloudcorprecords-evalsnap.md), [page](https://verifymcp.io/servers/cloudcorprecords-evalsnap/ghcr-io-cloudcorprecords-evalsnap)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/cloudcorprecords/evalsnap`
- Version: `0.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-11-05.

- **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**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 75 tokens (~75/item across 1 items; 1 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); 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.CloudCorpRecords/evalsnap MCP server?

io.github.CloudCorpRecords/evalsnap runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/evalsnap:0.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 cloudcorprecords-evalsnap -- docker run --rm -i ghcr.io/cloudcorprecords/evalsnap:0.1.0
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-evalsnap": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/evalsnap:0.1.0"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-evalsnap": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/evalsnap:0.1.0"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-evalsnap -- docker run --rm -i ghcr.io/cloudcorprecords/evalsnap:0.1.0
```

### opencode

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

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-evalsnap:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/cloudcorprecords/evalsnap:0.1.0"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-evalsnap": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/evalsnap:0.1.0"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-evalsnap": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/evalsnap:0.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-11-04 (score 40, +1)

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

### 2026-11-02 (score 39)

First indexed and scored.

## MCP tools (1)

### `diff_snapshots` (~75 tokens)

Diff two eval snapshots matched by case_id: changed and unchanged cases, score and duration deltas, regressions, average scores over matched scored cases, and a pass/fail verdict.

Input parameters:

- `baseline` (array, required): Baseline snapshot entries (at least one)
- `current` (array, required): Current snapshot entries (at least one)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-evalsnap/ghcr-io-cloudcorprecords-evalsnap#diagnostics

## Score history

- 2026-11-05: 40
- 2026-11-04: 40
- 2026-11-03: 39
- 2026-11-02: 39

## Common questions

### What is the io.github.CloudCorpRecords/evalsnap MCP server?

io.github.CloudCorpRecords/evalsnap is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/evalsnap. Snapshot diff for agent and tool outputs: changed cases, score regressions, pass/fail verdict. This page covers its container image (ghcr.io/cloudcorprecords/evalsnap).

### Is the io.github.CloudCorpRecords/evalsnap MCP server safe to use?

io.github.CloudCorpRecords/evalsnap scores 40 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.CloudCorpRecords/evalsnap MCP server expose?

io.github.CloudCorpRecords/evalsnap exposes 1 tool: diff_snapshots. Their descriptions and schemas cost roughly 75 tokens of context every time the server is loaded.

### Is the io.github.CloudCorpRecords/evalsnap MCP server still maintained?

io.github.CloudCorpRecords/evalsnap 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.CloudCorpRecords/evalsnap MCP server under?

io.github.CloudCorpRecords/evalsnap declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- GitHub Container Registry: https://ghcr.io/cloudcorprecords/evalsnap
- Repository: https://github.com/CloudCorpRecords/evalsnap
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-evalsnap/ghcr-io-cloudcorprecords-evalsnap.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-evalsnap/ghcr-io-cloudcorprecords-evalsnap.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-evalsnap/ghcr-io-cloudcorprecords-evalsnap