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.
git clone --depth 1 https://github.com/Ar5en1c/context-guardianWrote 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/ar5en1c/context-guardian/context-guardian-mcp)<a href="https://agentmods.dev/mcp/ar5en1c/context-guardian/context-guardian-mcp"><img src="https://agentmods.dev/badge/mcp/ar5en1c/context-guardian/context-guardian-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/ar5en1c/context-guardian/context-guardian-mcp"><img src="https://agentmods.dev/badge/mcp/ar5en1c/context-guardian/context-guardian-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
context-guardian-mcp 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 10d 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-guardian-mcp": { "command": "npx", "args": [ "-y", "context-guardian-mcp" ] } }
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.
- 10d ago First seen · 9 lines scan A e4fa981efe6b
context-guardian-mcp is an MCP server published in the GitHub repository Ar5en1c/context-guardian (7 stars, last pushed 5mo 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
nexusmem
Local-first memory for AI coding agents: shell history with exit codes, git diffs, docs, MCP. Runs locally from the nexusmem npm package.
ctxmem
Git-native, shareable project memory for AI coding agents — fully local, no cloud. Runs locally from the ctxmem Python package.
trazum
Trazum as an MCP server: let an agent price and budget its own prompts before it sends them. Runs locally from the @trazum/mcp npm package.
lithium-kb
Fast, in-memory structured markdown knowledge base (.agent-kb/) with 2D neural graph visualization, live SSE activity stream, and MCP stdio integration. Runs locally from the @liulinnuha/lithium-kb npm package.
vectorlane
Open-source local vector memory engine for AI agents — ingest documents, chunk content, generate embeddings, search locally, return metadata/citations. Runs locally from the @talocode/vectorlane npm package.
linggen
MCP server "linggen", hosted remotely, as configured in linggen/linggen-memory.