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/lorismascio17/droste-memory/droste-memory-droste-memorygit clone --depth 1 https://github.com/lorismascio17/droste-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/lorismascio17/droste-memory/droste-memory-droste-memory)<a href="https://agentmods.dev/mcp/lorismascio17/droste-memory/droste-memory-droste-memory"><img src="https://agentmods.dev/badge/mcp/lorismascio17/droste-memory/droste-memory-droste-memory.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
droste-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 6d 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
{
"droste-memory": {
"command": "powershell.exe",
"args": [
"-NoProfile",
"-ExecutionPolicy",
"Bypass",
"-File",
".\\scripts\\run_mcp.ps1"
],
"env": {
"DROSTE_VISUALIZER_URL": "http://127.0.0.1:5000"
}
}
}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.
- 6d ago First seen · 15 lines scan A 6ea35a9d8f8f
droste-memory is an MCP server published in the GitHub repository lorismascio17/droste-memory (3 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
sverklo
MCP server "sverklo" as configured in sverklo/sverklo. Launched with /opt/homebrew/bin/sverklo .. Needs 1 environment variable to run.
ivygrep
MCP server "ivygrep" as configured in bvolpato/ivygrep. Launched with https://github.com/bvolpato/ivygrep/releases/download/v1.2.9/ivygrep-mcp-v1.2.9..
repo-context-forge
MCP server "repo-context-forge" as configured in negativexq/repo-context-forge. Runs locally from the repo-context-forge Python package.
codex-memory-intelligence
Local-first project memory, dependency and impact intelligence, evidence-driven change history, and session continuation for AI coding agents. Runs locally from the codex-memory-intelligence npm package.
codebase-memory-mcp
Codebase knowledge graph for AI agents — 159 languages, sub-ms queries, 99% fewer tokens. Runs locally from the codebase-memory-mcp npm package.
memorywhale
MCP server "memorywhale" as configured in wuisabel-gif/MemWhale. Launched with mw-mcp.