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/fpolica91/memfedWrote 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/fpolica91/memfed/memfed-cli)<a href="https://agentmods.dev/mcp/fpolica91/memfed/memfed-cli"><img src="https://agentmods.dev/badge/mcp/fpolica91/memfed/memfed-cli/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/fpolica91/memfed/memfed-cli"><img src="https://agentmods.dev/badge/mcp/fpolica91/memfed/memfed-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
memfed-cli 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
{ "memfed-cli": { "command": "npx", "args": [ "-y", "memfed-cli" ] } }
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 First seen · 9 lines scan A 3b761de45977
memfed-cli is an MCP server published in the GitHub repository fpolica91/memfed (0 stars, last pushed 3mo ago), licensed Apache-2.0. 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
klypix-mcp
Active state management for multi-agent coding: a shared, versioned project brain over MCP. Runs locally from the klypix-mcp npm package. Needs 1 environment variable to run.
vulcanus
A validated Markdown memory vault your coding agent can recall, project by project. Runs locally from the @sunsato/vulcanus npm package.
memory-engine-mcp
MCP server "memory-engine-mcp" as configured in SimoneB79/memory-engine-mcp. Runs in Docker (ghcr.io/simoneb79/memory-engine-mcp:1.5.3). Needs 3 environment variables to run.
memento-vault
MCP server "memento-vault" as configured in sandsower/memento-vault. Runs locally from the memento-vault Python package.
mcp-memory-suite
MCP server "mcp-memory-suite" as configured in sscctv/mcp-memory-suite. Runs locally from the mcp-memory-suite Python package.
ori-memory
Persistent memory infrastructure for AI agents. Identity, knowledge graph, and search. Runs locally from the ori-memory npm package.