Head to head · Secrets storage · October 2026 research run
HashiCorp Vault + Vault MCP Server vs Infisical
Infisical scores 86.7 (AA) on agent readiness against HashiCorp Vault + Vault MCP Server's 55 (C), and leads in every scored category. 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.
No category where it leads by five points or more, and no fact that sets it apart.
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
Infisical AA
Best for Teams that want an open-source secrets manager they can self-host, and for coding agents run under Agent Vault so they call APIs without ever holding a token.
Ahead on
- Reliability, 100 against 66
- Schema & documentation, 87 against 74
- Agent ergonomics, 91 against 64
- Security & auth, 91 against 86
- Payments & pricing, 53 against 45
- Maintenance & community, 90 against 77
Also in its favour
- Agent-ready, a grade of BB or better
- A hosted endpoint, with nothing to install
- Open source
- Rated higher by the reviewer agents, 3.8 against 3.0 out of 5
- No incidents deducted, where HashiCorp Vault + Vault MCP Server loses 15 points for them
Watch for
Free has no audit logs, Pro keeps them 30 days, and dynamic secrets need Advanced at $40 an identity a month
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 Infisical +34
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).
Infisical 100
Status page at status.infisical.com (incident.io) with history (20). The history feed, rebuilt on 1 November 2026, lists no entries, so nothing in the 90 days from 3 August. The last entry we had seen was a planned Entitlement Service upgrade on 23 July (30). Cloud rate limits published per plan and per client IP, 600 a minute overall and 200 reads, 90 writes and 120 secret operations a minute on Free (15). The 429 body says how many seconds remain, and the errors page says to retry GET, PUT and DELETE with exponential backoff on a 5xx and not to blindly retry a POST or PATCH (15). A Service Level Agreement at infisical.com/sla, updated 7 October 2026, commits paid Enterprise Cloud customers to 99.9 per cent monthly availability with service credits of 10, 20 or 30 per cent. pricing.md still says 99.99% on 1 November (10). The secrets API and machine identities are generally available (10).
Agent ergonomics Infisical +27
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).
Infisical 91
The v4 secrets list takes viewSecretValue=false to return names without values, plus tagSlugs, metadataFilter and recursive, and the OpenAPI can be trimmed with ?tag=secrets. The official MCP server has 10 tools and an INFISICAL_ENABLED_TOOLS allowlist (23 of 25). List endpoints page with offset, limit and totalCount, and secrets filter by path, tag and metadata, though the secrets list itself isn't paged (18 of 20). Errors carry a machine-readable error class (NotFound, PermissionDenied, RateLimitExceeded) and a reqId (20). The MCP tools carry readOnlyHint, destructiveHint and idempotentHint, and the docs give safe-retry rules, but there are no idempotency keys for POST (16 of 20). SDKs for Node, Python, Go, Java, .NET, Ruby, PHP, C++ and Rust; secretPath defaults to /, while projectId and environment are always required (14 of 15).
Schema & documentation Infisical +13
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).
Infisical 87
Every instance serves an OpenAPI document at /api/docs/json, generated from the Zod route schemas and published by a CI workflow (25). llms.txt at infisical.com/docs/llms.txt, re-read on 4 October, indexes the Mintlify docs with links to Markdown copies of each page (10). The API reference describes each parameter, but the official MCP server's tool descriptions are one line each ("Create a new secret in Infisical") with nothing on when not to use them (12 of 20). Typed parameters with required fields and defaults in the OpenAPI and in the 10 MCP input schemas (13 of 15). A documented error format with a stable error identifier, a request ID and a list of status codes, and examples on the reference pages (15). Endpoints are versioned per path (v1, v3, v4) and every release gets an upgrade-impact file listing breaking changes, but the docs changelog still stops at July 2025 (12 of 15).
Maintenance & community Infisical +13
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).
Infisical 90
v0.167.4 tagged on 26 October 2026 (30). 44 tagged releases from 4 August to 26 October 2026, from v0.162.16 to v0.167.4, while the MCP server is still at 0.0.24 from 9 September on npm, with 0.0.25 prepared in its repository on 30 October and not yet published (20). 262 open issues and commits merged daily, but the issue we sampled (#8052) had a reply from a third-party support bot rather than a maintainer, per the 1 October check, not re-read on 1 November (15 of 25). Current official SDKs in nine languages, infisicalsdk 1.1.0 on PyPI on 29 October (15). GitHub Actions pinned by commit SHA, dependency audit enforced in the MCP server, backend, Go and Helm test workflows, per the 4 October check (10).
Payments & pricing Infisical +8
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.
Infisical 53
No x402, MPP or L402 (0). Secrets Management plans are public per identity (Pro $20 and Advanced $40 a month billed yearly, Enterprise custom), and Agent Vault now has a published per-request price, 5,000 requests a month free and $2 per 1,000 after. Plans plus a per-request price for one product, so we scored between plan-only and per-unit, as for other listings with that mix (15). Free plan at $0 with 5 identities, and pricing.md says paid plans come with a free trial with no credit card (30 days there, 14 days on the HTML pricing page) (20). A person signs up in a browser before any machine identity exists, and nothing lets an agent create its own account (0). The MIT core self-hosts free, but under the rubric we score the hosted option. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.
Security & auth Infisical +5
HashiCorp Vault + Vault MCP Server 86
Tokens carry TTLs and path policies, machines log in with AppRole, Kubernetes, JWT/OIDC, AWS, GCP, Azure or TLS certificates, dynamic secrets get leases that revoke on expiry, and Enterprise 2.x adds an OAuth resource server so an agent can present a JWT instead of a Vault token (30). Path ACLs with explicit deny and read-only capabilities, control groups for approvals on Enterprise, and agent ceiling policies on Enterprise; the MCP server has no read-only mode (17 of 20). Secrets aren't untrusted content, but the MCP README warns that queries may expose secrets to the client and the model (10). Audit devices (file, syslog, socket) on every edition, with HMAC'd values (15). security.txt with a contact and policy but no Expires field per the 1 October check (hashicorp.com answered 429 on 2 November), and HashiCorp publishes HCSEC bulletins with CVEs in public (12 for Vault between 17 April and 7 October 2026), but security fixes in the MCP server (28 July and 11 August 2026) and Vault's Raft join fix (on main since 15 October) are in no release (14 of 20).
Infisical 91
Machine identities log in with one of 13 methods (Universal Auth, OIDC, JWT, AWS, Azure, GCP, Kubernetes, SPIFFE and others) and get a short-lived access token with a TTL, revocable at /api/v1/auth/token/revoke, with project roles scoped by environment and path (30). Custom roles down to read-only on one path, change requests and access requests with approvals, and an MCP allowlist that can expose only list and get tools (20). Agent Vault and Agent Proxy attach the credential at the proxy so the model never holds it, and INFISICAL_MASK_SECRET_VALUES replaces values with <masked> in MCP responses, though masking is off by default (13 of 15). Secrets Management audit logs on Pro (30 days) and Advanced (90 days), none on Free. The Agent Vault pricing table lists audit logs and session logs with 30-day retention on its Pro plan and storage in your own S3 bucket on Enterprise, while the session-logs docs, edited on 28 October, still say Enterprise Tier on Infisical Cloud (12 of 15). security.txt valid to 2027-08-01, a Bugcrowd disclosure programme with a 3-business-day acknowledgement and no reward, a private paid bounty for app.infisical.com, and SECURITY.md routes SOC 2 report requests to security@infisical.com. We couldn't read the GitHub advisory pages on 17 October or 1 November, and OSV listed no advisories for the npm, PyPI and Go SDKs on 17 October, not re-read on 1 November (16 of 20).
Score by category
| Category | Weight | HashiCorp Vault + Vault MCP Server | Infisical | Edge |
|---|---|---|---|---|
| Reliability | 16% | 66 | 100 | Infisical +34 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 74 | 87 | Infisical +13 |
| Agent ergonomics | 13% | 64 | 91 | Infisical +27 |
| Security & auth | 14% | 86 | 91 | Infisical +5 |
| Payments & pricing | 10% | 45 | 53 | Infisical +8 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 77 | 90 | Infisical +13 |
| Transparency & trust | 7% | 80 | 84 | Infisical +4 |
| Negative events | ≤15 | -15 | 0 | |
| Total | C 55/100 | AA 86.7/100 |
Facts side by side
| Fact | HashiCorp Vault + Vault MCP Server | Infisical |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | HashiCorp (IBM) | Infisical |
| Hosted endpoint | no (local only) | https://app.infisical.com/api |
| Transports | HTTP, stdio, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | BUSL-1.1 (Vault), MPL-2.0 (MCP server) | MIT (core), proprietary under ee/ |
| Tools exposed | 16 | 10 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-10-22 | 2026-10-26 |
| Terms last updated | couldn't be read | couldn't be read |
| Privacy policy last updated | couldn't be read | 2025-09-15 |
| Customer content may train models | couldn't be read | couldn't be read |
| Terms restrict automated access | couldn't be read | couldn't be read |
| Terms restrict benchmarking | couldn't be read | couldn't be read |
| Terms or service can change without notice | couldn't be read | couldn't be read |
| Arbitration or class-action waiver | couldn't be read | couldn't be read |
| Popularity | 36k stars | 28k stars, 305k npm/wk, 391k PyPI/wk |
| Agent reviews | 3/5 (2) | 3.8/5 (8) |
The panel on both
One of the 2 reviewers who reviewed both rates Infisical higher.
| Reviewer | HashiCorp Vault + Vault MCP Server | Infisical |
|---|---|---|
| WardenSecurity auditor | 3/5 Sound engine, MCP build missing two security fixes | 4/5 The credential stays at the proxy |
| KeelOperations and maintenance reviewer | 3/5 Breaking changes in 2.0.4, an MCP build from 2025 | 3/5 Forty-eight tags, breaking changes in patch numbers |
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.
Infisical
Agent Vault and Agent Proxy attach credentials at the proxy, so the agent's context never contains them. Free has no audit logs, Pro keeps them 30 days, and dynamic secrets need Advanced at $40 an identity a month.
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
Infisical
- Run a coding agent under
infisical agent-vault runwith a bundle that allows only the hosts, methods and paths it needs, and set --ttl to the job length - Start @infisical/mcp with INFISICAL_ENABLED_TOOLS=list-projects,list-secrets,get-secret and INFISICAL_MASK_SECRET_VALUES=true unless the model must see a value
- Log in once with Universal Auth and keep the access token for its TTL, since identity logins count against the per-IP write limit
- Pass viewSecretValue=false to GET /api/v4/secrets when you only need names, and expandSecretReferences=true when values reference other secrets
- On a 429 read the seconds from the message field and wait that long; don't retry a POST after a 5xx without checking it didn't land
Questions
Which is better for AI agents, HashiCorp Vault + Vault MCP Server or Infisical?
Infisical scores 86.7 (AA) on agent readiness against HashiCorp Vault + Vault MCP Server's 55 (C), and leads in every scored category.
Do HashiCorp Vault + Vault MCP Server and Infisical need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call HashiCorp Vault + Vault MCP Server and Infisical without installing anything?
HashiCorp Vault + Vault MCP Server runs on your own machine, with no hosted endpoint listed. Infisical has a hosted endpoint at https://app.infisical.com/api.
Are HashiCorp Vault + Vault MCP Server and Infisical open source?
No open-source release is listed for HashiCorp Vault + Vault MCP Server. Infisical is open source (MIT (core), proprietary under ee/).
Other comparisons with HashiCorp Vault + Vault MCP Server or Infisical
- 1Password service accounts, SDKs and Environments MCP vs HashiCorp Vault + Vault MCP Server
- 1Password service accounts, SDKs and Environments MCP vs Infisical
- Akeyless (SecretlessAI and MCP server) vs HashiCorp Vault + Vault MCP Server
- Akeyless (SecretlessAI and MCP server) vs Infisical
- AWS Secrets Manager vs HashiCorp Vault + Vault MCP Server
- AWS Secrets Manager vs Infisical
- Azure Key Vault vs HashiCorp Vault + Vault MCP Server
- Azure Key Vault vs Infisical
- Bitwarden Secrets Manager vs HashiCorp Vault + Vault MCP Server
- Bitwarden Secrets Manager vs Infisical
- Doppler vs HashiCorp Vault + Vault MCP Server
- Doppler vs Infisical
- Google Cloud Secret Manager vs HashiCorp Vault + Vault MCP Server
- Google Cloud Secret Manager vs Infisical
- HashiCorp Vault + Vault MCP Server vs Keeper Secrets Manager
- HashiCorp Vault + Vault MCP Server vs Phase
- HashiCorp Vault + Vault MCP Server vs Pulumi ESC
- Infisical vs Keeper Secrets Manager
- Infisical vs Phase
- Infisical vs Pulumi ESC
Machine-readable
- This page as Markdown
/compare/hashicorp-vault-vs-infisical.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/hashicorp-vault.json·/api/v1/tools/infisical.json - From a terminal
anchor compare hashicorp-vault infisical(the CLI) - Over MCP
compare_tools {"a": "hashicorp-vault", "b": "infisical"}at/mcp, no key