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/videnovnebojsa/vault-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/videnovnebojsa/vault-mcp/vault-mcp-dev)<a href="https://agentmods.dev/mcp/videnovnebojsa/vault-mcp/vault-mcp-dev"><img src="https://agentmods.dev/badge/mcp/videnovnebojsa/vault-mcp/vault-mcp-dev/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/videnovnebojsa/vault-mcp/vault-mcp-dev"><img src="https://agentmods.dev/badge/mcp/videnovnebojsa/vault-mcp/vault-mcp-dev.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
vault-mcp-dev 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.
What it actually says
{
"vault-mcp-dev": {
"type": "http",
"url": "http://127.0.0.1:3782/mcp"
}
}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 · 6 lines scan A 01d3e10c6bce
vault-mcp-dev is an MCP server published in the GitHub repository videnovnebojsa/vault-mcp (2 stars, last pushed 4d 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
obsidian-mcp-server
Read, write, search, and surgically edit Obsidian notes, tags, and frontmatter via MCP. Runs locally from the obsidian-mcp-server npm package. Needs 10 environment variables to run.
obsidian-native-mcp
Zero-dependency MCP server for Obsidian vaults. Direct filesystem access — no Obsidian process or REST API plugin needed. Runs locally from the obsidian-native-mcp npm package.
notes-mcp
MCP for managing markdown notes with YAML frontmatter. Runs locally from the notes-mcp Python package.
obsidian-hybrid-search
Search Obsidian vaults with hybrid full-text, fuzzy, semantic, and graph retrieval. Runs locally from the obsidian-hybrid-search npm package. Needs 10 environment variables to run.
figma-mcp-rust
Figma MCP server in Rust: plugin bridge, no API token, no rate limits, 73 tools. Runs locally from the @alvinindra/figma-mcp-rust npm package.
ninjaone-mcp
MCP server "ninjaone-mcp" as configured in WYRE-AI/ninjaone-mcp. Runs in Docker (ghcr.io/wyre-ai/ninjaone-mcp:v2.3.0). Needs 6 environment variables to run.