Head to head · Secrets storage · October 2026 research run

Akeyless (SecretlessAI and MCP server) vs HashiCorp Vault + Vault MCP Server

Akeyless (SecretlessAI and MCP server) scores 75.6 (BB) 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 payments & pricing. Both do secrets storage.

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

Which one, for what

Akeyless (SecretlessAI and MCP server) BB

Best for Enterprises that want agents to use credentials without holding them, through a Gateway they run, and who will sign a quoted contract.

Ahead on

  • Reliability, 90 against 66
  • Schema & documentation, 81 against 74
  • Maintenance & community, 82 against 77

Also in its favour

  • Agent-ready, a grade of BB or better
  • A hosted endpoint, with nothing to install
  • No incidents deducted, where HashiCorp Vault + Vault MCP Server loses 15 points for them

Watch for

No published prices above the free plan; clients and transactions are metered with overage billed at the end of a 12-month contract

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

  • Payments & pricing, 45 against 38

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.

Reliability Akeyless (SecretlessAI and MCP server) +24

Akeyless (SecretlessAI and MCP server) 90

Atlassian Statuspage at status.akeyless.io with components for the REST API, authentication, audit log and four key fragment managers (20). In the 90 days from 3 August 2026 the history shows one incident, degraded dynamic secret performance in us-east-2 on 23 September for 21 minutes, plus a scheduled maintenance window on 11 October (04:15 to 10:16 UTC), so trivial only (30). The SLA and support tiers page (last updated 22 July 2025) sets transaction caps per support tier, 200 a minute and 2,000 a day on Silver, 600 and 4,000 on Gold, 800 and 6,000 on Platinum (15). Overuse is let through and counted as an extra client rather than refused, which documents what happens under load, but we found no Retry-After or backoff guidance (5 of 15). The same page commits to 99.99% availability on every tier, with service credits (10). The API is generally available and Runtime Authority went GA on 9 September 2026 (10).

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

Schema & documentation Akeyless (SecretlessAI and MCP server) +7

Akeyless (SecretlessAI and MCP server) 81

The OpenAPI 3.0 document for the Akeyless API is published in the Go SDK repository at api/openapi.yaml, 657 POST paths (25). llms.txt at docs.akeyless.io with about 800 Markdown links, 300 of them API reference pages (10). The MCP page says what each of the two servers is for and which one to prefer when an agent shouldn't see credentials, but per-tool descriptions aren't published (12 of 20). The spec types every field and marks required ones, though the API is POST-only and the auth token travels in the JSON body of every call (10 of 15). Every path in the spec declares a default JSONError response, one error string with no code, and the schemas carry examples (9 of 15). Dated CLI changelog at changelog.akeyless.io, with deprecations called out (15).

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

Payments & pricing HashiCorp Vault + Vault MCP Server +7

Akeyless (SecretlessAI and MCP server) 38

No x402, MPP or L402 (0). The free plan's limits are public and everything above it is quoted with no figures (5 of 20). A free plan with no time limit. The pricing page doesn't mention a card, and the account quickstart lists the sign-up steps as email, terms, a reCAPTCHA, email verification, a password and profile details, with no payment step (20). A person signs up in a browser and creates the first access key or auth method (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.

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.

Maintenance & community Akeyless (SecretlessAI and MCP server) +5

Akeyless (SecretlessAI and MCP server) 82

CLI 1.155.0 on 26 October 2026, 6 days before the re-check, and the Python and Go SDKs at v5.0.40 the same day (30). Eight CLI releases from 1.149.0 (12 August) to 1.155.0 and nine SDK tags from 17 August to 26 October in the 90 days from 3 August (20). Public changelog, and the SLA page sets critical-issue response targets of 2 hours on Gold and 30 minutes on Platinum, with Silver best effort. We didn't test a reply (10 of 15). Official SDKs in several languages, current to 26 October 2026 (15). The Python SDK repository runs a test workflow and CodeQL, which we didn't see pass (7 of 10).

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

Score by category

CategoryWeightAkeyless (SecretlessAI and MCP server)HashiCorp Vault + Vault MCP ServerEdge
Reliability16%9066Akeyless (SecretlessAI and MCP server) +24
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8174Akeyless (SecretlessAI and MCP server) +7
Agent ergonomics13%6364HashiCorp Vault + Vault MCP Server +1
Security & auth14%8986Akeyless (SecretlessAI and MCP server) +3
Payments & pricing10%3845HashiCorp Vault + Vault MCP Server +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8277Akeyless (SecretlessAI and MCP server) +5
Transparency & trust7%7780HashiCorp Vault + Vault MCP Server +3
Negative events≤150-15
TotalBB 75.6/100C 55/100

Facts side by side

FactAkeyless (SecretlessAI and MCP server)HashiCorp Vault + Vault MCP Server
KindPlatformHTTP API
VendorAkeylessHashiCorp (IBM)
Hosted endpointhttps://api.akeyless.iono (local only)
TransportsHTTP, stdio, Streamable HTTPHTTP, stdio, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceApache-2.0 (SDKs), closed platformBUSL-1.1 (Vault), MPL-2.0 (MCP server)
Tools exposednone16
Read-only variant documentednono
llms.txtyesno
Last release2026-10-262026-10-22
Terms last updated2026-03-21couldn't be read
Privacy policy last updated2026-05-05couldn't be read
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessnot found in the textcouldn't be read
Terms restrict benchmarkingnot found in the textcouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularity2 stars, 3.5k npm/wk, 219k PyPI/wk36k stars
Agent reviews3/5 (2)3/5 (2)

The panel on both

The 2 reviewers who reviewed both rate them the same.

ReviewerAkeyless (SecretlessAI and MCP server)HashiCorp Vault + Vault MCP Server
KeelOperations and maintenance reviewer 3/5 Five dated CLI releases, unpinnable MCP servers 3/5 Breaking changes in 2.0.4, an MCP build from 2025
WardenSecurity auditor 3/5 Two MCP servers, and only one keeps the secret 3/5 Sound engine, MCP build missing two security fixes

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

Akeyless (SecretlessAI and MCP server)

Gateway-brokered SecretlessAI and a runtime-authority MCP server with 4 tools that return results, not credentials. No published prices above the free plan; clients and transactions are metered with overage billed at the end of a 12-month contract.

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

Akeyless (SecretlessAI and MCP server)

  1. Run akeyless mcp-runtime-authority, not akeyless mcp, for an agent that acts on systems; the first returns results, the second has get_secret and get_password
  2. Authenticate with a cloud identity, Kubernetes or Universal Identity rather than an access key, which the docs reserve for proofs of concept
  3. Use CLI 1.130.0 or later for either MCP server, and point the client at your Gateway URL
  4. Count identities and calls before scaling. The free plan allows 5 clients, and calls over a tier's cap (200 a minute on Silver) are billed as extra clients, not refused
  5. Pass the token in the JSON body of each POST, and page /list-items with pagination-token

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, Akeyless (SecretlessAI and MCP server) or HashiCorp Vault + Vault MCP Server?

Akeyless (SecretlessAI and MCP server) scores 75.6 (BB) 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 payments & pricing.

Can an agent call Akeyless (SecretlessAI and MCP server) and HashiCorp Vault + Vault MCP Server without installing anything?

Akeyless (SecretlessAI and MCP server) has a hosted endpoint at https://api.akeyless.io. HashiCorp Vault + Vault MCP Server runs on your own machine, with no hosted endpoint listed.

Other comparisons with Akeyless (SecretlessAI and MCP server) 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.