NestDaddy

Keep Me Secure

io.github.robertkeus/keep-me-secure-mcp · v1.7.0

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

Connect Remote server

Terminal
claude mcp add --transport http keep-me-secure-mcp https://mcp.keepmesecure.dev/mcp
~/.cursor/mcp.json
{
  "mcpServers": {
    "keep-me-secure-mcp": {
      "url": "https://mcp.keepmesecure.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "keep-me-secure-mcp": {
      "type": "http",
      "url": "https://mcp.keepmesecure.dev/mcp"
    }
  }
}
Claude Desktop
Settings > Connectors > Add custom connector
URL: https://mcp.keepmesecure.dev/mcp

Tools 4 found in our last check

  • check_packages

    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…

  • check_platform

    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.

  • check_runtime

    Checks a Node.js or PHP version against known security flaws in the runtime itself. Use with the exact version, for example from `node --version` or `php --version`. The list is curated, so no findings doesn't prove a version is safe.

  • check_package

    Checks one exact package version against public security advisories.

Details

Endpointhttps://mcp.keepmesecure.dev/mcp (Streamable HTTP)
Packageghcr.io/robertkeus/keep-me-secure-mcp:v1.7.0 (OCI, stdio)
First published6 Nov 2026
Last updated6 Nov 2026
Registry nameio.github.robertkeus/keep-me-secure-mcp

More developer tools servers See all

Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.