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/brainslugs83/githubcopilotcli-vectormemorymcp/ghcp-cli-vector-memory-mcpgit clone --depth 1 https://github.com/BrainSlugs83/GithubCopilotCLI-VectorMemoryMCPWrote 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/brainslugs83/githubcopilotcli-vectormemorymcp/ghcp-cli-vector-memory-mcp)<a href="https://agentmods.dev/mcp/brainslugs83/githubcopilotcli-vectormemorymcp/ghcp-cli-vector-memory-mcp"><img src="https://agentmods.dev/badge/mcp/brainslugs83/githubcopilotcli-vectormemorymcp/ghcp-cli-vector-memory-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
ghcp-cli-vector-memory-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 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.
What it actually says
{ "ghcp-cli-vector-memory-mcp": { "command": "npx", "args": [ "-y", "ghcp-cli-vector-memory-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.
- 3d ago First seen · 9 lines scan A 24f0af44849e
ghcp-cli-vector-memory-mcp is an MCP server published in the GitHub repository BrainSlugs83/GithubCopilotCLI-VectorMemoryMCP (1 stars, last pushed 2mo 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
perenna
A lightweight, Git-backed permanent memory for AI agents. Runs locally from the perenna Python package. Needs 4 environment variables to run.
mcp-memory-server
Hosted memory for AI agents that learns from outcomes — one key across Claude, Cursor & ChatGPT. Runs locally from the @mnemoverse/mcp-memory-server npm package. Needs 2 environment variables to run.
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.
mcp-server
Persistent memory and virtual filesystem MCP server for AI agents. Runs locally from the @memofs/mcp-server npm package. Needs 2 environment variables to run.
memory
MCP server "memory", hosted remotely at memory.studiomeyer.io, as configured in studiomeyer-io/studiomeyer-memory.
sovseal-memory
Local-first, zero-knowledge AI memory across Claude, Cursor, and every MCP client. 0 RTT reads. Runs locally from the @sovseal/mcp-server npm package.