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/hifriendbot/cogmemai-mcpWrote 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/hifriendbot/cogmemai-mcp/cogmemai)<a href="https://agentmods.dev/mcp/hifriendbot/cogmemai-mcp/cogmemai"><img src="https://agentmods.dev/badge/mcp/hifriendbot/cogmemai-mcp/cogmemai/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/hifriendbot/cogmemai-mcp/cogmemai"><img src="https://agentmods.dev/badge/mcp/hifriendbot/cogmemai-mcp/cogmemai.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
cogmemai 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
{
"cogmemai": {
"command": "npx",
"args": [
"-y",
"cogmemai-mcp"
],
"env": {
"COGMEMAI_API_KEY": ""
}
}
}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 · 12 lines scan A 24e063e0bbaf
cogmemai is an MCP server published in the GitHub repository hifriendbot/cogmemai-mcp (7 stars, last pushed 10d 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
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.
elesync
Local-first AI project workspace — a private vault where approved assistants share context, knowledge, and tasks. Runs locally from the elesync Python package. Needs 1 environment variable to run.
amber
Long-term memory for AI assistants. Hybrid retrieval, query expansion, auto-topics. Remote server at mcp.ambermem.com.
gnosem
Cross-vendor AI memory over MCP. One semantic store, readable and writeable from every MCP client. Remote server at gnosem.dev.
sthayi
Local-first AI memory over MCP. No account; you own the store. Runs locally from the sthayi npm package.
kireo
Long-term memory for Claude Code, Cursor and any MCP client, with a searchable web dashboard. Runs locally from the @kireo/mcp-server npm package. Needs 1 environment variable to run.