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/Wolstapp/stillvault-mcpWrote 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/wolstapp/stillvault-mcp/stillvault)<a href="https://agentmods.dev/mcp/wolstapp/stillvault-mcp/stillvault"><img src="https://agentmods.dev/badge/mcp/wolstapp/stillvault-mcp/stillvault/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/wolstapp/stillvault-mcp/stillvault"><img src="https://agentmods.dev/badge/mcp/wolstapp/stillvault-mcp/stillvault.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
stillvault 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 8d 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
{
"stillvault": {
"command": "npx",
"args": [
"-y",
"@wolstapp/stillvault-mcp"
],
"env": {
"STILLVAULT_AGENT": "claude-prod",
"STILLVAULT_TENANT": "<your-org-id>"
}
}
}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.
- 8d ago First seen · 13 lines scan A 8e713e2936ef
stillvault is an MCP server published in the GitHub repository Wolstapp/stillvault-mcp (0 stars, last pushed 2mo 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
trusty-squire
Trusty Squire signs up / in to websites for you so you don’t have to. Runs locally from the @trusty-squire/mcp npm package.
mcp
Credential broker that signs your AI agent up to SaaS dev tools, within a signed spending mandate. Runs locally from the @trusty-squire/mcp npm package.
elicitly-free-dev
MCP server "elicitly-free-dev" as configured in elicitly/elicitly. Runs packages/elicitly/dist/cli.mjs with node.
elicitly-free
Local (stdio) MCP server that gives your prompts and Agent Skills MCP elicitation — human-in-the-loop dialogs (elicitconfirm, elicitform) and the elicitdoctor capability report, with no server of your own. Runs locally from the elicitly npm package.
veil-mcp
Agent-native shell as an MCP server — quiet-by-default, addressable detail, effects-as-data, opt-in sandbox/trace. Built for LLM agents (Claude Code), not humans at a terminal. Runs locally from the veil-mcp npm package.
fs-governed
MCP server "fs-governed" as configured in hishamalward/mcpclerk. Launched with mcpclerk serve --policy examples/policy.filesystem.yaml --log audit/mcpclerk.jso.