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/zd87pl/slm-vaultInstalling this writes the configuration, not the program: `python` runs a file from the repository, so clone it first and make the path in the command match where you put it.
Wrote 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/zd87pl/slm-vault/mcp_server-enclave)<a href="https://agentmods.dev/mcp/zd87pl/slm-vault/mcp_server-enclave"><img src="https://agentmods.dev/badge/mcp/zd87pl/slm-vault/mcp_server-enclave/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/zd87pl/slm-vault/mcp_server-enclave"><img src="https://agentmods.dev/badge/mcp/zd87pl/slm-vault/mcp_server-enclave.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
enclave 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
{
"enclave": {
"command": "python",
"args": [
"-m",
"advanced_vault.mcp_server"
],
"env": {
"VAULT_PATH": "~/.vault"
}
}
}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 · 12 lines scan A 9690dc0986b4
enclave is an MCP server published in the GitHub repository zd87pl/slm-vault (2 stars, last pushed 27d 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
remnic
MCP server "remnic", hosted remotely at localhost, as configured in joshuaswarren/remnic.
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.
agent-magnet
Self-learning memory infrastructure for AI products. Runs locally from the agent-magnet Python package. Needs 6 environment variables to run.
usrcp
Encrypted local ledger of structured user state, shared across every MCP-aware AI tool. Runs locally from the usrcp npm package. Needs 1 environment variable to run.
mcp
Memory the human governs, on their own machine, plus what other coding agents here wrote. Runs locally from the @mnemosyne_os/mcp npm package. Needs 3 environment variables to run.
forkmind
Branchable LLM history DAG + encrypted context capsules agents can save, restore, and crypto-shred. Runs locally from the forkmind npm package.