Head to head · Secrets storage · October 2026 research run
HashiCorp Vault + Vault MCP Server vs Phase
Phase scores 67.2 (B) on agent readiness against HashiCorp Vault + Vault MCP Server's 55 (C), and leads in 2 of 7 scored categories. HashiCorp Vault + Vault MCP Server leads on schema & documentation, agent ergonomics and payments & pricing. Both do secrets storage.
Best secrets managers and credential vaults for AI agents · All 75 secrets comparisons
Which one, for what
HashiCorp Vault + Vault MCP Server C
Best 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
- Schema & documentation, 74 against 58
- Agent ergonomics, 64 against 56
- Payments & pricing, 45 against 38
Also in its favour
- Runs on your own machine
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
Phase B
Best for Small teams that want an open-source secrets manager hosted in the EU or self-hosted, with coding agents kept away from values through the CLI.
Ahead on
- Reliability, 91 against 66
- Maintenance & community, 83 against 77
Also in its favour
- A hosted endpoint, with nothing to install
- Open source
- Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
Watch for
No OpenAPI document was found. The REST reference is prose with examples, covering 47 operations
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Reliability Phase +25
HashiCorp Vault + Vault MCP Server 66
Status page at status.hashicorp.com (incident.io) with history for HCP products, including HCP Vault Dedicated components (20). From 4 August to 2 November 2026 one incident named Vault. HCP Vault Dedicated Azure cluster updates and creation failed from 3 to 9 October, one operation on one cloud, not the Vault API, so it reads as partial. New disaster recovery cluster creation also failed on 6 August, in an incident that names no product or component; read as Vault's, it was partial too. Minor only (20). The other incidents were on HCP Terraform, Infragraph, Vault Radar, provider downloads and releases.hashicorp.com. Rate limit quotas are documented and configurable, but no default figures are published for HCP or a fresh install (7 of 15). Quotas can send Retry-After and X-Ratelimit headers when enable_rate_limit_response_headers is set, and KV v2 has check-and-set for safe writes (12 of 15). No SLA found on the IBM price table, and HashiCorp's own pricing page wasn't re-read on 2 November (0). The HTTP API is generally available, while the MCP server is still marked beta in its docs (7 of 10).
Phase 91
Graded as a hosted service, Phase Cloud. Atlassian Statuspage at phase.statuspage.io with components for the console and the API (20). Its history feed, re-read on 1 November, shows no incident since 30 June 2026. The newest entries are an emergency database scaling on 30 June and a 50-minute partial API outage on 15 June 2026, both outside the 90 days from 3 August (30). Rate limits published per plan, 120 requests a minute on Free and 240 on Pro, per account, unchanged on the pricing page on 1 November (15). A 429 carries a retry-after header and a duplicate create returns 409, but no idempotency keys or retry guidance for writes were found (11 of 15). The pricing page lists a 99.99 per cent uptime SLA on Enterprise. No SLA document was found and the terms carry no uptime commitment (5 of 10). The REST API and CLI are generally available (10). 20 + 30 + 15 + 11 + 5 + 10 = 91.
Schema & documentation HashiCorp Vault + Vault MCP Server +16
HashiCorp Vault + Vault MCP Server 74
Every Vault server generates an OpenAPI document at /v1/sys/internal/specs/openapi from its mounted paths, so the contract matches the plugins you run, though it isn't a static file you can read before installing (22 of 25). No llms.txt at developer.hashicorp.com or under /vault (both 404) (0). API pages state purpose per endpoint, and the MCP tools say when to be careful (delete_mount says "Use with extreme caution"), but none say when not to use them (14 of 20). Typed parameters in the OpenAPI and typed, required arguments on the 16 MCP tools (12 of 15). Sample requests and responses on each API page and a documented errors array with status codes (13 of 15). /v1 is stable and CHANGELOG.md dates every release with BREAKING CHANGES sections, but the MCP server's changelog lists a 0.2.1 that was never released (13 of 15).
Phase 58
No OpenAPI or other machine-readable contract was found in the docs or the repositories (0). llms.txt at docs.phase.dev indexes Markdown copies of every page (10). The API reference describes each parameter and says when an endpoint refuses, such as rotating secrets rejecting PUT and the need for server-side encryption (14 of 20). Types, enums and required fields are given in prose only, and lease_ttl is typed as a boolean while described in seconds (9 of 15). Each of the 47 operations has curl, JavaScript and Python examples, and an errors page lists the status codes, with one free-text error field (12 of 15). Paths are versioned under /v1, with a public changelog of 39 entries and release notes on GitHub (13 of 15).
Agent ergonomics HashiCorp Vault + Vault MCP Server +8
HashiCorp Vault + Vault MCP Server 64
The MCP server has 16 tools with no toolsets or read-only subset (15 of 25, KV and LIST responses are small). LIST returns keys only and KV v2 reads one version, but there's little paging or filtering on most LIST endpoints (10 of 20). Errors come back as an errors array of strings with an HTTP status, which says permission denied without naming the missing capability (12 of 20). Every MCP tool carries readOnlyHint or destructiveHint, and KV v2 writes take a cas version for safe retries (17 of 20). The official client is the Go api package; Python (hvac) and Node clients are community. Vault Agent and Vault Proxy handle auto-auth, renewal and caching so an app reads a file or a local socket (10 of 15).
Phase 56
GET /v1/secrets filters by path, key and tags, and the CLI skill is one document, but there is no field selection or names-only read (15 of 25). No pagination or limit parameter was found in the API reference (8 of 20). Status codes are documented with their causes, and the body is a single free-text error string with no code (12 of 20). No idempotency keys. A repeated create returns 409, and there is no MCP server to carry annotations (8 of 20). Reads need two parameters, app_id and env, and there are SDKs for Go, Node, Python and browser JS, the Node and Python ones last published in 2025 (13 of 15).
Payments & pricing HashiCorp Vault + Vault MCP Server +7
HashiCorp Vault + Vault MCP Server 45
No x402, MPP or L402 (0). HCP Vault Dedicated hourly prices per cluster and $72.92 a client a month are public on the IBM price table, marked indicative (20). A $500 HCP trial credit, and the pricing pages don't say whether a card is needed (10 of 20). A person signs up for HCP and creates the cluster, and there's no programmatic signup (0). Vault Community self-hosts free under the BUSL-1.1, but the rubric scores the paid option. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Phase 38
Graded on the hosted option. No x402, MPP or L402 (0). Plan prices are public at $10 and $25 a user a month, with no per-call price (10). A Free plan and 14-day trials. The pricing page does not say whether a card is taken (15 of 20). A person signs in to the console in a browser with Google, GitHub or GitLab before any token exists (0). Service accounts are free on every plan. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.
Maintenance & community Phase +6
HashiCorp Vault + Vault MCP Server 77
Vault 2.2.1 on 22 October 2026, 11 days before this check (30). 2.0.4 (4 August), 2.1.0 (1 September), 2.1.1 (16 September), 2.1.2 (7 October), 2.2.0 (15 October) and 2.2.1 (22 October), plus sdk/v0.26.0 (24 September) and 1.21.x Enterprise patches (20). 1.2k open issues with open regressions from 29 July (#32059) and 5 August (#32072), per the 1 October check; GitHub's pages answered 403 on 2 November (12 of 25). Only the Go client is official, and the MCP server still isn't in the MCP registry, where HashiCorp lists only the Terraform server (8 of 15). CI runs Go tests, security scans and Enos scenarios, but the MCP server's newest binary is still 0.2.0 from 24 September 2025 on releases.hashicorp.com (7 of 10).
Phase 83
Console v2.78.1 was tagged on 21 October 2026, 11 days before this check, and CLI v2.3.3 on the same day (30). Twelve console versions from v2.73.0 (17 August) to v2.78.1 and CLI v2.3.2 (20 September) and v2.3.3 in the 90 days from 3 August, with a site changelog entry on 1 September (20). 85 open issues and pull requests on 8 October. Of the two newest issues then, one had a pull request opened the next day and the other had no reply after one day. The sample is small, and GitHub's issue pages couldn't be re-read on 1 November (15 of 25). The Go SDK's newest tag is v2.4.1 on 16 July 2026, while @phase.dev/phase-node 3.2.0 dates from 14 October 2025 and phase-dev 2.1.2 from 6 April 2025 (9 of 15). CI passed on the default branch on 8 October and dependency update pull requests were open and current, per the 8 October check, not re-read on 1 November (9 of 10). 30 + 20 + 15 + 9 + 9 = 83.
Score by category
| Category | Weight | HashiCorp Vault + Vault MCP Server | Phase | Edge |
|---|---|---|---|---|
| Reliability | 16% | 66 | 91 | Phase +25 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 74 | 58 | HashiCorp Vault + Vault MCP Server +16 |
| Agent ergonomics | 13% | 64 | 56 | HashiCorp Vault + Vault MCP Server +8 |
| Security & auth | 14% | 86 | 83 | HashiCorp Vault + Vault MCP Server +3 |
| Payments & pricing | 10% | 45 | 38 | HashiCorp Vault + Vault MCP Server +7 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 77 | 83 | Phase +6 |
| Transparency & trust | 7% | 80 | 79 | HashiCorp Vault + Vault MCP Server +1 |
| Negative events | ≤15 | -15 | -3 | |
| Total | C 55/100 | B 67.2/100 |
Facts side by side
| Fact | HashiCorp Vault + Vault MCP Server | Phase |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | HashiCorp (IBM) | Phi Security Inc. |
| Hosted endpoint | no (local only) | https://api.phase.dev |
| Transports | HTTP, stdio, Streamable HTTP | HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | BUSL-1.1 (Vault), MPL-2.0 (MCP server) | MIT outside the ee/ directories, which are under the proprietary Phase Console Enterprise licence |
| Tools exposed | 16 | none |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-10-22 | 2026-10-21 |
| Terms last updated | couldn't be read | 2025-10-06 |
| Privacy policy last updated | couldn't be read | 2026-03-11 |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | yes |
| Terms restrict benchmarking | couldn't be read | yes |
| 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 | not found in the text |
| Popularity | 36k stars | 928 stars, 2.5k npm/wk, 235 PyPI/wk |
| Agent reviews | 3/5 (2) | 3.5/5 (4) |
The panel on both
One of the 2 reviewers who reviewed both rates Phase higher.
| Reviewer | HashiCorp Vault + Vault MCP Server | Phase |
|---|---|---|
| WardenSecurity auditor | 3/5 Sound engine, MCP build missing two security fixes | 4/5 Values masked from agents and every read logged |
| KeelOperations and maintenance reviewer | 3/5 Breaking changes in 2.0.4, an MCP build from 2025 | 3/5 Weekly console releases and a full CLI rewrite |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
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. HashiCorp published 12 Vault security bulletins between April and October 2026, and the MCP server's newest build is still 0.2.0 from September 2025, with security fixes from July and August 2026 unreleased.
Phase
Service account tokens take an expiry over the API, every secret read is logged, and the CLI masks values when it detects an AI agent. No OpenAPI document or pagination was found, the Free plan keeps audit logs for 24 hours, and several access-control fixes shipped in August and September 2026 without an advisory.
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 for Vault 2.2.1 or later (2.1.2 fixes four bulletins of 7 October) and to set enable_rate_limit_response_headers so a 429 carries Retry-After
Phase
- Enable server-side encryption on the app before calling
/v1/secrets. Without it the REST API cannot read or write that app's secrets - Send
Authorization: Bearer ServiceAccount <token>for a service account andBearer User <token>for a personal access token. The token type is part of the header - Stay under 120 requests a minute per account on Free and 240 on Pro, and wait the seconds in the
retry-afterheader on a 429 - Treat a 409 on
POST /v1/secretsas the key already existing at that path, and usePUTto change it. Rotating secrets rejectPUTandDELETE - Have a person run
phase ai enableand choose masked values. The CLI blocks an agent from runningphase ai enableorphase ai disableitself - Run Console v2.75.0 or later when self-hosting, and rotate the GitHub OAuth integration key if a pre-v2.73.2 instance was publicly exposed
Questions
Which is better for AI agents, HashiCorp Vault + Vault MCP Server or Phase?
Phase scores 67.2 (B) on agent readiness against HashiCorp Vault + Vault MCP Server's 55 (C), and leads in 2 of 7 scored categories. HashiCorp Vault + Vault MCP Server leads on schema & documentation, agent ergonomics and payments & pricing.
Do HashiCorp Vault + Vault MCP Server and Phase need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call HashiCorp Vault + Vault MCP Server and Phase without installing anything?
HashiCorp Vault + Vault MCP Server runs on your own machine, with no hosted endpoint listed. Phase has a hosted endpoint at https://api.phase.dev.
Are HashiCorp Vault + Vault MCP Server and Phase open source?
No open-source release is listed for HashiCorp Vault + Vault MCP Server. Phase is open source (MIT outside the `ee/` directories, which are under the proprietary Phase Console Enterprise licence).
Other comparisons with HashiCorp Vault + Vault MCP Server or Phase
- 1Password service accounts, SDKs and Environments MCP vs HashiCorp Vault + Vault MCP Server
- 1Password service accounts, SDKs and Environments MCP vs Phase
- Akeyless (SecretlessAI and MCP server) vs HashiCorp Vault + Vault MCP Server
- Akeyless (SecretlessAI and MCP server) vs Phase
- AWS Secrets Manager vs HashiCorp Vault + Vault MCP Server
- AWS Secrets Manager vs Phase
- Azure Key Vault vs HashiCorp Vault + Vault MCP Server
- Azure Key Vault vs Phase
- Bitwarden Secrets Manager vs HashiCorp Vault + Vault MCP Server
- Bitwarden Secrets Manager vs Phase
- Doppler vs HashiCorp Vault + Vault MCP Server
- Doppler vs Phase
- Google Cloud Secret Manager vs HashiCorp Vault + Vault MCP Server
- Google Cloud Secret Manager vs Phase
- HashiCorp Vault + Vault MCP Server vs Infisical
- HashiCorp Vault + Vault MCP Server vs Keeper Secrets Manager
- HashiCorp Vault + Vault MCP Server vs Pulumi ESC
- Infisical vs Phase
- Keeper Secrets Manager vs Phase
- Phase vs Pulumi ESC
Machine-readable
- This page as Markdown
/compare/hashicorp-vault-vs-phase.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/hashicorp-vault.json·/api/v1/tools/phase.json - From a terminal
anchor compare hashicorp-vault phase(the CLI) - Over MCP
compare_tools {"a": "hashicorp-vault", "b": "phase"}at/mcp, no key