# Keep Me Secure (remote · mcp.keepmesecure.dev)

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

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

## Components

- remote · `mcp.keepmesecure.dev`: 66/100 (this document), [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, [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

- Endpoint: `https://mcp.keepmesecure.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.4.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 377 tokens (~125/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 80% 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: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Keep Me Secure MCP server?

Keep Me Secure is a hosted endpoint at https://mcp.keepmesecure.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http robertkeus-keep-me-secure-mcp 'https://mcp.keepmesecure.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "robertkeus-keep-me-secure-mcp": {
      "url": "https://mcp.keepmesecure.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "robertkeus-keep-me-secure-mcp": {
      "type": "http",
      "url": "https://mcp.keepmesecure.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.robertkeus-keep-me-secure-mcp]
url = "https://mcp.keepmesecure.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "robertkeus-keep-me-secure-mcp": {
      "type": "remote",
      "url": "https://mcp.keepmesecure.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add robertkeus-keep-me-secure-mcp --url 'https://mcp.keepmesecure.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  robertkeus-keep-me-secure-mcp:
    url: "https://mcp.keepmesecure.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "robertkeus-keep-me-secure-mcp": {
      "Transport": "http",
      "Url": "https://mcp.keepmesecure.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add robertkeus-keep-me-secure-mcp -t streamable-http -u 'https://mcp.keepmesecure.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "robertkeus-keep-me-secure-mcp": {
      "type": "http",
      "url": "https://mcp.keepmesecure.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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 66)

First indexed and scored.

## MCP tools (3)

### `check_packages` (~109 tokens)

Is my stack secure?

Use for questions like 'is my stack secure?' or 'do we have vulnerable packages?'. Checks a list of exact installed package versions against public security advisories. Read them from the project's lockfiles, including transitive packages. Up to 500 per call; call again for more. verdict is yes, no or unknown; unknown means the check was incomplete, so never report it as safe. Does not cover language runtimes, OS packages or Docker base images.

Input parameters:

- `packages` (array, required)

### `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: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/robertkeus-keep-me-secure-mcp/mcp#diagnostics

## Score history

- 2026-11-05: 66

## 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 hosted endpoint (https://mcp.keepmesecure.dev/mcp).

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

Keep Me Secure scores 66 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 Keep Me Secure MCP server expose?

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

### Does the Keep Me Secure MCP server require authentication?

No. We connected to Keep Me Secure without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### 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 TLS certificate, Authorization, HSTS header, DNSSEC and 7 more. 2 items could not be completed, a gap on our side rather than a finding about Keep Me Secure: HTTPS and Stability. One category scores 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.keepmesecure.dev/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/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/robertkeus-keep-me-secure-mcp/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/robertkeus-keep-me-secure-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/robertkeus-keep-me-secure-mcp/mcp