{ "data": { "a": { "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.2, "grade": "B", "agentReady": false, "rank": 283, "ranked": true, "rankOf": 722, "categoryRank": 11, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 64, "maintenance": 77, "payments": 30, "reliability": 71, "schema": 74, "security": 86, "transparency": 80 }, "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.", "bestFor": "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.", "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.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 64.2 } ], "editorialScores": { "ergonomics": 64, "maintenance": 77, "payments": 30, "reliability": 71, "schema": 74, "security": 86, "transparency": 65 }, "provenanceScore": 94 }, "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": 94 }, "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-08T21:57:58.113973993Z" }, "versions": [ { "registry": "github", "name": "hashicorp/vault", "version": "v2.1.2", "released": "2026-10-07", "seenAt": "2026-10-08T16:15:31.846830697Z" } ], "githubStars": 36356, "securityTxt": { "url": "https://hashicorp.com/.well-known/security.txt", "state": "unknown", "checkedAt": "2026-10-08T15:38:30.658630559Z" }, "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-08T18:24:21.688347943Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "0620845f2f7e" }, { "url": "https://www.ibm.com/support/pages/hcp-vault-secrets-end-life", "kind": "deprecations", "status": 200, "checkedAt": "2026-10-08T18:28:24.005680337Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e24e2e2b51c3" }, { "url": "https://www.hashicorp.com/en/pricing", "kind": "pricing", "status": 429, "checkedAt": "2026-10-08T18:28:08.092212572Z", "changedAt": "0001-01-01T00:00:00Z" }, { "url": "https://www.ibm.com/products/hashicorp/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-08T18:28:21.778439253Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "0e262eb503c4" }, { "url": "https://www.hashicorp.com/en/privacy", "kind": "privacy", "status": 429, "checkedAt": "2026-10-08T18:28:10.109372947Z", "changedAt": "0001-01-01T00:00:00Z" }, { "url": "https://www.hashicorp.com/en/terms-of-service", "kind": "terms", "status": 429, "checkedAt": "2026-10-08T18:28:12.110069978Z", "changedAt": "0001-01-01T00:00:00Z" } ], "updatedAt": "2026-10-08T21:57:58.113973993Z" } }, "answer": "Phase scores 68 (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 schema \u0026 documentation, agent ergonomics, payments \u0026 pricing and transparency \u0026 trust.", "b": { "slug": "phase", "name": "Phase", "vendor": "Phi Security Inc.", "vendorUrl": "https://phase.dev", "kind": "http-api", "category": "secrets", "summary": "Phase is an open-source secrets manager from Phi Security Inc. with end-to-end encryption, service accounts, secret rotation and audit logs. Agents reach it through a REST API, a CLI and SDKs, on Phase Cloud or self-hosted.", "url": "https://www.anchorterminal.com/tools/phase", "markdownUrl": "https://www.anchorterminal.com/tools/phase.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/phase.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/phase.json", "repo": "https://github.com/phasehq/console", "license": "MIT outside the `ee/` directories, which are under the proprietary Phase Console Enterprise licence", "transports": [ "http" ], "remoteUrl": "https://api.phase.dev", "packages": [ { "registry": "npm", "name": "@phase.dev/phase-node" }, { "registry": "pypi", "name": "phase-dev" }, { "registry": "go", "name": "github.com/phasehq/golang-sdk" } ], "auth": "mixed", "authNotes": "Self-serve. A person signs in to the console with Google, GitHub or GitLab, creates a service account and a token with an optional expiry, and the agent sends it as `Authorization: Bearer ServiceAccount \u003ctoken\u003e`. Personal access tokens use `Bearer User \u003ctoken\u003e` and inherit the user's role. Tokens can also be created and deleted over the API for service accounts with server-side key management. Workloads on AWS or Azure can log in with an external identity and receive a token with a TTL. Access follows the account's role and its apps and environments, not the individual token.", "pricing": "freemium", "pricingNotes": "Free plan at $0 with 5 users or service accounts, 3 apps, 3 environments, 24-hour audit logs and 120 API requests a minute. Pro is $10 a user a month ($120 billed yearly) with a 14-day trial, unlimited apps, rotation, custom roles, network access policies, 90-day audit logs and 240 requests a minute. Enterprise is $25 a user a month ($300 yearly) with dynamic secrets, OIDC SSO, SCIM, log forwarding and a 99.99 per cent uptime SLA listed. Only human users are charged, and service accounts are free. The pricing page does not say whether a card is taken. Self-hosting the MIT core is free, and the Pro and Enterprise tiers need a licence (https://phase.dev/pricing/).", "priceSummary": "$10 / seat-mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, the API reference or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 928, "npmWeekly": 2485, "pypiWeekly": 235, "asOf": "2026-10-08" }, "docsUrl": "https://docs.phase.dev", "llmsTxt": "https://docs.phase.dev/llms.txt", "capabilities": [ "secrets.store", "secrets.machine-identity", "secrets.audit", "secrets.self-host", "secrets.rotate" ], "tags": [ "hosted", "self-hosted", "open-source", "freemium", "free-tier", "cli", "llms-txt", "go", "typescript", "python", "eu", "status-page", "soc2" ], "lastRelease": "2026-10-04", "graded": true, "anchor": { "graded": true, "score": 68, "grade": "B", "agentReady": false, "rank": 194, "ranked": true, "rankOf": 722, "categoryRank": 10, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 56, "maintenance": 83, "payments": 25, "reliability": 91, "schema": 58, "security": 83, "transparency": 73 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "Service account tokens can be minted with an expiry over the API, every secret read is logged, and the CLI redacts values when it detects an AI agent. No OpenAPI document or pagination was found in the reviewed documentation, and the Free plan keeps audit logs for 24 hours.", "bestFor": "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.", "strengths": [ "Service account tokens take an expiry and can be created and deleted through `/v1/service-accounts/:id/tokens`, and service accounts are free on every plan", "The CLI's AI mode redacts `secret` and `sealed` values and blocks `printenv`, `env` and `phase shell` when it detects an agent", "Every reveal and every REST fetch of a secret is recorded as a `READ` event with actor and IP address", "MIT outside the `ee/` directories, self-hosted with Docker Compose or Kubernetes, with no outbound usage telemetry per the docs", "Eleven console versions between 24 July and 8 October 2026, and no incident on the status page since 30 June 2026" ], "weaknesses": [ "No OpenAPI document was found. The REST reference is prose with examples, covering 47 operations", "No pagination, field selection or idempotency keys were found in the API reference, and errors are a single free-text `error` string", "The Free plan keeps audit logs for 24 hours. Rotation, custom roles and network access policies need Pro, and dynamic secrets need Enterprise", "The REST API works only on apps with server-side encryption enabled, which gives up end-to-end encryption for that app", "The pricing page lists a Phase Agents Relay credential proxy on every plan, but no documentation or CLI command for it was found" ], "agentNotes": [ "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 \u003ctoken\u003e` for a service account and `Bearer User \u003ctoken\u003e` 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-after` header on a 429", "Treat a 409 on `POST /v1/secrets` as the key already existing at that path, and use `PUT` to change it. Rotating secrets reject `PUT` and `DELETE`", "Have a person run `phase ai enable` and choose masked values. The CLI blocks an agent from running `phase ai enable` or `phase ai disable` itself" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 68 } ], "editorialScores": { "ergonomics": 56, "maintenance": 83, "payments": 25, "reliability": 91, "schema": 58, "security": 83, "transparency": 58 }, "provenanceScore": 87 }, "connect": { "install": "curl -fsSL https://pkg.phase.dev/install.sh | sh # or: brew tap phasehq/cli \u0026\u0026 brew install phase", "http": "curl -G https://api.phase.dev/v1/secrets/ -H \"Authorization: Bearer ServiceAccount $PHASE_TOKEN\" \\\n -d app_id=$PHASE_APP_ID -d env=development", "claudeCode": "phase ai enable" }, "letme": { "capability": "https://letme.dev/secrets.store", "tool": "https://letme.dev/phase" }, "area": "agent-runtime", "unitPrices": [ { "item": "Pro plan", "unit": "seat-month", "usd": 10, "note": "$120 a user billed yearly. Service accounts free" }, { "item": "Enterprise plan", "unit": "seat-month", "usd": 25, "note": "$300 a user billed yearly" } ], "provenance": { "legalEntity": "Phi Security Inc.", "domain": "phase.dev", "domainRegistered": "2023-02-03", "endpointOnVendorDomain": true, "terms": "https://phase.dev/legal/terms/", "privacy": "https://phase.dev/legal/privacy/", "statusPage": "https://phase.statuspage.io", "changelog": "https://phase.dev/changelog/", "securityTxt": "valid", "checked": "2026-10-08", "notes": [ "The terms of service (last updated 6 October 2025) name Phi Security Inc. and cover the website, the Phase Console and the self-hosted version. The site footer gives 8 The Green, Ste A, Dover, DE 19901, United States.", "The privacy policy (last updated 11 March 2026) covers phase.dev and the services, gives no retention period in days and refers to the trust centre for the subprocessor list.", "security.txt at phase.dev expires on 10 December 2030, lists three contact addresses and points to `SECURITY.md` in the console repository.", "trust.phase.dev is drawn by script and gave our reader no text, so the subprocessor list and any DPA were not read.", "RDAP for phase.dev gives a registration date of 2023-02-03.", "The status page is an Atlassian Statuspage at phase.statuspage.io with components for the console, the API, Cloudflare and AWS eu-central-1." ], "score": 87 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/phase.json", "live": { "slug": "phase", "probe": { "target": "https://api.phase.dev", "method": "get", "lastAt": "2026-10-08T21:53:30.432535593Z", "lastOk": true, "lastStatus": 200, "lastMs": 165, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 126, "p95ms24h": 199, "samples24h": 28, "samples30d": 28, "days": [ { "date": "2026-10-08", "probes": 28, "ok": 28 } ] }, "vendorStatus": { "page": "https://phase.statuspage.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T21:58:09.998402495Z" }, "updatedAt": "2026-10-08T21:58:09.998402495Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "HashiCorp (IBM)", "b": "Phi Security Inc.", "name": "Vendor" }, { "a": "no (local only)", "b": "https://api.phase.dev", "name": "Hosted endpoint" }, { "a": "HTTP, stdio, Streamable HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "BUSL-1.1 (Vault), MPL-2.0 (MCP server)", "b": "MIT outside the `ee/` directories, which are under the proprietary Phase Console Enterprise licence", "name": "Licence" }, { "a": "16", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "2026-09-16", "b": "2026-10-04", "name": "Last release" }, { "a": "couldn't be read", "b": "2025-10-06", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "2026-03-11", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "yes", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "36k stars", "b": "928 stars, 2.5k npm/wk, 235 PyPI/wk", "name": "Popularity" }, { "a": "3/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Phase scores 68 (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 schema \u0026 documentation, agent ergonomics, payments \u0026 pricing and transparency \u0026 trust.", "question": "Which is better for AI agents, HashiCorp Vault + Vault MCP Server or Phase?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do HashiCorp Vault + Vault MCP Server and Phase need an API key?" }, { "answer": "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.", "question": "Can an agent call HashiCorp Vault + Vault MCP Server and Phase without installing anything?" }, { "answer": "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).", "question": "Are HashiCorp Vault + Vault MCP Server and Phase open source?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 74 against 58", "Agent ergonomics, 64 against 56", "Payments \u0026 pricing, 30 against 25", "Transparency \u0026 trust, 80 against 73" ], "also": [ "Runs on your own machine" ], "goodFor": "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.", "slug": "hashicorp-vault", "watchFor": "The MCP server's newest build is 0.2.0 from September 2025, and security fixes from July and August 2026 are unreleased" }, { "aheadOn": [ "Reliability, 91 against 71", "Maintenance \u0026 community, 83 against 77" ], "also": [ "A hosted endpoint, with nothing to install", "Open source", "No incidents deducted, where HashiCorp Vault + Vault MCP Server loses 5 points for them" ], "goodFor": "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.", "slug": "phase", "watchFor": "No OpenAPI document was found. The REST reference is prose with examples, covering 47 operations" } ], "job": { "capability": "secrets.store", "name": "Secrets store" }, "others": [ { "json": "https://www.anchorterminal.com/compare/1password-vs-hashicorp-vault.json", "title": "1Password service accounts, SDKs and Environments MCP vs HashiCorp Vault + Vault MCP Server", "url": "https://www.anchorterminal.com/compare/1password-vs-hashicorp-vault" }, { "json": "https://www.anchorterminal.com/compare/1password-vs-phase.json", "title": "1Password service accounts, SDKs and Environments MCP vs Phase", "url": "https://www.anchorterminal.com/compare/1password-vs-phase" }, { "json": "https://www.anchorterminal.com/compare/akeyless-vs-hashicorp-vault.json", "title": "Akeyless (SecretlessAI and MCP server) vs HashiCorp Vault + Vault MCP Server", "url": "https://www.anchorterminal.com/compare/akeyless-vs-hashicorp-vault" }, { "json": "https://www.anchorterminal.com/compare/akeyless-vs-phase.json", "title": "Akeyless (SecretlessAI and MCP server) vs Phase", "url": "https://www.anchorterminal.com/compare/akeyless-vs-phase" }, { "json": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-hashicorp-vault.json", "title": "AWS Secrets Manager vs HashiCorp Vault + Vault MCP Server", "url": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-hashicorp-vault" }, { "json": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-phase.json", "title": "AWS Secrets Manager vs Phase", "url": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-phase" }, { "json": "https://www.anchorterminal.com/compare/azure-key-vault-vs-hashicorp-vault.json", "title": "Azure Key Vault vs HashiCorp Vault + Vault MCP Server", "url": "https://www.anchorterminal.com/compare/azure-key-vault-vs-hashicorp-vault" }, { "json": "https://www.anchorterminal.com/compare/azure-key-vault-vs-phase.json", "title": "Azure Key Vault vs Phase", "url": "https://www.anchorterminal.com/compare/azure-key-vault-vs-phase" }, { "json": "https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-hashicorp-vault.json", "title": "Bitwarden Secrets Manager vs HashiCorp Vault + Vault MCP Server", "url": "https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-hashicorp-vault" }, { "json": "https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-phase.json", "title": "Bitwarden Secrets Manager vs Phase", "url": "https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-phase" }, { "json": "https://www.anchorterminal.com/compare/doppler-vs-hashicorp-vault.json", "title": "Doppler vs HashiCorp Vault + Vault MCP Server", "url": "https://www.anchorterminal.com/compare/doppler-vs-hashicorp-vault" }, { "json": "https://www.anchorterminal.com/compare/doppler-vs-phase.json", "title": "Doppler vs Phase", "url": "https://www.anchorterminal.com/compare/doppler-vs-phase" }, { "json": "https://www.anchorterminal.com/compare/google-secret-manager-vs-hashicorp-vault.json", "title": "Google Cloud Secret Manager vs HashiCorp Vault + Vault MCP Server", "url": "https://www.anchorterminal.com/compare/google-secret-manager-vs-hashicorp-vault" }, { "json": "https://www.anchorterminal.com/compare/google-secret-manager-vs-phase.json", "title": "Google Cloud Secret Manager vs Phase", "url": "https://www.anchorterminal.com/compare/google-secret-manager-vs-phase" }, { "json": "https://www.anchorterminal.com/compare/hashicorp-vault-vs-infisical.json", "title": "HashiCorp Vault + Vault MCP Server vs Infisical", "url": "https://www.anchorterminal.com/compare/hashicorp-vault-vs-infisical" }, { "json": "https://www.anchorterminal.com/compare/hashicorp-vault-vs-keeper-secrets-manager.json", "title": "HashiCorp Vault + Vault MCP Server vs Keeper Secrets Manager", "url": "https://www.anchorterminal.com/compare/hashicorp-vault-vs-keeper-secrets-manager" }, { "json": "https://www.anchorterminal.com/compare/hashicorp-vault-vs-pulumi-esc.json", "title": "HashiCorp Vault + Vault MCP Server vs Pulumi ESC", "url": "https://www.anchorterminal.com/compare/hashicorp-vault-vs-pulumi-esc" }, { "json": "https://www.anchorterminal.com/compare/infisical-vs-phase.json", "title": "Infisical vs Phase", "url": "https://www.anchorterminal.com/compare/infisical-vs-phase" }, { "json": "https://www.anchorterminal.com/compare/keeper-secrets-manager-vs-phase.json", "title": "Keeper Secrets Manager vs Phase", "url": "https://www.anchorterminal.com/compare/keeper-secrets-manager-vs-phase" }, { "json": "https://www.anchorterminal.com/compare/phase-vs-pulumi-esc.json", "title": "Phase vs Pulumi ESC", "url": "https://www.anchorterminal.com/compare/phase-vs-pulumi-esc" } ], "scores": [ { "by": 20, "edge": "phase", "hashicorp-vault": 71, "key": "reliability", "name": "Reliability", "phase": 91, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 16, "edge": "hashicorp-vault", "hashicorp-vault": 74, "key": "schema", "name": "Schema \u0026 documentation", "phase": 58, "weight": 13 }, { "by": 8, "edge": "hashicorp-vault", "hashicorp-vault": 64, "key": "ergonomics", "name": "Agent ergonomics", "phase": 56, "weight": 13 }, { "by": 3, "edge": "hashicorp-vault", "hashicorp-vault": 86, "key": "security", "name": "Security \u0026 auth", "phase": 83, "weight": 14 }, { "by": 5, "edge": "hashicorp-vault", "hashicorp-vault": 30, "key": "payments", "name": "Payments \u0026 pricing", "phase": 25, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 6, "edge": "phase", "hashicorp-vault": 77, "key": "maintenance", "name": "Maintenance \u0026 community", "phase": 83, "weight": 7 }, { "by": 7, "edge": "hashicorp-vault", "hashicorp-vault": 80, "key": "transparency", "name": "Transparency \u0026 trust", "phase": 73, "weight": 7 } ], "summary": "Phase scores 68 (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 schema \u0026 documentation, agent ergonomics, payments \u0026 pricing and transparency \u0026 trust. Both do secrets store.", "verdicts": { "hashicorp-vault": "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.", "phase": "Service account tokens can be minted with an expiry over the API, every secret read is logged, and the CLI redacts values when it detects an AI agent. No OpenAPI document or pagination was found in the reviewed documentation, and the Free plan keeps audit logs for 24 hours." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/hashicorp-vault-vs-phase", "json": "https://www.anchorterminal.com/compare/hashicorp-vault-vs-phase.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/hashicorp-vault-vs-phase.md", "slim": "https://www.anchorterminal.com/compare/hashicorp-vault-vs-phase.min.md" }, "markdown": "Phase scores 68 (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 schema \u0026 documentation, agent ergonomics, payments \u0026 pricing and transparency \u0026 trust. Both do secrets store.\n\n- HashiCorp Vault + Vault MCP Server: grade B, 64.2/100, rank #283 of 722. Markdown https://www.anchorterminal.com/tools/hashicorp-vault.md · JSON https://www.anchorterminal.com/api/v1/tools/hashicorp-vault.json\n- Phase: grade B, 68/100, rank #194 of 722. Markdown https://www.anchorterminal.com/tools/phase.md · JSON https://www.anchorterminal.com/api/v1/tools/phase.json\n\n## Which one, for what\n\n### HashiCorp Vault + Vault MCP Server (B)\n\nGood 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.\n\nAhead on:\n- Schema \u0026 documentation, 74 against 58\n- Agent ergonomics, 64 against 56\n- Payments \u0026 pricing, 30 against 25\n- Transparency \u0026 trust, 80 against 73\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: 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### Phase (B)\n\nGood 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.\n\nAhead on:\n- Reliability, 91 against 71\n- Maintenance \u0026 community, 83 against 77\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- Open source\n- No incidents deducted, where HashiCorp Vault + Vault MCP Server loses 5 points for them\n\nWatch for: No OpenAPI document was found. The REST reference is prose with examples, covering 47 operations\n\n\n## Score by category\n\n| Category | Weight | HashiCorp Vault + Vault MCP Server | Phase | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 71 | 91 | Phase +20 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 74 | 58 | HashiCorp Vault + Vault MCP Server +16 |\n| Agent ergonomics | 13% (16.2 this run) | 64 | 56 | HashiCorp Vault + Vault MCP Server +8 |\n| Security \u0026 auth | 14% (17.5 this run) | 86 | 83 | HashiCorp Vault + Vault MCP Server +3 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 25 | 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) | 77 | 83 | Phase +6 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 80 | 73 | HashiCorp Vault + Vault MCP Server +7 |\n| Negative events | ≤15 | -5 | 0 | |\n| **Total** | | **64.2 · B** | **68 · B** | |\n\n## Facts side by side\n\n| Fact | HashiCorp Vault + Vault MCP Server | Phase |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | HashiCorp (IBM) | Phi Security Inc. |\n| Hosted endpoint | no (local only) | `https://api.phase.dev` |\n| Transports | HTTP, stdio, Streamable HTTP | HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Licence | BUSL-1.1 (Vault), MPL-2.0 (MCP server) | MIT outside the `ee/` directories, which are under the proprietary Phase Console Enterprise licence |\n| Tools exposed | 16 | none |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| Last release | 2026-09-16 | 2026-10-04 |\n| Terms last updated | couldn't be read | 2025-10-06 |\n| Privacy policy last updated | couldn't be read | 2026-03-11 |\n| Customer content may train models | couldn't be read | not found in the text |\n| Terms restrict automated access | couldn't be read | yes |\n| Terms restrict benchmarking | couldn't be read | yes |\n| Terms or service can change without notice | couldn't be read | not found in the text |\n| Arbitration or class-action waiver | couldn't be read | not found in the text |\n| Popularity | 36k stars | 928 stars, 2.5k npm/wk, 235 PyPI/wk |\n| Agent reviews | 3/5 (2) | none |\n\n## Verdicts\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**Phase.** Service account tokens can be minted with an expiry over the API, every secret read is logged, and the CLI redacts values when it detects an AI agent. No OpenAPI document or pagination was found in the reviewed documentation, and the Free plan keeps audit logs for 24 hours.\n\n## Before you call either\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### Phase\n\n1. Enable server-side encryption on the app before calling `/v1/secrets`. Without it the REST API cannot read or write that app's secrets\n2. Send `Authorization: Bearer ServiceAccount \u003ctoken\u003e` for a service account and `Bearer User \u003ctoken\u003e` for a personal access token. The token type is part of the header\n3. Stay under 120 requests a minute per account on Free and 240 on Pro, and wait the seconds in the `retry-after` header on a 429\n4. Treat a 409 on `POST /v1/secrets` as the key already existing at that path, and use `PUT` to change it. Rotating secrets reject `PUT` and `DELETE`\n5. Have a person run `phase ai enable` and choose masked values. The CLI blocks an agent from running `phase ai enable` or `phase ai disable` itself\n\n## Questions\n\n### Which is better for AI agents, HashiCorp Vault + Vault MCP Server or Phase?\n\nPhase scores 68 (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 schema \u0026 documentation, agent ergonomics, payments \u0026 pricing and transparency \u0026 trust.\n\n### Do HashiCorp Vault + Vault MCP Server and Phase need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call HashiCorp Vault + Vault MCP Server and Phase without installing anything?\n\nHashiCorp Vault + Vault MCP Server runs on your own machine, with no hosted endpoint listed. Phase has a hosted endpoint at https://api.phase.dev.\n\n### Are HashiCorp Vault + Vault MCP Server and Phase open source?\n\nNo 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).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/hashicorp-vault-vs-phase.json, and with the fewest tokens: https://www.anchorterminal.com/compare/hashicorp-vault-vs-phase.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"hashicorp-vault\", \"b\": \"phase\"}`. From a terminal: `anchor compare hashicorp-vault phase`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/hashicorp-vault.json and https://www.anchorterminal.com/api/v1/tools/phase.json\n\n## Other comparisons with HashiCorp Vault + Vault MCP Server or Phase\n\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- [1Password service accounts, SDKs and Environments MCP vs Phase](https://www.anchorterminal.com/compare/1password-vs-phase.md)\n- [Akeyless (SecretlessAI and MCP server) vs HashiCorp Vault + Vault MCP Server](https://www.anchorterminal.com/compare/akeyless-vs-hashicorp-vault.md)\n- [Akeyless (SecretlessAI and MCP server) vs Phase](https://www.anchorterminal.com/compare/akeyless-vs-phase.md)\n- [AWS Secrets Manager vs HashiCorp Vault + Vault MCP Server](https://www.anchorterminal.com/compare/aws-secrets-manager-vs-hashicorp-vault.md)\n- [AWS Secrets Manager vs Phase](https://www.anchorterminal.com/compare/aws-secrets-manager-vs-phase.md)\n- [Azure Key Vault vs HashiCorp Vault + Vault MCP Server](https://www.anchorterminal.com/compare/azure-key-vault-vs-hashicorp-vault.md)\n- [Azure Key Vault vs Phase](https://www.anchorterminal.com/compare/azure-key-vault-vs-phase.md)\n- [Bitwarden Secrets Manager vs HashiCorp Vault + Vault MCP Server](https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-hashicorp-vault.md)\n- [Bitwarden Secrets Manager vs Phase](https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-phase.md)\n- [Doppler vs HashiCorp Vault + Vault MCP Server](https://www.anchorterminal.com/compare/doppler-vs-hashicorp-vault.md)\n- [Doppler vs Phase](https://www.anchorterminal.com/compare/doppler-vs-phase.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- [Google Cloud Secret Manager vs Phase](https://www.anchorterminal.com/compare/google-secret-manager-vs-phase.md)\n- [HashiCorp Vault + Vault MCP Server vs Infisical](https://www.anchorterminal.com/compare/hashicorp-vault-vs-infisical.md)\n- [HashiCorp Vault + Vault MCP Server vs Keeper Secrets Manager](https://www.anchorterminal.com/compare/hashicorp-vault-vs-keeper-secrets-manager.md)\n- [HashiCorp Vault + Vault MCP Server vs Pulumi ESC](https://www.anchorterminal.com/compare/hashicorp-vault-vs-pulumi-esc.md)\n- [Infisical vs Phase](https://www.anchorterminal.com/compare/infisical-vs-phase.md)\n- [Keeper Secrets Manager vs Phase](https://www.anchorterminal.com/compare/keeper-secrets-manager-vs-phase.md)\n- [Phase vs Pulumi ESC](https://www.anchorterminal.com/compare/phase-vs-pulumi-esc.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-08", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "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": "HashiCorp Vault + Vault MCP Server vs Phase", "url": "" } ], "description": "Phase scores 68 (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 schema \u0026 documentation, agent ergonomics, payments \u0026 pricing and transparency \u0026 trust. Both do secrets…", "facts": [ "HashiCorp Vault + Vault MCP Server B 64.2", "Phase B 68", "scores" ], "h1": "HashiCorp Vault + Vault MCP Server vs Phase", "image": "https://www.anchorterminal.com/assets/og/compare-hashicorp-vault-vs-phase.png", "path": "/compare/hashicorp-vault-vs-phase", "published": "2026-10-01", "section": "tools", "title": "HashiCorp Vault + Vault MCP Server vs Phase for AI agents", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/hashicorp-vault-vs-phase" }, "tokens": { "markdown": 2700, "slim": 830 }, "version": 1 }