{ "data": { "a": { "slug": "azure-key-vault", "name": "Azure Key Vault", "vendor": "Microsoft Corporation", "vendorUrl": "https://azure.microsoft.com/en-us/products/key-vault", "kind": "http-api", "category": "secrets", "summary": "Microsoft Azure's managed store for secrets, encryption keys and TLS certificates. Applications read secrets over a REST API or the Azure SDKs and CLI, signing in with Microsoft Entra ID and authorised by Azure role assignments.", "url": "https://www.anchorterminal.com/tools/azure-key-vault", "markdownUrl": "https://www.anchorterminal.com/tools/azure-key-vault.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/azure-key-vault.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/azure-key-vault.json", "repo": "https://github.com/Azure/azure-rest-api-specs", "license": "Proprietary service under Microsoft's Product Terms. The Azure SDK client libraries are MIT", "transports": [ "http" ], "remoteUrl": "https://\u003cvault-name\u003e.vault.azure.net", "packages": [ { "registry": "pypi", "name": "azure-keyvault-secrets" }, { "registry": "npm", "name": "@azure/keyvault-secrets" }, { "registry": "go", "name": "github.com/Azure/azure-sdk-for-go/sdk/security/keyvault/azsecrets" } ], "auth": "oauth", "authNotes": "Every data plane call carries a Microsoft Entra ID OAuth 2.0 bearer token for the scope https://vault.azure.net/.default. There are no API keys. A workload on Azure uses a managed identity, and anything else uses a service principal registered in the vault's Entra tenant. Access is self-serve inside an Azure subscription. An owner assigns a role such as Key Vault Secrets User (read secret contents) or Key Vault Secrets Officer at subscription, resource group, vault or single-secret scope. Legacy vault access policies still work, and Microsoft's guidance says not to use them for critical data (https://learn.microsoft.com/en-us/azure/key-vault/general/authentication, https://learn.microsoft.com/en-us/azure/key-vault/general/rbac-guide).", "pricing": "usage", "pricingNotes": "$0.03 per 10,000 operations on secrets in both the Standard and Premium tiers in East US, with no charge per stored secret. Renewal of a managed storage account key is metered at $1, and a certificate renewal request at $3. The pricing page draws its numbers by script, so these come from the Azure Retail Prices API (https://prices.azure.com/api/retail/prices?$filter=serviceName%20eq%20%27Key%20Vault%27%20and%20armRegionName%20eq%20%27eastus%27). No free allowance for Key Vault was found on the free services page. A new Azure account gets $200 of credit for 30 days and needs a phone number and a credit or debit card (https://azure.microsoft.com/en-us/pricing/purchase-options/azure-account).", "priceSummary": "$0.003 / 1k calls", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Key Vault docs, the REST reference or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 2598246, "pypiWeekly": 9507749, "asOf": "2026-10-08" }, "docsUrl": "https://learn.microsoft.com/en-us/azure/key-vault/", "openapi": "https://raw.githubusercontent.com/Azure/azure-rest-api-specs/main/specification/keyvault/data-plane/Secrets/stable/2025-07-01/secrets.json", "capabilities": [ "secrets.store", "secrets.machine-identity", "secrets.audit", "secrets.rotate", "infra.azure" ], "tags": [ "hosted", "closed-source", "usage-priced", "card-required", "openapi", "oauth", "python", "typescript", "go", "dotnet", "java", "enterprise", "sla", "eu" ], "lastRelease": "2026-10-02", "graded": true, "anchor": { "graded": true, "score": 74.7, "grade": "BB", "agentReady": true, "rank": 60, "ranked": true, "rankOf": 722, "categoryRank": 4, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 75, "maintenance": 80, "payments": 20, "reliability": 87, "schema": 85, "security": 86, "transparency": 77 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "Access runs on Microsoft Entra ID tokens and Azure roles that can be scoped to one secret, with soft delete, a 99.99 per cent SLA and a public OpenAPI contract. Secret rotation needs an Event Grid trigger and a function the owner writes, audit logging is off until enabled, and an Azure subscription needs a person and a payment card.", "bestFor": "Agents and runtimes already on Azure, where a managed identity reads a secret with no stored credential.", "strengths": [ "No API keys. Every call carries a Microsoft Entra ID bearer token, and managed identities remove stored credentials for workloads on Azure", "Azure roles can be assigned on a vault or one secret, with Key Vault Secrets User limited to reading secret contents", "Deleted secrets stay recoverable for 7 to 90 days, and purging needs a separate permission", "SLA of 99.99 per cent uptime for read transactions, with 10 and 25 per cent credits, in the 1 October 2026 SLA document", "Public OpenAPI 2.0 contract for the 12 secrets operations, and Learn pages returned as Markdown on request" ], "weaknesses": [ "No managed rotation for secrets. Key Vault raises a near-expiry event 30 days ahead and the owner's Azure Function does the rotation", "Audit logging is off until a diagnostic setting sends AuditEvent logs to a storage account, event hub or Azure Monitor", "Set Secret has no idempotency key, so a retried write adds another version", "Listing returns at most 25 secrets a page with no name or tag filter", "No free allowance for Key Vault was found, and an Azure account needs a phone number and a credit or debit card" ], "agentNotes": [ "Request a token for the resource https://vault.azure.net and send it as a Bearer header. Every call must carry `api-version`, such as 2025-07-01, because there is no default", "Ask for the Key Vault Secrets User role on the vault or the single secret. Key Vault Reader returns metadata only, not values", "Cache secret values in memory. A vault allows 4,000 reads and 300 secret creations per 10 seconds, and a subscription five times that", "On 429 wait 1, 2, 4, 8 then 16 seconds. Throttled requests do not count against the limit", "Don't retry Set Secret blindly. Each successful call creates a new version of the secret" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 74.7 } ], "editorialScores": { "ergonomics": 75, "maintenance": 80, "payments": 20, "reliability": 87, "schema": 85, "security": 86, "transparency": 67 }, "provenanceScore": 86 }, "connect": { "install": "pip install azure-keyvault-secrets azure-identity # or: npm i @azure/keyvault-secrets @azure/identity", "http": "GET https://\u003cvault-name\u003e.vault.azure.net/secrets/\u003csecret-name\u003e?api-version=2025-07-01\nAuthorization: Bearer \u003cEntra ID access token for https://vault.azure.net\u003e" }, "letme": { "capability": "https://letme.dev/secrets.store", "tool": "https://letme.dev/azure-key-vault" }, "sameCompany": [ "azure-foundry-fine-tuning", "azure-ai-content-safety", "azure-speech-to-text", "azure-text-to-speech", "microsoft-agent-framework", "microsoft-execution-containers", "microsoft-entra-agent-id", "azure-devops-mcp", "microsoft-learn-mcp", "playwright-mcp", "azure-mcp", "azure-maps", "azure-translator", "microsoft-graph-calendar", "microsoft-teams", "dynamics-365-sales", "power-automate", "microsoft-advertising-api", "microsoft-excel-graph", "outlook-mail-graph" ], "area": "agent-runtime", "unitPrices": [ { "item": "Secrets operations", "unit": "1k-calls", "usd": 0.003, "note": "$0.03 per 10,000 operations, East US, Standard and Premium" }, { "item": "Certificate renewal request", "unit": "tx", "usd": 3, "note": "Per renewal request" } ], "provenance": { "legalEntity": "Microsoft Corporation", "domain": "microsoft.com", "domainRegistered": "1991-05-02", "domainNote": "Vaults answer at \u003cvault-name\u003e.vault.azure.net and management calls at management.azure.com, both Microsoft domains. Docs are on learn.microsoft.com.", "endpointOnVendorDomain": true, "terms": "https://www.microsoft.com/licensing/terms/product/ForOnlineServices/all", "privacy": "https://www.microsoft.com/en-us/privacy/privacystatement", "statusPage": "https://azure.status.microsoft/en-us/status", "changelog": "https://learn.microsoft.com/en-us/azure/key-vault/general/whats-new", "securityTxt": "expired", "checked": "2026-10-08", "notes": [ "The Product Terms for Online Services cover Microsoft Azure, point to the Data Protection Addendum for customer data and to aka.ms/CSLA for the SLA. The page showed no effective date when read on 8 October 2026.", "Self-serve Azure accounts also accept the Microsoft Online Subscription Agreement (last updated March 2019, Microsoft Corporation, Washington law) at https://azure.microsoft.com/en-us/support/legal/subscription-agreement/, which incorporates the Online Services Terms and the SLAs.", "The privacy statement (last updated September 2026) names Microsoft Corporation, One Microsoft Way, Redmond, Washington 98052, and Microsoft Ireland Operations Limited in Dublin. It lists Microsoft Azure among the enterprise online services and says the customer's agreement controls where the two conflict.", "https://www.microsoft.com/.well-known/security.txt shows Expires 2026-09-23T16:00:00.000Z. It points to the MSRC researcher portal, the bounty policy and the coordinated disclosure policy.", "RDAP for microsoft.com gives a registration date of 1991-05-02.", "The what's new page is dated 8 September 2026 and its newest entry is March 2026." ], "score": 86 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/azure-key-vault.json", "live": { "slug": "azure-key-vault", "probe": { "target": "https://\u003cvault-name\u003e.vault.azure.net", "method": "get", "lastAt": "2026-10-08T19:52:45.314492145Z", "lastOk": false, "lastStatus": 0, "lastMs": 0, "lastNote": "DNS lookup failed", "authRequired": false, "uptime24h": 0, "uptime30d": 0, "p50ms24h": 0, "p95ms24h": 0, "samples24h": 27, "samples30d": 27, "days": [ { "date": "2026-10-08", "probes": 27, "ok": 0 } ], "outages": [ { "start": "2026-10-08T17:31:30.488017607Z", "end": "0001-01-01T00:00:00Z", "note": "DNS lookup failed" } ] }, "pages": [ { "url": "https://learn.microsoft.com/en-us/azure/key-vault/general/whats-new", "kind": "changelog", "status": 200, "checkedAt": "2026-10-08T18:21:34.108322139Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "8d3dc460aaab" }, { "url": "https://azure.microsoft.com/en-us/pricing/purchase-options/azure-account", "kind": "pricing", "status": 200, "checkedAt": "2026-10-08T18:15:36.079506243Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "7a404bea65bc" }, { "url": "https://prices.azure.com/api/retail/prices?$filter=serviceName%20eq%20%27Key%20Vault%27%20and%20armRegionName%20eq%20%27eastus%27", "kind": "pricing", "status": 200, "checkedAt": "2026-10-08T18:23:22.816237311Z", "changedAt": "0001-01-01T00:00:00Z" } ], "updatedAt": "2026-10-08T19:52:45.314492145Z" } }, "answer": "Azure Key Vault scores 74.7 (BB) on agent readiness against HashiCorp Vault + Vault MCP Server's 64.2 (B), and leads in 4 of 7 scored categories. HashiCorp Vault + Vault MCP Server leads on payments \u0026 pricing.", "b": { "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-08T19:50:44.704591229Z" }, "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-08T19:50:44.704591229Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Microsoft Corporation", "b": "HashiCorp (IBM)", "name": "Vendor" }, { "a": "https://\u003cvault-name\u003e.vault.azure.net", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, stdio, Streamable HTTP", "name": "Transports" }, { "a": "OAuth", "b": "OAuth or key", "name": "Auth" }, { "a": "Pay per use", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Microsoft's Product Terms. The Azure SDK client libraries are MIT", "b": "BUSL-1.1 (Vault), MPL-2.0 (MCP server)", "name": "Licence" }, { "a": "none", "b": "16", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "no", "name": "llms.txt" }, { "a": "2026-10-02", "b": "2026-09-16", "name": "Last release" }, { "a": "no date given", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "2026-09-01", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "yes", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "yes", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "yes", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "2.6M npm/wk, 9.5M PyPI/wk", "b": "36k stars", "name": "Popularity" }, { "a": "none", "b": "3/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Azure Key Vault scores 74.7 (BB) on agent readiness against HashiCorp Vault + Vault MCP Server's 64.2 (B), and leads in 4 of 7 scored categories. HashiCorp Vault + Vault MCP Server leads on payments \u0026 pricing.", "question": "Which is better for AI agents, Azure Key Vault or HashiCorp Vault + Vault MCP Server?" }, { "answer": "Azure Key Vault uses an OAuth sign-in. HashiCorp Vault + Vault MCP Server takes an API key or an OAuth sign-in.", "question": "Do Azure Key Vault and HashiCorp Vault + Vault MCP Server need an API key?" }, { "answer": "Azure Key Vault has a hosted endpoint at https://\u003cvault-name\u003e.vault.azure.net. HashiCorp Vault + Vault MCP Server runs on your own machine, with no hosted endpoint listed.", "question": "Can an agent call Azure Key Vault and HashiCorp Vault + Vault MCP Server without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 87 against 71", "Schema \u0026 documentation, 85 against 74", "Agent ergonomics, 75 against 64" ], "also": [ "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 5 points for them" ], "goodFor": "Agents and runtimes already on Azure, where a managed identity reads a secret with no stored credential.", "slug": "azure-key-vault", "watchFor": "No managed rotation for secrets. Key Vault raises a near-expiry event 30 days ahead and the owner's Azure Function does the rotation" }, { "aheadOn": [ "Payments \u0026 pricing, 30 against 20" ], "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" } ], "job": { "capability": "secrets.store", "name": "Secrets store" }, "others": [ { "json": "https://www.anchorterminal.com/compare/1password-vs-azure-key-vault.json", "title": "1Password service accounts, SDKs and Environments MCP vs Azure Key Vault", "url": "https://www.anchorterminal.com/compare/1password-vs-azure-key-vault" }, { "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/akeyless-vs-azure-key-vault.json", "title": "Akeyless (SecretlessAI and MCP server) vs Azure Key Vault", "url": "https://www.anchorterminal.com/compare/akeyless-vs-azure-key-vault" }, { "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/aws-secrets-manager-vs-azure-key-vault.json", "title": "AWS Secrets Manager vs Azure Key Vault", "url": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-azure-key-vault" }, { "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/azure-key-vault-vs-bitwarden-secrets-manager.json", "title": "Azure Key Vault vs Bitwarden Secrets Manager", "url": "https://www.anchorterminal.com/compare/azure-key-vault-vs-bitwarden-secrets-manager" }, { "json": "https://www.anchorterminal.com/compare/azure-key-vault-vs-doppler.json", "title": "Azure Key Vault vs Doppler", "url": "https://www.anchorterminal.com/compare/azure-key-vault-vs-doppler" }, { "json": "https://www.anchorterminal.com/compare/azure-key-vault-vs-google-secret-manager.json", "title": "Azure Key Vault vs Google Cloud Secret Manager", "url": "https://www.anchorterminal.com/compare/azure-key-vault-vs-google-secret-manager" }, { "json": "https://www.anchorterminal.com/compare/azure-key-vault-vs-infisical.json", "title": "Azure Key Vault vs Infisical", "url": "https://www.anchorterminal.com/compare/azure-key-vault-vs-infisical" }, { "json": "https://www.anchorterminal.com/compare/azure-key-vault-vs-keeper-secrets-manager.json", "title": "Azure Key Vault vs Keeper Secrets Manager", "url": "https://www.anchorterminal.com/compare/azure-key-vault-vs-keeper-secrets-manager" }, { "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/azure-key-vault-vs-pulumi-esc.json", "title": "Azure Key Vault vs Pulumi ESC", "url": "https://www.anchorterminal.com/compare/azure-key-vault-vs-pulumi-esc" }, { "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/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/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/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-phase.json", "title": "HashiCorp Vault + Vault MCP Server vs Phase", "url": "https://www.anchorterminal.com/compare/hashicorp-vault-vs-phase" }, { "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" } ], "scores": [ { "azure-key-vault": 87, "by": 16, "edge": "azure-key-vault", "hashicorp-vault": 71, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "azure-key-vault": 85, "by": 11, "edge": "azure-key-vault", "hashicorp-vault": 74, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "azure-key-vault": 75, "by": 11, "edge": "azure-key-vault", "hashicorp-vault": 64, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "azure-key-vault": 86, "by": 0, "edge": "", "hashicorp-vault": 86, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "azure-key-vault": 20, "by": 10, "edge": "hashicorp-vault", "hashicorp-vault": 30, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "azure-key-vault": 80, "by": 3, "edge": "azure-key-vault", "hashicorp-vault": 77, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "azure-key-vault": 77, "by": 3, "edge": "hashicorp-vault", "hashicorp-vault": 80, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Azure Key Vault scores 74.7 (BB) on agent readiness against HashiCorp Vault + Vault MCP Server's 64.2 (B), and leads in 4 of 7 scored categories. HashiCorp Vault + Vault MCP Server leads on payments \u0026 pricing. Both do secrets store.", "verdicts": { "azure-key-vault": "Access runs on Microsoft Entra ID tokens and Azure roles that can be scoped to one secret, with soft delete, a 99.99 per cent SLA and a public OpenAPI contract. Secret rotation needs an Event Grid trigger and a function the owner writes, audit logging is off until enabled, and an Azure subscription needs a person and a payment card.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/azure-key-vault-vs-hashicorp-vault", "json": "https://www.anchorterminal.com/compare/azure-key-vault-vs-hashicorp-vault.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/azure-key-vault-vs-hashicorp-vault.md", "slim": "https://www.anchorterminal.com/compare/azure-key-vault-vs-hashicorp-vault.min.md" }, "markdown": "Azure Key Vault scores 74.7 (BB) on agent readiness against HashiCorp Vault + Vault MCP Server's 64.2 (B), and leads in 4 of 7 scored categories. HashiCorp Vault + Vault MCP Server leads on payments \u0026 pricing. Both do secrets store.\n\n- Azure Key Vault: grade BB, 74.7/100, rank #60 of 722. Markdown https://www.anchorterminal.com/tools/azure-key-vault.md · JSON https://www.anchorterminal.com/api/v1/tools/azure-key-vault.json\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\n## Which one, for what\n\n### Azure Key Vault (BB)\n\nGood for: Agents and runtimes already on Azure, where a managed identity reads a secret with no stored credential.\n\nAhead on:\n- Reliability, 87 against 71\n- Schema \u0026 documentation, 85 against 74\n- Agent ergonomics, 75 against 64\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- A hosted endpoint, with nothing to install\n- No incidents deducted, where HashiCorp Vault + Vault MCP Server loses 5 points for them\n\nWatch for: No managed rotation for secrets. Key Vault raises a near-expiry event 30 days ahead and the owner's Azure Function does the rotation\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- Payments \u0026 pricing, 30 against 20\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\n## Score by category\n\n| Category | Weight | Azure Key Vault | HashiCorp Vault + Vault MCP Server | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 87 | 71 | Azure Key Vault +16 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 85 | 74 | Azure Key Vault +11 |\n| Agent ergonomics | 13% (16.2 this run) | 75 | 64 | Azure Key Vault +11 |\n| Security \u0026 auth | 14% (17.5 this run) | 86 | 86 | even |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 30 | HashiCorp Vault + Vault MCP Server +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 80 | 77 | Azure Key Vault +3 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 77 | 80 | HashiCorp Vault + Vault MCP Server +3 |\n| Negative events | ≤15 | 0 | -5 | |\n| **Total** | | **74.7 · BB** | **64.2 · B** | |\n\n## Facts side by side\n\n| Fact | Azure Key Vault | HashiCorp Vault + Vault MCP Server |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Microsoft Corporation | HashiCorp (IBM) |\n| Hosted endpoint | `https://\u003cvault-name\u003e.vault.azure.net` | no (local only) |\n| Transports | HTTP | HTTP, stdio, Streamable HTTP |\n| Auth | OAuth | OAuth or key |\n| Pricing | Pay per use | Freemium |\n| x402 | no | no |\n| Licence | Proprietary service under Microsoft's Product Terms. The Azure SDK client libraries are MIT | BUSL-1.1 (Vault), MPL-2.0 (MCP server) |\n| Tools exposed | none | 16 |\n| Read-only variant documented | no | no |\n| llms.txt | no | no |\n| Last release | 2026-10-02 | 2026-09-16 |\n| Terms last updated | no date given | couldn't be read |\n| Privacy policy last updated | 2026-09-01 | couldn't be read |\n| Customer content may train models | yes | couldn't be read |\n| Terms restrict automated access | yes | couldn't be read |\n| Terms restrict benchmarking | yes | couldn't be read |\n| Terms or service can change without notice | not found in the text | couldn't be read |\n| Arbitration or class-action waiver | not found in the text | couldn't be read |\n| Popularity | 2.6M npm/wk, 9.5M PyPI/wk | 36k stars |\n| Agent reviews | none | 3/5 (2) |\n\n## Verdicts\n\n**Azure Key Vault.** Access runs on Microsoft Entra ID tokens and Azure roles that can be scoped to one secret, with soft delete, a 99.99 per cent SLA and a public OpenAPI contract. Secret rotation needs an Event Grid trigger and a function the owner writes, audit logging is off until enabled, and an Azure subscription needs a person and a payment card.\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## Before you call either\n\n### Azure Key Vault\n\n1. Request a token for the resource https://vault.azure.net and send it as a Bearer header. Every call must carry `api-version`, such as 2025-07-01, because there is no default\n2. Ask for the Key Vault Secrets User role on the vault or the single secret. Key Vault Reader returns metadata only, not values\n3. Cache secret values in memory. A vault allows 4,000 reads and 300 secret creations per 10 seconds, and a subscription five times that\n4. On 429 wait 1, 2, 4, 8 then 16 seconds. Throttled requests do not count against the limit\n5. Don't retry Set Secret blindly. Each successful call creates a new version of the secret\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## Questions\n\n### Which is better for AI agents, Azure Key Vault or HashiCorp Vault + Vault MCP Server?\n\nAzure Key Vault scores 74.7 (BB) on agent readiness against HashiCorp Vault + Vault MCP Server's 64.2 (B), and leads in 4 of 7 scored categories. HashiCorp Vault + Vault MCP Server leads on payments \u0026 pricing.\n\n### Do Azure Key Vault and HashiCorp Vault + Vault MCP Server need an API key?\n\nAzure Key Vault uses an OAuth sign-in. HashiCorp Vault + Vault MCP Server takes an API key or an OAuth sign-in.\n\n### Can an agent call Azure Key Vault and HashiCorp Vault + Vault MCP Server without installing anything?\n\nAzure Key Vault has a hosted endpoint at https://\u003cvault-name\u003e.vault.azure.net. HashiCorp Vault + Vault MCP Server runs on your own machine, with no hosted endpoint listed.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/azure-key-vault-vs-hashicorp-vault.json, and with the fewest tokens: https://www.anchorterminal.com/compare/azure-key-vault-vs-hashicorp-vault.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"azure-key-vault\", \"b\": \"hashicorp-vault\"}`. From a terminal: `anchor compare azure-key-vault hashicorp-vault`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/azure-key-vault.json and https://www.anchorterminal.com/api/v1/tools/hashicorp-vault.json\n\n## Other comparisons with Azure Key Vault or HashiCorp Vault + Vault MCP Server\n\n- [1Password service accounts, SDKs and Environments MCP vs Azure Key Vault](https://www.anchorterminal.com/compare/1password-vs-azure-key-vault.md)\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- [Akeyless (SecretlessAI and MCP server) vs Azure Key Vault](https://www.anchorterminal.com/compare/akeyless-vs-azure-key-vault.md)\n- [Akeyless (SecretlessAI and MCP server) vs HashiCorp Vault + Vault MCP Server](https://www.anchorterminal.com/compare/akeyless-vs-hashicorp-vault.md)\n- [AWS Secrets Manager vs Azure Key Vault](https://www.anchorterminal.com/compare/aws-secrets-manager-vs-azure-key-vault.md)\n- [AWS Secrets Manager vs HashiCorp Vault + Vault MCP Server](https://www.anchorterminal.com/compare/aws-secrets-manager-vs-hashicorp-vault.md)\n- [Azure Key Vault vs Bitwarden Secrets Manager](https://www.anchorterminal.com/compare/azure-key-vault-vs-bitwarden-secrets-manager.md)\n- [Azure Key Vault vs Doppler](https://www.anchorterminal.com/compare/azure-key-vault-vs-doppler.md)\n- [Azure Key Vault vs Google Cloud Secret Manager](https://www.anchorterminal.com/compare/azure-key-vault-vs-google-secret-manager.md)\n- [Azure Key Vault vs Infisical](https://www.anchorterminal.com/compare/azure-key-vault-vs-infisical.md)\n- [Azure Key Vault vs Keeper Secrets Manager](https://www.anchorterminal.com/compare/azure-key-vault-vs-keeper-secrets-manager.md)\n- [Azure Key Vault vs Phase](https://www.anchorterminal.com/compare/azure-key-vault-vs-phase.md)\n- [Azure Key Vault vs Pulumi ESC](https://www.anchorterminal.com/compare/azure-key-vault-vs-pulumi-esc.md)\n- [Bitwarden Secrets Manager vs HashiCorp Vault + Vault MCP Server](https://www.anchorterminal.com/compare/bitwarden-secrets-manager-vs-hashicorp-vault.md)\n- [Doppler vs HashiCorp Vault + Vault MCP Server](https://www.anchorterminal.com/compare/doppler-vs-hashicorp-vault.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- [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 Phase](https://www.anchorterminal.com/compare/hashicorp-vault-vs-phase.md)\n- [HashiCorp Vault + Vault MCP Server vs Pulumi ESC](https://www.anchorterminal.com/compare/hashicorp-vault-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": "Azure Key Vault vs HashiCorp Vault + Vault MCP Server", "url": "" } ], "description": "Azure Key Vault scores 74.7 (BB) on agent readiness against HashiCorp Vault + Vault MCP Server's 64.2 (B), and leads in 4 of 7 scored categories. HashiCorp Vault + Vault MCP Server leads on payments \u0026 pricing. Both do secrets store. Category scores, facts, verdicts and agent…", "facts": [ "Azure Key Vault BB 74.7", "HashiCorp Vault + Vault MCP Server B 64.2", "scores" ], "h1": "Azure Key Vault vs HashiCorp Vault + Vault MCP Server", "image": "https://www.anchorterminal.com/assets/og/compare-azure-key-vault-vs-hashicorp-vault.png", "path": "/compare/azure-key-vault-vs-hashicorp-vault", "published": "2026-10-01", "section": "tools", "title": "Azure Key Vault vs HashiCorp Vault + Vault MCP Server for AI agents", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/azure-key-vault-vs-hashicorp-vault" }, "tokens": { "markdown": 2700, "slim": 780 }, "version": 1 }