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/muyen/vibe-to-prodWrote 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/muyen/vibe-to-prod/memory)<a href="https://agentmods.dev/mcp/muyen/vibe-to-prod/memory"><img src="https://agentmods.dev/badge/mcp/muyen/vibe-to-prod/memory/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/muyen/vibe-to-prod/memory"><img src="https://agentmods.dev/badge/mcp/muyen/vibe-to-prod/memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
memory 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 3d 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.
This is a copy
92% identical to memory — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"memory": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-memory"
]
}
}What else .mcp.json configures
This page is one entry in a file that holds 5. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 3d ago First seen · 9 lines scan A 2ab64fbe22b4
memory is an MCP server published in the GitHub repository muyen/vibe-to-prod (33 stars, last pushed 6mo 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. It is 92% identical to memory, differing in 2 lines, and is treated as a copy.
Other mcp servers, from other repositories
mcp-memory
MCP server for enabling memory for Claude through a knowledge graph. Runs locally from the mcp-memory-py Python package.
fidelis-memory
Fidelis Memory: faithful agent memory with zero-LLM retrieval by default. By Hermes Labs. Runs locally from the fidelis-memory Python package. Needs 1 environment variable to run.
cgr-capture
MCP server that captures agent judgments and outcomes as CGR substrate on GRAFOMEM Cloud. Runs locally from the grafomem-cgr Python package. Needs 6 environment variables to run.
server-memory
The agentage Memory MCP server: exposes your local vaults as the frozen 6 memory tools over stdio. The open, cross-vendor counterpart to @modelcontextprotocol/server-memory. Runs locally from the @agentage/server-memory npm package.
june-mcp
MCP server for Junê — give any MCP agent (Claude Desktop, Claude Code, …) a shared, cited knowledge-graph memory backed by a June endpoint. Runs locally from the june-mcp Python package. Needs 13 environment variables to run.
recall-mcp
Recall (recall.it) — your AI knowledge base / 'second brain'. Via the official API: semantic search. Remote server at api.mcp.ai.