io.github.AIWerk/mcp-server-vault
io.github.AIWerk/mcp-server-vault
Is the io.github.AIWerk/mcp-server-vault MCP server down? Yes. It has given no valid answer since 2026-10-17: not found.
Bitwarden/Vaultwarden for agents: list tagged items, TOTP codes, one-time Sends, save new secrets.
not found down since 2026-10-17 · probed 2026-11-14 · unchanged since 2026-10-31
npm error 404 Note that you can also install from a npm error 404 tarball, folder, http url, or git url. npm error A complete log of this run can be found in: /
- Run it
- npx -y @aiwerk/mcp-server-vault@0.2.1 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/AIWerk/mcp-server-vault
- Registry
- active, updated 2026-06-24 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.AInoAKARI/keymaster-mcp · alive
- io.github.AIWerk/mcp-server-cal · not found
- io.github.AIWerk/mcp-server-clawhub · not found
- io.github.AIWerk/mcp-server-imap · not found
- io.github.AIWerk/mcp-server-shopify · not found
- io.github.AIWerk/mcp-server-wheel-size · not found
- io.github.AIWerk/mcp-server-wise · not found
- io.github.AJSMonty/adobe-mcp · needs env
Servers that mention vault.
- Hyperresearch ai.hyperresearch/hyperresearch · needs auth
- JustOnce ai.justonce/memory · needs auth
- ai.smithery/Hint-Services-obsidian-github-mcp · not found
- ai.smithery/sunub-obsidian-mcp-server · not found
- Insuro au.com.insuro/insuro · alive
- Arca build.arca.mcp/arca-mcp-server · needs auth
- cc.accrue/mcp · alive
- AgentBrink com.agentbrink.www/mcp · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-10-17, in every probe since then.
- The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.