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/ceweldy/bitwarden-agent-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/ceweldy/bitwarden-agent-vault-mcp/bitwarden-agent-vault)<a href="https://agentmods.dev/mcp/ceweldy/bitwarden-agent-vault-mcp/bitwarden-agent-vault"><img src="https://agentmods.dev/badge/mcp/ceweldy/bitwarden-agent-vault-mcp/bitwarden-agent-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/ceweldy/bitwarden-agent-vault-mcp/bitwarden-agent-vault"><img src="https://agentmods.dev/badge/mcp/ceweldy/bitwarden-agent-vault-mcp/bitwarden-agent-vault.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
bitwarden-agent-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 11d 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
{
"bitwarden-agent-vault": {
"command": "node",
"args": [
"./mcp/server.mjs"
],
"cwd": ".",
"tool_timeout_sec": 300
}
}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.
- 11d ago First seen · 10 lines scan A eaa28d89ffc1
bitwarden-agent-vault is an MCP server published in the GitHub repository ceweldy/bitwarden-agent-vault-mcp (0 stars, last pushed 2d 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-09-01.
Other mcp servers, from other repositories
gsheets
Model Context Protocol (MCP) server for Google Sheets API integration. Runs locally from the mcp-gsheets npm package.
mcp-automem
Graph-vector memory for AI assistants using FalkorDB and Qdrant. Runs locally from the @verygoodplugins/mcp-automem npm package.
koma-gate-mcp
Classifies prompt injection, jailbreaks, and out-of-scope user input before agents act on it. Runs locally from the koma-gate-mcp npm package. Needs 6 environment variables to run.
lcu-mcp
MCP server "lcu-mcp" as configured in Triggered0/lcu-mcp. Runs locally from the lcu-mcp npm package.
orca-mcp
External MCP server for controlling Orca (worktrees, sessions, orchestration). Runs locally from the orca-mcp npm package. Needs 5 environment variables to run.
mcp-server-template
Production-grade MCP Server Template for TypeScript and Node.js. Runs locally from the @qmmughal/mcp-server-template npm package.