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/joshylchen/zettelkastenWrote 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/joshylchen/zettelkasten/zettelkasten-assistant)<a href="https://agentmods.dev/mcp/joshylchen/zettelkasten/zettelkasten-assistant"><img src="https://agentmods.dev/badge/mcp/joshylchen/zettelkasten/zettelkasten-assistant/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/joshylchen/zettelkasten/zettelkasten-assistant"><img src="https://agentmods.dev/badge/mcp/joshylchen/zettelkasten/zettelkasten-assistant.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
zettelkasten-assistant 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 · 14 lines scan A 2baa42dff181
zettelkasten-assistant is an MCP server published in the GitHub repository joshylchen/zettelkasten (39 stars, last pushed 11mo ago), with no licence file. 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-30.
Other mcp servers, from other repositories
hypermnesia-mcp
Scientifically-grounded memory system based on computational neuroscience research. Runs locally from the hypermnesia-mcp Python package.
rag-rat
CLI and MCP entrypoint for indexing repositories into local source, graph, history, and memory evidence. Runs locally from the @rag-rat/bin npm package.
cgr-capture
MCP server that captures agent judgments and outcomes as CGR substrate on GRAFOMEM Cloud. Runs locally from the grafomem-cgr Python package. Needs 6 environment variables to run.
neverinfamous-memory-journal-mcp
A MCP server built for developers enabling Git based project management with project and personal… Remote server at server.smithery.ai.
server-memory
The agentage Memory MCP server: exposes your local vaults as the frozen 6 memory tools over stdio. The open, cross-vendor counterpart to @modelcontextprotocol/server-memory. Runs locally from the @agentage/server-memory npm package.
forkmind
Branchable LLM history DAG + encrypted context capsules agents can save, restore, and crypto-shred. Runs locally from the forkmind npm package.