# Keep Me Secure (oci · ghcr.io/robertkeus/keep-me-secure-mcp)

Tells your coding agent whether your installed packages need patching, with advice on what to do.

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

## Components

- remote · `mcp.keepmesecure.dev`: 66/100, [markdown](https://verifymcp.io/servers/robertkeus-keep-me-secure-mcp/mcp.md), [page](https://verifymcp.io/servers/robertkeus-keep-me-secure-mcp/mcp)
- oci · `ghcr.io/robertkeus/keep-me-secure-mcp`: 38/100 (this document), [markdown](https://verifymcp.io/servers/robertkeus-keep-me-secure-mcp/ghcr-io-robertkeus-keep-me-secure-mcp.md), [page](https://verifymcp.io/servers/robertkeus-keep-me-secure-mcp/ghcr-io-robertkeus-keep-me-secure-mcp)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/robertkeus/keep-me-secure-mcp`
- Version: `v1.4.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 image's dependency list comes from an SBOM its publisher attached, which nothing verifies, so we will not report it as a clean result.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.
- **Provenance & Transparency**: 35/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 0 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 494 tokens (~164/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability observed for 0 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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: 2 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 Keep Me Secure MCP server?

Keep Me Secure runs locally as a container image, launched with docker run --rm -i ghcr.io/robertkeus/keep-me-secure-mcp:v1.4.0, plus the required -v, which you supply. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. 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 robertkeus-keep-me-secure-mcp -- docker run --rm -i ghcr.io/robertkeus/keep-me-secure-mcp:v1.4.0
```

The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks -v as required and gives no value we can show, so it is not in this command. Add it before you run it.

### Cursor

```json
{
  "mcpServers": {
    "robertkeus-keep-me-secure-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/robertkeus/keep-me-secure-mcp:v1.4.0"
      ]
    }
  }
}
```

The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks -v as required and gives no value we can show, so it is not in this command. Add it before you run it.

### VS Code

```json
{
  "servers": {
    "robertkeus-keep-me-secure-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/robertkeus/keep-me-secure-mcp:v1.4.0"
      ]
    }
  }
}
```

The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks -v as required and gives no value we can show, so it is not in this command. Add it before you run it.

### Codex

```bash
codex mcp add robertkeus-keep-me-secure-mcp -- docker run --rm -i ghcr.io/robertkeus/keep-me-secure-mcp:v1.4.0
```

The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks -v as required and gives no value we can show, so it is not in this command. Add it before you run it.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "robertkeus-keep-me-secure-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/robertkeus/keep-me-secure-mcp:v1.4.0"
      ],
      "enabled": true
    }
  }
}
```

The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks -v as required and gives no value we can show, so it is not in this command. Add it before you run it.

### Hermes

```yaml
mcp_servers:
  robertkeus-keep-me-secure-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/robertkeus/keep-me-secure-mcp:v1.4.0"]
```

The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks -v as required and gives no value we can show, so it is not in this command. Add it before you run it.

### Netclaw

```json
{
  "McpServers": {
    "robertkeus-keep-me-secure-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/robertkeus/keep-me-secure-mcp:v1.4.0"
      ]
    }
  }
}
```

The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks -v as required and gives no value we can show, so it is not in this command. Add it before you run it.

### Other

```json
{
  "mcpServers": {
    "robertkeus-keep-me-secure-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/robertkeus/keep-me-secure-mcp:v1.4.0"
      ]
    }
  }
}
```

The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks -v as required and gives no value we can show, so it is not in this command. Add it before you run it.

## 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-05 (score 38)

First indexed and scored.

## MCP tools (3)

### `check_project` (~198 tokens)

Is my stack secure?

Use for questions like 'is my stack secure?', 'do I need to patch anything?' or 'do we have vulnerable packages?'. Checks every installed package, including transitive ones, in all lockfiles in this project against public security advisories. verdict is yes, no or unknown; unknown means the check was incomplete, so never report it as safe. Supports PHP, JavaScript, Python, Go, Rust, Ruby, Java (Gradle lockfiles) and .NET. Does not cover language runtimes, OS packages or Docker base images.

Input parameters:

- `ecosystem` (string): Only to limit the check: php, npm, python, go, rust, ruby, java or dotnet. Omit for a full check.
- `path` (string): Subfolder relative to the project root. Omit to scan the whole project. Test and example folders are skipped unless named here.
- `refresh` (boolean): Ignore today's cached result

### `check_platform` (~83 tokens)

Has this platform been breached?

Lists known security incidents at hosting, deployment and AI platforms, with what to do and a link to the source. Use when the user asks about a platform or breach. Omit name to list all. The list is curated and not complete, so no result doesn't mean a platform is safe.

Input parameters:

- `name` (string): Platform name, such as railway or vercel

### `check_package` (~77 tokens)

Is this package version safe?

Checks one exact package version against public security advisories.

Input parameters:

- `ecosystem` (string, required): php, npm, python, go, rust, ruby, java or dotnet
- `name` (string, required): Package name, such as guzzlehttp/guzzle
- `version` (string, required): Exact version, such as 7.4.0

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities. The full working is on the page: https://verifymcp.io/servers/robertkeus-keep-me-secure-mcp/ghcr-io-robertkeus-keep-me-secure-mcp#diagnostics

## Score history

- 2026-11-05: 38

## Common questions

### What is the Keep Me Secure MCP server?

Keep Me Secure is an MCP server listed in the public MCP registry as io.github.robertkeus/keep-me-secure-mcp. Tells your coding agent whether your installed packages need patching, with advice on what to do. This page covers its container image (ghcr.io/robertkeus/keep-me-secure-mcp).

### Is the Keep Me Secure MCP server safe to use?

Keep Me Secure scores 38 out of 100 on VerifyMCP. The SBOM its publisher attached lists packages with 19 known advisories as of 5 November 2026. We do not grade that SBOM, as nothing verifies it. 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 Keep Me Secure MCP server expose?

Keep Me Secure exposes 3 tools: check_project, check_platform, check_package. Their descriptions and schemas cost roughly 358 tokens of context every time the server is loaded.

### Is the Keep Me Secure MCP server still maintained?

Keep Me Secure 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 did VerifyMCP test on the Keep Me Secure MCP server?

VerifyMCP ran 11 checks on Keep Me Secure, covering Source repository, Provenance, License, Maintenance and 7 more. 5 items could not be completed, a gap on our side rather than a finding about Keep Me Secure: Malware scan, Known CVEs, Install scripts, Dependency health and 1 more. 2 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- GitHub Container Registry: https://ghcr.io/robertkeus/keep-me-secure-mcp
- Repository: https://github.com/robertkeus/keep-me-secure-mcp
- Website: https://keepmesecure.dev/
- Changelog RSS feed: https://verifymcp.io/servers/robertkeus-keep-me-secure-mcp/ghcr-io-robertkeus-keep-me-secure-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/robertkeus-keep-me-secure-mcp/ghcr-io-robertkeus-keep-me-secure-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/robertkeus-keep-me-secure-mcp/ghcr-io-robertkeus-keep-me-secure-mcp.json
- HTML version of this page: https://verifymcp.io/servers/robertkeus-keep-me-secure-mcp/ghcr-io-robertkeus-keep-me-secure-mcp