# scree (oci · ghcr.io/jrapakko/scree)

Local semantic and keyword search over the markdown in a repo or notes folder.

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

## Components

- mcpb · `scree_0.4.1.mcpb`: 9/100, [markdown](https://verifymcp.io/servers/jrapakko-scree/scree.md), [page](https://verifymcp.io/servers/jrapakko-scree/scree)
- oci · `ghcr.io/jrapakko/scree`: 9/100 (this document), [markdown](https://verifymcp.io/servers/jrapakko-scree/ghcr-io-jrapakko-scree.md), [page](https://verifymcp.io/servers/jrapakko-scree/ghcr-io-jrapakko-scree)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/jrapakko/scree`
- Version: `0.4.1`
- 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 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.
- **Capabilities**: 0/100
  - Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.

**Unverified: 6 categories.** Categories scored 0 because we could not verify them: 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 scree MCP server?

scree runs locally as a container image, launched with docker run --rm -i -e OPENROUTER_API_KEY ghcr.io/jrapakko/scree:0.4.1. 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 jrapakko-scree -- docker run --rm -i -e OPENROUTER_API_KEY ghcr.io/jrapakko/scree:0.4.1
```

This image reads OPENROUTER_API_KEY. Set it in your client's env block for this server; docker run -e passes it through to the container.

### Cursor

```json
{
  "mcpServers": {
    "jrapakko-scree": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "OPENROUTER_API_KEY",
        "ghcr.io/jrapakko/scree:0.4.1"
      ]
    }
  }
}
```

This image reads OPENROUTER_API_KEY. Set it in your client's env block for this server; docker run -e passes it through to the container.

### VS Code

```json
{
  "servers": {
    "jrapakko-scree": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "OPENROUTER_API_KEY",
        "ghcr.io/jrapakko/scree:0.4.1"
      ]
    }
  }
}
```

This image reads OPENROUTER_API_KEY. Set it in your client's env block for this server; docker run -e passes it through to the container.

### Codex

```bash
codex mcp add jrapakko-scree -- docker run --rm -i -e OPENROUTER_API_KEY ghcr.io/jrapakko/scree:0.4.1
```

This image reads OPENROUTER_API_KEY. Set it in your client's env block for this server; docker run -e passes it through to the container.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jrapakko-scree": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "-e",
        "OPENROUTER_API_KEY",
        "ghcr.io/jrapakko/scree:0.4.1"
      ],
      "enabled": true
    }
  }
}
```

This image reads OPENROUTER_API_KEY. Set it in your client's env block for this server; docker run -e passes it through to the container.

### Hermes

```yaml
mcp_servers:
  jrapakko-scree:
    command: "docker"
    args: ["run", "--rm", "-i", "-e", "OPENROUTER_API_KEY", "ghcr.io/jrapakko/scree:0.4.1"]
```

This image reads OPENROUTER_API_KEY. Set it in your client's env block for this server; docker run -e passes it through to the container.

### Netclaw

```json
{
  "McpServers": {
    "jrapakko-scree": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "-e",
        "OPENROUTER_API_KEY",
        "ghcr.io/jrapakko/scree:0.4.1"
      ]
    }
  }
}
```

This image reads OPENROUTER_API_KEY. Set it in your client's env block for this server; docker run -e passes it through to the container.

### Other

```json
{
  "mcpServers": {
    "jrapakko-scree": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "OPENROUTER_API_KEY",
        "ghcr.io/jrapakko/scree:0.4.1"
      ]
    }
  }
}
```

This image reads OPENROUTER_API_KEY. Set it in your client's env block for this server; docker run -e passes it through to the container.

## 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 9, 0)

- [security regression] Provenance: fail → unverified
- [functional] Package version: 0.4.0 → 0.4.1

### 2026-11-03 (score 9, 0)

- [functional] Package version: 0.3.5 → 0.4.0
- [functional] Package version: 0.3.5 → 0.3.6

### 2026-11-01 (score 9)

First indexed and scored.

## MCP tools (0)

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

## Diagnostics

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

## Score history

- 2026-11-05: 9
- 2026-11-04: 9
- 2026-11-03: 9
- 2026-11-02: 9
- 2026-11-01: 9

## Common questions

### What is the scree MCP server?

scree is an MCP server listed in the public MCP registry as io.github.jrapakko/scree. Local semantic and keyword search over the markdown in a repo or notes folder. This page covers its container image (ghcr.io/jrapakko/scree).

### Is the scree MCP server safe to use?

scree scores 9 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.

### Is the scree MCP server still maintained?

scree 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 scree MCP server under?

scree 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/jrapakko/scree
- Repository: https://github.com/jrapakko/scree
- Website: https://scree.jrpko.dev/
- Changelog RSS feed: https://verifymcp.io/servers/jrapakko-scree/ghcr-io-jrapakko-scree.xml
- Changelog JSON feed: https://verifymcp.io/servers/jrapakko-scree/ghcr-io-jrapakko-scree.json
- HTML version of this page: https://verifymcp.io/servers/jrapakko-scree/ghcr-io-jrapakko-scree