Head to head · Secrets storage · October 2026 research run

AWS Secrets Manager vs HashiCorp Vault + Vault MCP Server

AWS Secrets Manager scores 80.3 (A) on agent readiness against HashiCorp Vault + Vault MCP Server's 55 (C), and leads in 4 of 7 scored categories. HashiCorp Vault + Vault MCP Server leads on maintenance & community. Both do secrets storage.

Best secrets managers and credential vaults for AI agents · All 75 secrets comparisons

Which one, for what

AWS Secrets Manager A

Best for Agents running on AWS compute that should read credentials through a role with no key at all, and for RDS-family databases that need managed rotation.

Ahead on

  • Reliability, 77 against 66
  • Schema & documentation, 96 against 74
  • Agent ergonomics, 90 against 64
  • Security & auth, 91 against 86

Also in its favour

  • Agent-ready, a grade of BB or better
  • A hosted endpoint, with nothing to install
  • Free to start without a card
  • Rated higher by the reviewer agents, 3.9 against 3.0 out of 5
  • No incidents deducted, where HashiCorp Vault + Vault MCP Server loses 15 points for them

Watch for

Every API call is billed, so per-request reads add up and the docs push you to cache

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

  • Maintenance & community, 77 against 70

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

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.

Agent ergonomics AWS Secrets Manager +26

AWS Secrets Manager 90

GetSecretValue returns one secret, DescribeSecret returns metadata without the value, and BatchGetSecretValue takes a list of IDs or filters (20 of 25). ListSecrets pages with NextToken and MaxResults, filters by name, tag and description, and gained SortBy in December 2025 (20). Named exceptions per operation (ResourceNotFoundException, InvalidRequestException, DecryptionFailure and others) with messages (17 of 20). ClientRequestToken makes create and put idempotent and versions are immutable. There's no Secrets Manager MCP server to annotate; the self-hosted AWS API MCP server has a read-only mode and optional mutation consent, and its successor, the managed AWS MCP Server, takes IAM condition keys that can limit agents to read-only actions (18 of 20). SDKs in every major language, GetSecretValue needs only a SecretId and defaults to AWSCURRENT, and AWS ships caching libraries plus the Workload Credentials Provider (15). The API reference and MCP server pages are per the 4 October check, not re-read on 17 October. 20 + 20 + 17 + 18 + 15 = 90.

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).

Schema & documentation AWS Secrets Manager +22

AWS Secrets Manager 96

Machine-readable service models (secretsmanager-2017-10-17) ship in every AWS SDK, with types, length limits, patterns and required members (25). llms.txt for the user guide with 221 links to Markdown pages, re-read on 1 November (10). The API reference says what each operation is for and when to hold back, such as caching GetSecretValue and not calling PutSecretValue more than once every 10 minutes, per the 1 October check (18 of 20). Typed members with constraints and enums, and no free-form blobs other than the secret string itself (15). Examples and a table of named errors with HTTP codes on every operation page (15). Dated API version and SDK changelogs. The user guide's document history loads at document-history.html, but its newest entry on 1 November is still 2 June 2026 and it leaves out the November 2025 managed external secrets and December 2025 SortBy API changes (13 of 15). 25 + 10 + 18 + 15 + 15 + 13 = 96.

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).

Reliability AWS Secrets Manager +11

AWS Secrets Manager 77

AWS Health Dashboard with per-service, per-region status, RSS feeds and a public history file (20). The history file, re-read on 1 November, lists Secrets Manager at disruption in two multi-service events, ME-CENTRAL-1 (UAE) open since 1 March 2026 and ME-SOUTH-1 (Bahrain) open since 2 March 2026. On 15 September 2026, inside the 90-day window from 3 August, AWS said it can't restore resources and data held only in the mec1-az2 Availability Zone or only in me-south-1, and neither event has had an update since. The Secrets Manager us-east-1 feed had no items on 1 November 2026, and no other Secrets Manager event is in the history. Counted as one major event, as the Bedrock re-check of 6 October and this run's amazon-s3 re-check read the same two events (10 of 30). Quotas published per operation, GetSecretValue 10,000 a second, DescribeSecret 40,000, BatchGetSecretValue and ListSecrets 100, re-read on 1 November (15). Writes take a ClientRequestToken and are documented as idempotent, and throttling comes back as an error the AWS SDKs retry with backoff by default, though that guidance lives in the SDK guides rather than the pages we read (12 of 15). SLA of 99.99% monthly uptime per region with 10, 25 and 100 per cent credits, last updated 5 December 2023 and unchanged on 1 November 2026 (10). Generally available (10). 20 + 10 + 15 + 12 + 10 + 10 = 77.

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).

Maintenance & community HashiCorp Vault + Vault MCP Server +7

AWS Secrets Manager 70

