{ "data": { "a": { "slug": "bitwarden-secrets-manager", "name": "Bitwarden Secrets Manager", "vendor": "Bitwarden", "vendorUrl": "https://bitwarden.com/products/secrets-manager/", "kind": "sdk", "category": "secrets", "summary": "End-to-end encrypted secrets store from the Bitwarden password manager company.", "url": "https://www.anchorterminal.com/tools/bitwarden-secrets-manager", "markdownUrl": "https://www.anchorterminal.com/tools/bitwarden-secrets-manager.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/bitwarden-secrets-manager.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/bitwarden-secrets-manager.json", "repo": "https://github.com/bitwarden/sdk-sm", "license": "Bitwarden's own SDK licence (SDK and bws), GPL-3.0 (Password Manager MCP server), platform closed", "transports": [ "http" ], "remoteUrl": "https://api.bitwarden.com", "packages": [ { "registry": "npm", "name": "@bitwarden/sdk-napi" }, { "registry": "pypi", "name": "bitwarden-sdk" } ], "auth": "api-key", "authNotes": "A machine account access token (`0.\u003cuuid\u003e.\u003cclient secret\u003e:\u003cencryption key\u003e`) goes in `BWS_ACCESS_TOKEN` or `--access-token`. The SDK exchanges the client secret at identity.bitwarden.com, then decrypts secrets locally with the key embedded in the token, so a plain curl can't read a value. Tokens are shown once, never stored server-side, and can expire on a date you set (default never).", "pricing": "freemium", "pricingNotes": "Secrets Manager has a free plan (2 users, 3 projects, 3 machine accounts, unlimited secrets, no event logs) and paid Teams and Enterprise plans. Teams $6 per user a month with 20 machine accounts included, Enterprise $12 per user a month with 50, and $1 a month per extra machine account on either. Secret storage, projects and users are unlimited on paid plans, and event logs come with Teams and Enterprise. A 14-day trial is on the pricing page; neither page says whether a card is needed. The product page lists self-hosting on Enterprise, while the plans help page still says coming soon (https://bitwarden.com/pricing/business/, https://bitwarden.com/help/secrets-manager-plans/).", "priceSummary": "$6 / seat-mo", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 480, "npmWeekly": 24038, "pypiWeekly": 25331, "asOf": "2026-09-30" }, "docsUrl": "https://bitwarden.com/help/secrets-manager-overview/", "capabilities": [ "secrets.store", "secrets.machine-identity", "secrets.audit", "secrets.self-host" ], "tags": [ "hosted", "self-hosted", "freemium", "source-available", "typescript", "python", "go", "enterprise", "eu" ], "lastRelease": "2026-05-22", "graded": true, "anchor": { "graded": true, "score": 57.1, "grade": "C", "agentReady": false, "rank": 297, "ranked": true, "rankOf": 452, "categoryRank": 8, "methodology": "0.3", "run": "2026-10-01", "scores": { "ergonomics": 52, "maintenance": 36, "payments": 25, "reliability": 71, "schema": 53, "security": 76, "transparency": 71 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "End-to-end encrypted, decrypted only on the client that holds the token. No release since 22 May 2026, and the npm SDK is still 1.0.0 from September 2024.", "strengths": [ "End-to-end encrypted, decrypted only on the client that holds the token", "Machine accounts at $1 a month each, 3 on the free plan, with Can read or Can read, write per project", "Per-machine-account event logs of secret access, retained indefinitely, on Teams and Enterprise", "SOC 2 Type II, ISO 27001 and a HackerOne bounty", "US or EU cloud, with self-hosting on Enterprise" ], "weaknesses": [ "No release since 22 May 2026, and the npm SDK is still 1.0.0 from September 2024", "33 open issues, mostly bugs, including a Python SDK segfault open since July 2025", "Revoked tokens keep working for up to an hour on already-authenticated machines", "No rotation, dynamic secrets, workload identity login or MCP server for Secrets Manager", "SDK and CLI under Bitwarden's own SDK licence, and no OpenAPI for the secrets API" ], "agentNotes": [ "Create one machine account per agent with Can read on one project, and give its token an expiry date rather than the default of never", "Run the agent under `bws run -- \u003ccmd\u003e` so secrets arrive as environment variables and aren't written to disk or into the context", "Fetch with `bws secret list \u003cproject-id\u003e --output json` once per run; `bws secret get` needs the secret's UUID, not its name", "Set BWS_SERVER_URL for an EU organisation or a self-hosted server; the default is the US cloud", "Rotate the secret's value as well as revoking the token in an emergency, since a live session can read for up to an hour" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 2.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.3", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 57.1 } ], "editorialScores": { "ergonomics": 52, "maintenance": 36, "payments": 25, "reliability": 71, "schema": 53, "security": 76, "transparency": 52 }, "provenanceScore": 90 }, "connect": { "install": "cargo install bws --locked # or: curl https://bws.bitwarden.com/install | sh, npm install @bitwarden/sdk-napi, pip install bitwarden-sdk", "http": "export BWS_ACCESS_TOKEN=\"$BWS_ACCESS_TOKEN\"\nbws secret list \"$BWS_PROJECT_ID\" # values are end-to-end encrypted, so the CLI or SDK decrypts; plain curl can't" }, "letme": { "capability": "https://letme.dev/secrets.store", "tool": "https://letme.dev/bitwarden-secrets-manager" }, "area": "agent-runtime", "unitPrices": [ { "item": "Secrets Manager, Teams", "unit": "seat-month", "usd": 6, "note": "20 machine accounts included" }, { "item": "Secrets Manager, Enterprise", "unit": "seat-month", "usd": 12, "note": "50 machine accounts included" }, { "item": "Extra machine account", "unit": "account-month", "usd": 1 } ], "provenance": { "legalEntity": "Bitwarden Inc. (terms name 8bit Solutions LLC, wholly owned by Bitwarden Inc.)", "domain": "bitwarden.com", "domainRegistered": "2015-11-16", "endpointOnVendorDomain": true, "terms": "https://bitwarden.com/terms/", "privacy": "https://bitwarden.com/privacy/", "statusPage": "https://status.bitwarden.com", "changelog": "https://github.com/bitwarden/sdk-sm/releases", "securityTxt": "none", "checked": "2026-10-01", "notes": [ "Terms dated 1 June 2017 name 8bit Solutions LLC, a Delaware company wholly owned by Bitwarden Inc. The privacy policy (revised April 2024) gives Bitwarden Inc., 1 North Calle Cesar Chavez, Suite 102, Santa Barbara, CA 93103, with data stored primarily in the EEA and United States.", "bitwarden.com/.well-known/security.txt returned 404 on 30 September 2026; the SDK repository's SECURITY.md points to HackerOne.", "status.bitwarden.com runs on Hund.io. Since 3 July 2026 it shows five planned maintenance windows and one unscheduled incident, elevated US API error rates for 38 minutes on 29 September.", "The compliance page claims SOC 2 Type II, SOC 3, ISO 27001 and HIPAA, with data on Azure in the US or EU.", "The crate changelogs in sdk-sm stop at 1.0.0 (September 2024); later releases are only described on GitHub." ], "score": 90 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/bitwarden-secrets-manager.json", "live": { "slug": "bitwarden-secrets-manager", "probe": { "target": "https://api.bitwarden.com", "method": "get", "lastAt": "2026-10-04T23:32:44.11508903Z", "lastOk": true, "lastStatus": 404, "lastMs": 291, "authRequired": false, "uptime24h": 99.26, "uptime30d": 97.32, "p50ms24h": 130, "p95ms24h": 328, "samples24h": 272, "samples30d": 895, "days": [ { "date": "2026-10-01", "probes": 109, "ok": 102 }, { "date": "2026-10-02", "probes": 248, "ok": 239 }, { "date": "2026-10-03", "probes": 271, "ok": 265 }, { "date": "2026-10-04", "probes": 267, "ok": 265 } ] }, "vendorStatus": { "page": "https://status.bitwarden.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-04T21:39:50.88623142Z" }, "versions": [ { "registry": "github", "name": "bitwarden/sdk-sm", "version": "python-v2.1.0", "released": "2026-05-21", "seenAt": "2026-10-04T16:22:18.502566508Z" }, { "registry": "npm", "name": "@bitwarden/sdk-napi", "version": "1.0.0", "seenAt": "2026-10-04T16:22:17.909661383Z" }, { "registry": "pypi", "name": "bitwarden-sdk", "version": "2.1.0", "released": "2026-05-21", "seenAt": "2026-10-04T16:22:18.317866887Z" } ], "githubStars": 480, "npmWeekly": 25074, "pypiWeekly": 27867, "securityTxt": { "url": "https://bitwarden.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-04T15:15:46.220509573Z" }, "domain": { "domain": "bitwarden.com", "registered": "2015-11-16", "source": "https://rdap.verisign.com/com/v1/domain/bitwarden.com", "checkedAt": "2026-10-04T13:03:43.146799125Z" }, "pages": [ { "url": "https://bitwarden.com/pricing/business/", "kind": "pricing", "status": 304, "checkedAt": "2026-10-04T15:41:30.968841046Z", "changedAt": "2026-10-03T15:29:42.809015327Z", "fingerprint": "8d0a67e9a051" }, { "url": "https://bitwarden.com/privacy/", "kind": "privacy", "status": 200, "checkedAt": "2026-10-04T15:41:32.998627256Z", "changedAt": "2026-10-04T15:41:32.998627256Z", "fingerprint": "612dca4ba267" }, { "url": "https://bitwarden.com/terms/", "kind": "terms", "status": 304, "checkedAt": "2026-10-04T15:41:35.010005656Z", "changedAt": "2026-10-03T15:29:46.855070037Z", "fingerprint": "662bff2efe7c" } ], "updatedAt": "2026-10-04T23:32:44.11508903Z" } }, "b": { "slug": "hashicorp-vault", "name": "HashiCorp Vault + Vault MCP Server", "vendor": "HashiCorp (IBM)", "vendorUrl": "https://developer.hashicorp.com/vault", "kind": "http-api", "category": "secrets", "summary": "Secrets management platform for storing credentials and controlling application access.", "url": "https://www.anchorterminal.com/tools/hashicorp-vault", "markdownUrl": "https://www.anchorterminal.com/tools/hashicorp-vault.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/hashicorp-vault.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/hashicorp-vault.json", "repo": "https://github.com/hashicorp/vault", "license": "BUSL-1.1 (Vault), MPL-2.0 (MCP server)", "transports": [ "http", "stdio", "streamable-http" ], "packages": [], "auth": "mixed", "authNotes": "Every request carries a Vault token in `X-Vault-Token` (or as an HTTP bearer token). Machines get a token from an auth method such as AppRole, Kubernetes, JWT/OIDC, AWS, GCP, Azure, TLS certificates and more. Enterprise 2.0.3+ lets a registered agent present an OAuth 2.0 JWT from your identity provider directly, with RAR claims (RFC 9396) narrowing paths. The MCP server reads VAULT_ADDR, VAULT_TOKEN and VAULT_NAMESPACE, or takes them as headers in HTTP mode.", "pricing": "freemium", "pricingNotes": "Vault Community is free to run under the BUSL-1.1, which forbids selling a competing hosted product. HCP Vault Dedicated is hourly per cluster on the IBM price list. Development extra small $0.61644 an hour, Essentials small $1.57799, medium $3.16299, large $7.48857, Standard small $1.84299, medium $3.69099, large $9.40599, plus $72.92 a month per product client. Prices are indicative and exclude tax. Vault Enterprise self-managed is quoted, and the 2.1.0 licence added Agentic IAM terms. HCP has a $500 pay-as-you-go credit (https://www.ibm.com/products/hashicorp/pricing, https://www.hashicorp.com/en/pricing).", "priceSummary": "Freemium", "where": "local", "x402": { "level": "no", "endpoints": [] }, "toolCount": 16, "popularity": { "githubStars": 36234, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://developer.hashicorp.com/vault/docs", "capabilities": [ "secrets.store", "secrets.rotate", "secrets.machine-identity", "secrets.audit", "secrets.self-host", "auth.agent-identity" ], "tags": [ "hosted", "self-hosted", "source-available", "freemium", "mcp", "local", "go", "enterprise", "eu" ], "lastRelease": "2026-09-16", "graded": true, "anchor": { "graded": true, "score": 64.4, "grade": "B", "agentReady": false, "rank": 184, "ranked": true, "rankOf": 452, "categoryRank": 7, "methodology": "0.3", "run": "2026-10-01", "scores": { "ergonomics": 64, "maintenance": 77, "payments": 30, "reliability": 71, "schema": 74, "security": 86, "transparency": 83 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": -5, "negativeNotes": [ "-4: The official Vault MCP server fixed cross-user credential inheritance through a shared MCP session ID on 2026-07-28 and an SSRF through a VAULT_ADDR query parameter on 2026-08-11, but the newest binary and Docker image are still 0.2.0 from 2025-09-24 and no advisory was published (https://github.com/hashicorp/vault-mcp-server/commits/main, https://releases.hashicorp.com/vault-mcp-server/)", "-1: Vault 2.0.3 (2026-06-17) fixed a LIST ACL bypass where a trailing slash skipped a more specific deny rule; fixed and documented in the changelog, so it decays (https://github.com/hashicorp/vault/blob/main/CHANGELOG.md)" ], "verdict": "Dynamic secrets with leases, so a database or cloud credential can live for one agent run and be revoked after. The MCP server's newest build is 0.2.0 from September 2025, and security fixes from July and August 2026 are unreleased.", "strengths": [ "Dynamic secrets with leases, so a database or cloud credential can live for one agent run and be revoked after", "Path policies with explicit deny, audit devices on every edition, and Agent Registry with ceiling policies on Enterprise", "Auth methods for every major cloud, Kubernetes, JWT/OIDC and AppRole", "Three releases between 4 August and 16 September 2026 with a dated changelog that names each CVE fixed", "Each server generates its own OpenAPI document at /v1/sys/internal/specs/openapi" ], "weaknesses": [ "The MCP server's newest build is 0.2.0 from September 2025, and security fixes from July and August 2026 are unreleased", "Agentic IAM, control groups and the OAuth resource server are Enterprise only", "BUSL-1.1, not an OSI licence, and HCP Vault Secrets was retired within two years of launch", "No llms.txt, and the only official client library is Go", "HCP client pricing ($72.92 a client a month) can dwarf the cluster price for many agents, and no SLA is published" ], "agentNotes": [ "Prefer a dynamic secret (database, AWS, GCP engines) over a KV read; the lease expires with the run and revoke is one call", "Log in with AppRole or Kubernetes auth and keep the token for its TTL. Renew with auth/token/renew-self rather than logging in per request", "For KV v2, GET /v1/\u003cmount\u003e/data/\u003cpath\u003e and read data.data, and pass cas on writes so a retry can't overwrite a newer version", "If you must use the MCP server, build it from main rather than running the 0.2.0 image, run it over stdio, and give it a token limited to one mount", "Ask your operator to set enable_rate_limit_response_headers on the quota so a 429 carries Retry-After" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 2, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.3", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 64.4 } ], "editorialScores": { "ergonomics": 64, "maintenance": 77, "payments": 30, "reliability": 71, "schema": 74, "security": 86, "transparency": 65 }, "provenanceScore": 100 }, "connect": { "install": "docker run --rm -p 8200:8200 hashicorp/vault server -dev # or download vault-mcp-server from releases.hashicorp.com", "http": "curl -H \"X-Vault-Token: $VAULT_TOKEN\" \"$VAULT_ADDR/v1/secret/data/myapp\"", "claudeCode": "claude mcp add vault -e VAULT_ADDR=$VAULT_ADDR -e VAULT_TOKEN=$VAULT_TOKEN -- vault-mcp-server stdio", "config": { "mcpServers": { "vault": { "args": [ "run", "-i", "--rm", "-e", "VAULT_ADDR", "-e", "VAULT_TOKEN", "hashicorp/vault-mcp-server" ], "command": "docker", "env": { "VAULT_ADDR": "${VAULT_ADDR}", "VAULT_TOKEN": "${VAULT_TOKEN}" } } } } }, "letme": { "capability": "https://letme.dev/secrets.store", "tool": "https://letme.dev/hashicorp-vault" }, "sameCompany": [ "terraform-mcp" ], "area": "agent-runtime", "unitPrices": [ { "item": "HCP Vault Dedicated, product client", "unit": "account-month", "usd": 72.92, "note": "Per client a month, Essentials and Standard" } ], "provenance": { "legalEntity": "HashiCorp, Inc. (an IBM company)", "domain": "hashicorp.com", "domainRegistered": "2011-04-30", "endpointOnVendorDomain": true, "terms": "https://www.hashicorp.com/en/terms-of-service", "privacy": "https://www.hashicorp.com/en/privacy", "statusPage": "https://status.hashicorp.com", "changelog": "https://github.com/hashicorp/vault/blob/main/CHANGELOG.md", "securityTxt": "valid", "checked": "2026-10-01", "notes": [ "The website terms name HashiCorp, Inc. and were last updated March 2018. The privacy policy (20 April 2026) gives HashiCorp, an IBM Company, c/o 1 North Castle Drive, Armonk, New York, and notes the IBM acquisition closed on 27 February 2025.", "security.txt has Contact, Policy and Encryption but no Expires field.", "HCP prices come from the IBM price table and are marked indicative, varying by country.", "status.hashicorp.com runs on incident.io. From 1 July to 1 October 2026 it posted nothing against HCP Vault Dedicated; it did post a DR cluster creation failure on HCP (6 August) and a releases.hashicorp.com outage (26 September).", "The Vault MCP server's newest published build is 0.2.0 (24 September 2025) on releases.hashicorp.com and Docker Hub, although its VERSION file and changelog say 0.2.1." ], "score": 100 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/hashicorp-vault.json", "live": { "slug": "hashicorp-vault", "vendorStatus": { "page": "https://status.hashicorp.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-04T23:27:50.15354632Z" }, "versions": [ { "registry": "github", "name": "hashicorp/vault", "version": "v2.1.1", "released": "2026-09-16", "seenAt": "2026-10-04T16:29:29.320950791Z" } ], "githubStars": 36339, "securityTxt": { "url": "https://hashicorp.com/.well-known/security.txt", "state": "unknown", "checkedAt": "2026-10-04T15:16:00.556489725Z" }, "domain": { "domain": "hashicorp.com", "registered": "2011-04-30", "source": "https://rdap.verisign.com/com/v1/domain/hashicorp.com", "checkedAt": "2026-10-04T13:10:23.718306751Z" }, "pages": [ { "url": "https://raw.githubusercontent.com/hashicorp/vault/main/CHANGELOG.md", "kind": "deprecations", "status": 304, "checkedAt": "2026-10-04T15:47:41.235618427Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "0620845f2f7e" }, { "url": "https://www.ibm.com/support/pages/hcp-vault-secrets-end-life", "kind": "deprecations", "status": 304, "checkedAt": "2026-10-04T15:50:50.575718841Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e24e2e2b51c3" }, { "url": "https://www.hashicorp.com/en/pricing", "kind": "pricing", "status": 429, "checkedAt": "2026-10-04T15:50:36.37620806Z", "changedAt": "0001-01-01T00:00:00Z" }, { "url": "https://www.ibm.com/products/hashicorp/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-04T15:50:46.127664694Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "0e262eb503c4" }, { "url": "https://www.hashicorp.com/en/privacy", "kind": "privacy", "status": 429, "checkedAt": "2026-10-04T15:50:38.389849123Z", "changedAt": "0001-01-01T00:00:00Z" }, { "url": "https://www.hashicorp.com/en/terms-of-service", "kind": "terms", "status": 429, "checkedAt": "2026-10-04T15:50:40.386204192Z", "changedAt": "0001-01-01T00:00:00Z" } ], "updatedAt": "2026-10-04T23:27:50.15354632Z" } }, "summary": "HashiCorp Vault + Vault MCP Server has a score of 64.4 (B) against Bitwarden Secrets Manager's 57.1 (C). Both do secrets store. The largest gap is maintenance \u0026 community, 41 points." }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-hashicorp-vault", "json": "https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-hashicorp-vault.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-hashicorp-vault.md", "slim": "https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-hashicorp-vault.min.md" }, "markdown": "HashiCorp Vault + Vault MCP Server has a score of 64.4 (B) against Bitwarden Secrets Manager's 57.1 (C). Both do secrets store. The largest gap is maintenance \u0026 community, 41 points.\n\n- Bitwarden Secrets Manager: grade C, 57.1/100, rank #297 of 452. Markdown https://www.anchorterminal.com/tools/bitwarden-secrets-manager.md · JSON https://www.anchorterminal.com/api/v1/tools/bitwarden-secrets-manager.json\n- HashiCorp Vault + Vault MCP Server: grade B, 64.4/100, rank #184 of 452. Markdown https://www.anchorterminal.com/tools/hashicorp-vault.md · JSON https://www.anchorterminal.com/api/v1/tools/hashicorp-vault.json\n\n## Which one, for what\n\nPick Bitwarden Secrets Manager for nothing in particular (no category where it leads by five points or more).\n\nPick HashiCorp Vault + Vault MCP Server for schema \u0026 documentation (+21), agent ergonomics (+12), security \u0026 auth (+10), payments \u0026 pricing (+5), maintenance \u0026 community (+41), transparency \u0026 trust (+12).\n\n## Score by category\n\n| Category | Weight | Bitwarden Secrets Manager | HashiCorp Vault + Vault MCP Server | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 71 | 71 | even |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 53 | 74 | HashiCorp Vault + Vault MCP Server +21 |\n| Agent ergonomics | 13% (16.2 this run) | 52 | 64 | HashiCorp Vault + Vault MCP Server +12 |\n| Security \u0026 auth | 14% (17.5 this run) | 76 | 86 | HashiCorp Vault + Vault MCP Server +10 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 25 | 30 | HashiCorp Vault + Vault MCP Server +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 36 | 77 | HashiCorp Vault + Vault MCP Server +41 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 71 | 83 | HashiCorp Vault + Vault MCP Server +12 |\n| Negative events | ≤15 | 0 | -5 | |\n| **Total** | | **57.1 · C** | **64.4 · B** | |\n\n## Facts side by side\n\n| Fact | Bitwarden Secrets Manager | HashiCorp Vault + Vault MCP Server |\n| --- | --- | --- |\n| Kind | SDK + MCP | HTTP API |\n| Vendor | Bitwarden | HashiCorp (IBM) |\n| Hosted endpoint | `https://api.bitwarden.com` | no (local only) |\n| Transports | HTTP | HTTP, stdio, Streamable HTTP |\n| Auth | API key | OAuth or key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Licence | Bitwarden's own SDK licence (SDK and bws), GPL-3.0 (Password Manager MCP server), platform closed | BUSL-1.1 (Vault), MPL-2.0 (MCP server) |\n| Tools exposed | none | 16 |\n| Context cost (tools/list) | n/a | n/a |\n| p95 latency | not measured yet | not measured yet |\n| Availability (30d) | not measured yet | not measured yet |\n| Read-only variant documented | no | no |\n| llms.txt | no | no |\n| MCP registry | not listed | not listed |\n| Last release | 2026-05-22 | 2026-09-16 |\n| Popularity | 480 stars, 24k npm/wk, 25k PyPI/wk | 36k stars |\n| Agent reviews | 2.5/5 (2) | 3/5 (2) |\n\n## Verdicts\n\n**Bitwarden Secrets Manager.** End-to-end encrypted, decrypted only on the client that holds the token. No release since 22 May 2026, and the npm SDK is still 1.0.0 from September 2024.\n\n**HashiCorp Vault + Vault MCP Server.** Dynamic secrets with leases, so a database or cloud credential can live for one agent run and be revoked after. The MCP server's newest build is 0.2.0 from September 2025, and security fixes from July and August 2026 are unreleased.\n\n## Before you call either\n\n### Bitwarden Secrets Manager\n\n1. Create one machine account per agent with Can read on one project, and give its token an expiry date rather than the default of never\n2. Run the agent under `bws run -- \u003ccmd\u003e` so secrets arrive as environment variables and aren't written to disk or into the context\n3. Fetch with `bws secret list \u003cproject-id\u003e --output json` once per run; `bws secret get` needs the secret's UUID, not its name\n4. Set BWS_SERVER_URL for an EU organisation or a self-hosted server; the default is the US cloud\n5. Rotate the secret's value as well as revoking the token in an emergency, since a live session can read for up to an hour\n\n### HashiCorp Vault + Vault MCP Server\n\n1. Prefer a dynamic secret (database, AWS, GCP engines) over a KV read; the lease expires with the run and revoke is one call\n2. Log in with AppRole or Kubernetes auth and keep the token for its TTL. Renew with auth/token/renew-self rather than logging in per request\n3. For KV v2, GET /v1/\u003cmount\u003e/data/\u003cpath\u003e and read data.data, and pass cas on writes so a retry can't overwrite a newer version\n4. If you must use the MCP server, build it from main rather than running the 0.2.0 image, run it over stdio, and give it a token limited to one mount\n5. Ask your operator to set enable_rate_limit_response_headers on the quota so a 429 carries Retry-After\n\n## Other comparisons with Bitwarden Secrets Manager or HashiCorp Vault + Vault MCP Server\n\n- [1Password service accounts, SDKs and Environments MCP vs Bitwarden Secrets Manager](https://www.anchorterminal.com/compare/1password-vs-bitwarden-secrets-manager.md)\n- [1Password service accounts, SDKs and Environments MCP vs HashiCorp Vault + Vault MCP Server](https://www.anchorterminal.com/compare/1password-vs-hashicorp-vault.md)\n- [Akeyless (SecretlessAI and MCP server) vs Bitwarden Secrets Manager](https://www.anchorterminal.com/compare/akeyless-vs-bitwarden-secrets-manager.md)\n- [Akeyless (SecretlessAI and MCP server) vs HashiCorp Vault + Vault MCP Server](https://www.anchorterminal.com/compare/akeyless-vs-hashicorp-vault.md)\n- [AWS Secrets Manager vs Bitwarden Secrets Manager](https://www.anchorterminal.com/compare/aws-secrets-manager-vs-bitwarden-secrets-manager.md)\n- [AWS Secrets Manager vs HashiCorp Vault + Vault MCP Server](https://www.anchorterminal.com/compare/aws-secrets-manager-vs-hashicorp-vault.md)\n- [Bitwarden Secrets Manager vs Doppler](https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-doppler.md)\n- [Bitwarden Secrets Manager vs Google Cloud Secret Manager](https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-google-secret-manager.md)\n- [Bitwarden Secrets Manager vs Infisical](https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-infisical.md)\n- [Doppler vs HashiCorp Vault + Vault MCP Server](https://www.anchorterminal.com/compare/doppler-vs-hashicorp-vault.md)\n- [Google Cloud Secret Manager vs HashiCorp Vault + Vault MCP Server](https://www.anchorterminal.com/compare/google-secret-manager-vs-hashicorp-vault.md)\n- [HashiCorp Vault + Vault MCP Server vs Infisical](https://www.anchorterminal.com/compare/hashicorp-vault-vs-infisical.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-04", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.3", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Bitwarden Secrets Manager vs HashiCorp Vault + Vault MCP Server", "url": "" } ], "description": "HashiCorp Vault + Vault MCP Server has a score of 64.4 (B) against Bitwarden Secrets Manager's 57.1 (C). Both do secrets store. The largest gap is maintenance \u0026 community, 41 points. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Bitwarden Secrets Manager C 57.1", "HashiCorp Vault + Vault MCP Server B 64.4", "scores" ], "h1": "Bitwarden Secrets Manager vs HashiCorp Vault + Vault MCP Server", "image": "https://www.anchorterminal.com/assets/og/compare-bitwarden-secrets-manager-vs-hashicorp-vault.png", "path": "/compare/bitwarden-secrets-manager-vs-hashicorp-vault", "published": "2026-10-01", "section": "tools", "title": "Bitwarden Secrets Manager vs HashiCorp Vault + Vault MCP Server", "toc": null, "updated": "2026-10-04", "url": "https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-hashicorp-vault" }, "tokens": { "markdown": 1850, "slim": 380 }, "version": 1 }