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/mlorentedev/hiveWrote 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/mlorentedev/hive/hive-vault)<a href="https://agentmods.dev/mcp/mlorentedev/hive/hive-vault"><img src="https://agentmods.dev/badge/mcp/mlorentedev/hive/hive-vault/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/mlorentedev/hive/hive-vault"><img src="https://agentmods.dev/badge/mcp/mlorentedev/hive/hive-vault.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
hive-vault 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
{
"hive-vault": {
"command": "uvx",
"args": [
"hive-vault"
],
"env": {
"VAULT_PATH": "",
"HIVE_OLLAMA_ENDPOINT": "",
"OPENROUTER_API_KEY": "",
"HIVE_VAULT_SCOPES": ""
}
}
}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 · 14 lines scan A 27158bfb39cf
hive-vault is an MCP server published in the GitHub repository mlorentedev/hive (11 stars, last pushed today), 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-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.
knowns
MCP server "knowns" as configured in knowns-dev/knowns. Launched with knowns mcp --stdio.
vault-cortex
MCP server "vault-cortex" as configured in aliasunder/vault-cortex. Runs in Docker (ghcr.io/aliasunder/vault-cortex:0.54.3). Needs 24 environment variables to run.
furl
MCP server "furl" as configured in omar-y-abdi/furl-ctx. Launched with sh -c PATH="$PATH:$HOME/.local/bin:$HOME/.cargo/bin:/opt/homebrew/bin:/usr/local. Needs 3 environment variables to run.
obsidian-github-mcp
MCP server "obsidian-github-mcp" as configured in SarutobiSasuke8/obsidian-github-mcp. Runs locally from the @sarutobi-sasuke/obsidian-github-mcp npm package.
you-md
MCP server "you-md", hosted remotely at mcp.you.md, as configured in brainsparker/you.md.