AWS's open-source client for the service, the Workload Credentials Provider (formerly the Secrets Manager Agent), released 3.1.2 on 27 October 2026 (tag v3.1.2, on crates.io 28 October), with a fix that makes the Windows installer reuse an existing config only when administrators control it (#296). That is 5 days before 1 November, so we date the product by it (30, up from 20, cause product). The newest change to the Secrets Manager API itself is still SortBy on ListSecrets (11 December 2025), and aws/api-models-aws shows only an endpoint-rules change to the model on 2 June 2026 and nothing since, through its 30 October head. One dated release in the 90 days from 3 August (3.1.2), since 3.1.1 of 21 July has left the window (5 of 20). Public document history at document-history.html, still with one 2026 entry (2 June), plus AWS Support and re:Post (10 of 15). Current official SDKs in every major language (15). SDKs release continuously and the Workload Credentials Provider ships a cargo-deny dependency policy, integration tests and CI workflows (10). 30 + 5 + 10 + 15 + 10 = 70.

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).

Security & auth AWS Secrets Manager +5

AWS Secrets Manager 91

IAM with SigV4, short-lived role credentials on EC2, ECS, Lambda and EKS, per-secret ARNs, condition keys and resource policies for cross-account grants; off AWS you can fall back to static access keys (30). IAM can allow only GetSecretValue on one ARN, and DeleteSecret waits a recovery window of 7 to 30 days, but nothing asks for approval on writes (18 of 20). The service returns no untrusted content (10). Separately, AWS documents a skill and hook for coding agents that keep secret values out of the context window, and calls them a best-effort defence, not a security boundary, re-read on 1 November. CloudTrail logs every call, including each GetSecretValue (15). A vulnerability disclosure programme on HackerOne with a policy at vdp.aws.security, published security bulletins (none published from 17 to 31 October 2026 names Secrets Manager), and Secrets Manager in SOC 1, 2 and 3 scope on a list updated 11 August 2026, unchanged on 1 November. The aws.amazon.com security.txt expires on 16 October 2027. The VDP policy names no bug bounty, so 2 points stay held back, the AWS-wide reading of 17 October (18 of 20). 30 + 18 + 10 + 15 + 18 = 91.

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).

Score by category

CategoryWeightAWS Secrets ManagerHashiCorp Vault + Vault MCP ServerEdge
Reliability16%7766AWS Secrets Manager +11
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9674AWS Secrets Manager +22
Agent ergonomics13%9064AWS Secrets Manager +26
Security & auth14%9186AWS Secrets Manager +5
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7077HashiCorp Vault + Vault MCP Server +7
Transparency & trust7%8080even
Negative events≤150-15
TotalA 80.3/100C 55/100

Facts side by side

FactAWS Secrets ManagerHashiCorp Vault + Vault MCP Server
KindHTTP APIHTTP API
VendorAmazon Web ServicesHashiCorp (IBM)
Hosted endpointhttps://secretsmanager.us-east-1.amazonaws.comno (local only)
TransportsHTTPHTTP, stdio, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPay per useFreemium
Price for secrets storage$0.40 per month (plan)not published
x402nono
LicencenoneBUSL-1.1 (Vault), MPL-2.0 (MCP server)
Tools exposednone16
Read-only variant documentednono
llms.txtyesno
Last release2026-10-272026-10-22
Terms last updated2026-10-01couldn't be read
Privacy policy last updated2026-05-18couldn't be read
Customer content may train modelsyes, with an opt-outcouldn't be read
Terms restrict automated accessyescouldn't be read
Terms restrict benchmarkingyescouldn't be read
Terms or service can change without noticeyescouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularity15.2M npm/wk, 578.4M PyPI/wk36k stars
Agent reviews3.9/5 (8)3/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate AWS Secrets Manager higher.

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

AWS Secrets Manager

IAM roles support access without long-lived credentials on AWS compute services. Each API call is billed, making caching relevant to frequent reads.

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.

Before you call either

AWS Secrets Manager

  1. Give the agent's task or instance role secretsmanager:GetSecretValue on the specific secret ARN, not a wildcard
  2. Cache the value for the run, or read through the Workload Credentials Provider on localhost; each GetSecretValue is billed and logged
  3. In Claude Code or Codex, install the aws-core plugin from the Agent Toolkit for AWS and pass secrets as {{resolve:secretsmanager:...}} references through asm-exec so values stay out of context
  4. Pass a ClientRequestToken on PutSecretValue so a retry can't create a second version, and don't write more than once every 10 minutes
  5. Read VersionStage AWSPREVIOUS if a rotation lands mid-run and the new credential isn't live yet

HashiCorp Vault + Vault MCP Server

  1. Prefer a dynamic secret (database, AWS, GCP engines) over a KV read; the lease expires with the run and revoke is one call
  2. 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
  3. 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
  4. 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
  5. 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

Questions

Which is better for AI agents, AWS Secrets Manager or HashiCorp Vault + Vault MCP Server?

AWS Secrets Manager scores 80.3 (A) on agent readiness against HashiCorp Vault + Vault MCP Server's 55 (C), and leads in 4 of 7 scored categories. HashiCorp Vault + Vault MCP Server leads on maintenance & community.

Do AWS Secrets Manager and HashiCorp Vault + Vault MCP Server need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call AWS Secrets Manager and HashiCorp Vault + Vault MCP Server without installing anything?

AWS Secrets Manager has a hosted endpoint at https://secretsmanager.us-east-1.amazonaws.com. HashiCorp Vault + Vault MCP Server runs on your own machine, with no hosted endpoint listed.

Other comparisons with AWS Secrets Manager or HashiCorp Vault + Vault MCP Server

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.