io.github.mrfentmen/bitwarden-mcp
bitwarden-mcp
Is the io.github.mrfentmen/bitwarden-mcp MCP server down? No. It answered initialize and tools/list in the probe of 2026-10-30.
Bitwarden public API: members, collections, groups, event logs.
alive probed 2026-11-14 · unchanged since 2026-10-30
- Run it
- npx -y @mrfentmen/bitwarden-mcp@1.0.1 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- bitwarden-mcp 1.0.0
- Capabilities
- tools
- Instructions
- none
- Of a 1M window
- <0.1 % of a 1M context window
- Count
- 431 tokens in Claude Opus 5.5, exact, measured 2026-10-16. With the Claude Code prefix mcp__…__ on each tool name: 487. The o200k_base estimate is 231. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/mrfentmen/premium-mcps
- Registry
- active, updated 2026-10-17 · registry entry
Most expensive tools
The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.87×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| get_events | 157 | 84 | 36 % |
| list_members | 95 | 51 | 22 % |
| list_collections | 90 | 48 | 21 % |
| list_groups | 90 | 48 | 21 % |
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.mrfentmen/bitget-mcp · alive
- io.github.mrfentmen/bithumb-mcp · alive
- io.github.mrfentmen/bitso-mcp · alive
- io.github.mrfentmen/bitstamp-mcp · alive
- io.github.mrfentmen/bkk-mcp · alive
- io.github.mrfentmen/blitzbasic-mcp · alive
- io.github.mrfentmen/blitzmax-mcp · alive
- io.github.mrfentmen/blizzard-mcp · alive
Servers that mention bitwarden.
- vaultgate io.github.adamrowles1996/vaultgate · needs your URL
- io.github.AIWerk/mcp-server-vault · not found
- Bitwarden Public API and Secrets Manager (unofficial) io.github.mguttmann/the-real-bitwarden-mcp · crashed on start
- Bitwarden com.foreverworks/bitwarden · alive
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
- The server answers initialize and tools/list. Nothing to fix.