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/gitwork-oss/memgrepInstalling this writes the configuration, not the program: `${userHome}/.nvm/versions/node/v20.20.2/bin/memgrep` has to be on your PATH already, or the server will not start.
Wrote 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/gitwork-oss/memgrep/memgrep)<a href="https://agentmods.dev/mcp/gitwork-oss/memgrep/memgrep"><img src="https://agentmods.dev/badge/mcp/gitwork-oss/memgrep/memgrep/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/gitwork-oss/memgrep/memgrep"><img src="https://agentmods.dev/badge/mcp/gitwork-oss/memgrep/memgrep.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
memgrep 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 1mo 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
{
"memgrep": {
"command": "${userHome}/.nvm/versions/node/v20.20.2/bin/memgrep",
"args": [
"serve"
]
}
}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.
- 1mo ago Changed · -1 lines c13706251bb7
- 1mo ago First seen · 9 lines scan A fb4d15623f93
memgrep is an MCP server published in the GitHub repository gitwork-oss/memgrep (2 stars, last pushed 1mo 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
stremai
StremAI MCP: shared memory for AI coding agents. Connected agents can recall. OAuth + local stdio. Runs locally from the aiagentsbay-mcp npm package.
krimto
Memory for AI coding agents — markdown in your own git, not a vendor database. Apache-2.0. Runs locally from the @krimto-labs/krimto npm package.
levh
Local-first memory layer for AI agents and humans. Runs locally from the levh Python package.
tokenmizer
MCP server "tokenmizer" as configured in Shweta-Mishra-ai/tokenmizer. Launched with tokenmizer-mcp. Needs 2 environment variables to run.
claude-faf-mcp
Persistent project context for Claude. IANA-registered .faf format. Runs locally from the claude-faf-mcp npm package.
superskill
One-entry orchestrator for coding agents: jailed vault, FTS knowledge graph, 18-axis review, in-harness Chrome QA. Curated packs — not a 90k-skill dump. Runs locally from the superskill npm package.