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/mashware/domain-memoryWrote 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/mashware/domain-memory/domain-memory)<a href="https://agentmods.dev/mcp/mashware/domain-memory/domain-memory"><img src="https://agentmods.dev/badge/mcp/mashware/domain-memory/domain-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/mashware/domain-memory/domain-memory"><img src="https://agentmods.dev/badge/mcp/mashware/domain-memory/domain-memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
domain-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 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
{
"domain-memory": {
"command": "npx",
"args": [
"-y",
"@mashware/domain-memory-server"
],
"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.
- 1mo ago First seen · 10 lines scan A 2acb1e2c0ddd
domain-memory is an MCP server published in the GitHub repository mashware/domain-memory (4 stars, last pushed 4mo 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
memorix
MCP server "memorix" as configured in AVIDS2/memorix. Launched with memorix serve --mode lite.
memorix
Local-first project memory with legacy MCP and 2026 discovery compatibility. Runs locally from the memorix npm package.
ai-context-kit
Lint, measure, and sync AI context files across Cursor, Claude Code, Copilot. Runs locally from the ai-context-kit npm package.
ai-mind-map
AI Mind Map — MCP server that reduces AI coding agent token usage by 80-99% through persistent codebase memory, knowledge graphs, and intelligent context management. Runs locally from the ai-mind-map npm package.
contextforge-mcp
Persistent memory MCP server for Claude Code, Cursor, and GitHub Copilot. Runs locally from the contextforge-mcp npm package. Needs 2 environment variables to run.
ironmem
MCP server "ironmem" as configured in BMC-INC/Iron-mem. Launched with ~/.ironmem/bin/ironmem mcp.