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/MnemeHQ/mnemeWrote 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/mnemehq/mneme/mneme)<a href="https://agentmods.dev/mcp/mnemehq/mneme/mneme"><img src="https://agentmods.dev/badge/mcp/mnemehq/mneme/mneme/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/mnemehq/mneme/mneme"><img src="https://agentmods.dev/badge/mcp/mnemehq/mneme/mneme.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
mneme 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 19d 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
{
"mneme": {
"command": "uvx",
"args": [
"mneme-hq",
"mneme-hq[mcp]==0.9.2"
],
"env": {}
}
}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.
- 19d ago Changed 25ec1e254ba3
- 24d ago First seen · 10 lines scan A e426c017d23a
mneme is an MCP server published in the GitHub repository MnemeHQ/mneme (27 stars, last pushed yesterday), 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-09-22.
Other mcp servers, from other repositories
no_human
Autonomous AI software-delivery orchestrator driving the Claude Agent SDK on your own Claude credentials. Runs locally from the no-human Python package.
no_human
MCP server "nohuman" as configured in no-human-ai/nohuman. Launched with nh mcp-serve.
graphlens-mcp
Semantic code graph MCP server for coding agents. Runs locally from the graphlens-mcp Python package.
opencode-export
MCP server "opencode-export" as configured in ZelinZhou-THU/opencode-export. Runs locally from the opencode-export Python package.
sequential-thinking
Adds a structured step-by-step reasoning tool the agent can call to break a problem into revisable thoughts. Runs locally from the @modelcontextprotocol/server-sequential-thinking npm package.
context-router
MCP server "context-router" as configured in mohankrishnaalavala/context-router. Launched with context-router mcp.