Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add mcp/jarmstrong158/context-keeper-remote/context-keeper-remotegit clone --depth 1 https://github.com/jarmstrong158/context-keeper-remoteWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/jarmstrong158/context-keeper-remote/context-keeper-remote)<a href="https://agentmods.dev/mcp/jarmstrong158/context-keeper-remote/context-keeper-remote"><img src="https://agentmods.dev/badge/mcp/jarmstrong158/context-keeper-remote/context-keeper-remote.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
context-keeper-remote scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"context-keeper-remote": {
"url": "https://context-keeper-remote.{account}.workers.dev/mcp/{token}",
"type": "streamable-http"
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 6 lines scan A 5c4aaad062b5
context-keeper-remote is an MCP server published in the GitHub repository jarmstrong158/context-keeper-remote (0 stars, last pushed 28d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
agentsync-remote
Cloudflare Worker remote transport for agentsync. MCP 2026-07-28, dual-era, stateless. Remote server at agentsync-remote.{account}.workers.dev.
prism-coder
Session memory for coding agents: local-first recall, drift detection, on-device inference. Runs locally from the prism-mcp-server npm package. Needs 8 environment variables to run.
prism-mcp
Persistent session memory for AI coding agents that never leaves your machine — including the on-device model that reasons over it. Restores your prior decisions, open TODOs, and changed files across sessions; adds associative recall of related past work. Runs locally from the prism-mcp-server npm package. Needs 1…
mcp-ts-core
Agent-native TypeScript framework for building MCP servers with declarative definitions. Runs locally from the @cyanheads/mcp-ts-core npm package. Needs 1 environment variable to run.
state-memory-mcp
Deterministic, persistent graph server for tracking workflow state, decisions, and blockers. Runs locally from the @putervision/state-memory-mcp npm package.
xmemo
Shared, governed long-term memory for AI agents across tools and sessions via MCP and REST. Runs locally from the @xmemo/client npm package. Needs 2 environment variables to run.