Keep Me Secure MCP server
io.github.robertkeus/keep-me-secure-mcprobertkeusstreamable-httpv1.7.0Scanned
Tells your coding agent whether your installed packages need patching, with advice on what to do.
4 tools: 3 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 4
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Keep Me Secure MCP server can do
The Keep Me Secure MCP server is published by the GitHub account robertkeus. It has 4 tools. It can create or change data (3 tools: check_packages, check_runtime and check_package), but cannot delete data. 1 tool only reads.
4 tools bring in text other people can write (check_packages, check_platform, check_runtime and 1 more).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 20, 2026, version 1.7.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 3Claude Code: ask
check_packageChecks one exact package version against public security advisories.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Checks one exact package version against public security advisories.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
check_packagesUse for questions like 'is my stack secure?' or 'do we have vulnerable packages?'.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 OS packages, Docker base images or your own code. Use check_runtime for Node.js and PHP versions.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
check_runtimeChecks a Node.js or PHP version against known security flaws in the runtime itself.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
Only reads 1Show 1 read-only tool
check_platformLists known security incidents at hosting, deployment and AI platforms, with what to do and a link to the source.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write4
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:23 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.keepmesecure.dev/mcp: tools/list returned 4 tools to an anonymous client, including check_packages (write), check_runtime (write), check_package (write)
Posture changes
- Nov 13, 2026
- Tools that change things, listed without credentials: 2 to 3
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 2 -> 3.View diff
- Tools that change things, listed without credentials: 2 to 3
Tools1 added, 1 changed.+1 added~1 changedView diff
- Added:check_runtimeChanges things
- Changed:check_packagesChanges thingsdescription
Tools1 added.+1 addedView diff
- Added:check_platformOnly reads
Install
Pinned to version 1.7.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http keep-me-secure https://mcp.keepmesecure.dev/mcpclaude mcp add --transport http keep-me-secure https://mcp.keepmesecure.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__keep-me-secure__check_platform"
],
"ask": [
"mcp__keep-me-secure__check_packages",
"mcp__keep-me-secure__check_runtime",
"mcp__keep-me-secure__check_package"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as keep-me-secure. Review it before you use it.
Capability tags behind 4 rules
- mcp__keep-me-secure__check_packages untrusted-input
- mcp__keep-me-secure__check_platform untrusted-input
- mcp__keep-me-secure__check_runtime untrusted-input
- mcp__keep-me-secure__check_package untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.robertkeus/keep-me-secure-mcp/verify?hash=845d4619ccdad70c5a7477e6994019964a6087829b8be134a962c56ac5ed6bb0" | jq -e '.changed == false'Pinned hash 845d4619ccda, from Nov 20, 2026, 10:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.robertkeus/keep-me-secure-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.robertkeus/keep-me-secure-mcp)Source: MCP Registry · repository. Synced Nov 6, 2026, 09:18 UTC.
Keep Me Secure MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Keep Me Secure MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Keep Me Secure MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Keep Me Secure MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Keep Me Secure MCP server have?
- 4 tools: 3 write, 1 read. check_packages, check_runtime, check_package and check_platform.
Does the Keep Me Secure MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Keep Me Secure MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Keep Me Secure MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 6, 2026. Every change is on this page and in its Atom feed.