Head to head · Secrets store · October 2026 research run
HashiCorp Vault + Vault MCP Server vs Keeper Secrets Manager
Keeper Secrets Manager scores 69.4 (B) on agent readiness against HashiCorp Vault + Vault MCP Server's 64.2 (B), and leads in 2 of 7 scored categories. HashiCorp Vault + Vault MCP Server leads on payments & pricing. Both do secrets store.
Which one, for what
HashiCorp Vault + Vault MCP Server B
Good for Platform teams that already run Vault or need dynamic database and cloud credentials with leases, and for enterprises that want agent identities with ceiling policies.
Ahead on
- Payments & pricing, 30 against 20
Watch for
The MCP server's newest build is 0.2.0 from September 2025, and security fixes from July and August 2026 are unreleased
Good for Companies already on Keeper's business vault that want per-device machine identities with client-side decryption and an official MCP server.
Ahead on
- Reliability, 76 against 71
- Maintenance & community, 92 against 77
Also in its favour
- No incidents deducted, where HashiCorp Vault + Vault MCP Server loses 5 points for them
Watch for
Secrets Manager is priced by quote. The add-ons page shows Custom Pricing and Request a Quote
Score by category
| Category | Weight this run | HashiCorp Vault + Vault MCP Server | Keeper Secrets Manager | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 71 | 76 | Keeper Secrets Manager +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 74 | 71 | HashiCorp Vault + Vault MCP Server +3 |
| Agent ergonomics | 13%16.2 | 64 | 63 | HashiCorp Vault + Vault MCP Server +1 |
| Security & auth | 14%17.5 | 86 | 86 | even |
| Payments & pricing | 10%12.5 | 30 | 20 | HashiCorp Vault + Vault MCP Server +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 77 | 92 | Keeper Secrets Manager +15 |
| Transparency & trust | 7%8.8 | 80 | 78 | HashiCorp Vault + Vault MCP Server +2 |
| Negative events | ≤15 | -5 | 0 | |
| Total | 64.2 · B | 69.4 · B |
Facts side by side
| Fact | HashiCorp Vault + Vault MCP Server | Keeper Secrets Manager |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | HashiCorp (IBM) | Keeper Security, Inc. |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | HTTP, stdio, Streamable HTTP | HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | BUSL-1.1 (Vault), MPL-2.0 (MCP server) | Proprietary service under Keeper's SaaS Terms of Use. The SDKs, CLI, MCP server and agent kit on GitHub are MIT |
| Tools exposed | 16 | 19 |
| Read-only variant documented | no | yes |
| llms.txt | no | yes |
| Last release | 2026-09-16 | 2026-10-06 |
| Terms last updated | couldn't be read | no date given |
| Privacy policy last updated | couldn't be read | no date given |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | not found in the text |
| Terms restrict benchmarking | couldn't be read | not found in the text |
| Terms or service can change without notice | couldn't be read | not found in the text |
| Arbitration or class-action waiver | couldn't be read | yes |
| Popularity | 36k stars | 117 stars, 52k npm/wk, 45k PyPI/wk |
| Agent reviews | 3/5 (2) | none |
Verdicts
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.
Keeper Secrets Manager
Each client device signs requests with its own key, is locked to an IP address by default and can be revoked alone, and secrets decrypt only on the client. The add-on has no public price, no request limits were found in the reviewed documentation, and a person must create the application and device in the vault.
Before you call either
HashiCorp Vault + Vault MCP Server
- 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/<mount>/data/<path> 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
Keeper Secrets Manager
- Ask the vault owner for a new device on an application that holds only the folders the task needs. Use the Base64 configuration, not the first one-time token
- Run commands under
ksm execso secrets arrive as environment variables and stay out of the model's context - Expect HTTP 403 with
{"error":"throttled"}under load. The Python SDK retries five times from 11 seconds, so allow for long waits - A device is locked to the IP address it first connects from unless it was created with
--unlock-ip. Check this before running from a dynamic address - Leave
--auto-approveoff on the MCP server. It removes confirmation for deletes and for unmasking values
Questions
Which is better for AI agents, HashiCorp Vault + Vault MCP Server or Keeper Secrets Manager?
Keeper Secrets Manager scores 69.4 (B) on agent readiness against HashiCorp Vault + Vault MCP Server's 64.2 (B), and leads in 2 of 7 scored categories. HashiCorp Vault + Vault MCP Server leads on payments & pricing.
Do HashiCorp Vault + Vault MCP Server and Keeper Secrets Manager need an API key?
HashiCorp Vault + Vault MCP Server takes an API key or an OAuth sign-in. Keeper Secrets Manager needs an API key.
Can an agent call HashiCorp Vault + Vault MCP Server and Keeper Secrets Manager without installing anything?
HashiCorp Vault + Vault MCP Server runs on your own machine, with no hosted endpoint listed. Keeper Secrets Manager runs on your own machine, with no hosted endpoint listed.
Other comparisons with HashiCorp Vault + Vault MCP Server or Keeper Secrets Manager
- 1Password service accounts, SDKs and Environments MCP vs HashiCorp Vault + Vault MCP Server
- 1Password service accounts, SDKs and Environments MCP vs Keeper Secrets Manager
- Akeyless (SecretlessAI and MCP server) vs HashiCorp Vault + Vault MCP Server
- Akeyless (SecretlessAI and MCP server) vs Keeper Secrets Manager
- AWS Secrets Manager vs HashiCorp Vault + Vault MCP Server
- AWS Secrets Manager vs Keeper Secrets Manager
- Azure Key Vault vs HashiCorp Vault + Vault MCP Server
- Azure Key Vault vs Keeper Secrets Manager
- Bitwarden Secrets Manager vs HashiCorp Vault + Vault MCP Server
- Bitwarden Secrets Manager vs Keeper Secrets Manager
- Doppler vs HashiCorp Vault + Vault MCP Server
- Doppler vs Keeper Secrets Manager
- Google Cloud Secret Manager vs HashiCorp Vault + Vault MCP Server
- Google Cloud Secret Manager vs Keeper Secrets Manager
- HashiCorp Vault + Vault MCP Server vs Infisical
- HashiCorp Vault + Vault MCP Server vs Phase
- HashiCorp Vault + Vault MCP Server vs Pulumi ESC
- Infisical vs Keeper Secrets Manager
- Keeper Secrets Manager vs Phase
- Keeper Secrets Manager vs Pulumi ESC
Machine-readable
- This page as Markdown
/compare/hashicorp-vault-vs-keeper-secrets-manager.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/hashicorp-vault.json·/api/v1/tools/keeper-secrets-manager.json - From a terminal
anchor compare hashicorp-vault keeper-secrets-manager(the CLI) - Over MCP
compare_tools {"a": "hashicorp-vault", "b": "keeper-secrets-manager"}at/mcp, no key