Vault MCP Server
HashiCorp an IBM Company · Cybersecurity & IT
Certification per AWS Marketplace.
Evidence tier Source Confirmed · 4 captures on record
What the publisher says
As described on AWS Marketplace.
The Vault MCP Server enables operators to use natural language to perform basic queries and operations in Vault, which would otherwise require traditional methods of issuing requests to Vault via Vault API.
For this experimental release, Vault operators can configure Vault MCP server in local standard input/output (stdio) mode or streamableHTTP transport and interacts with Vault APIs using any MCP client.
Show the rest of the publisher’s description (9 more lines)
We are seeking feedback from Vault operators and users regarding the usefulness of such capabilities. Based on the customer feedback, we plan to offer a richer set of capabilities to perform additional queries and/or otherwise interact with Vault APIs and eco-system plugins, including remote versions of the MCP Servers with security features.
Note: This Vault MCP Server release is experimental in nature and intended for development, testing, and evaluation purposes. Use of the Vault MCP server in production settings is not recommended at this time.
Supported Vault API commands include:
- Create new mounts in Vault (KV v1, KV v2)
- List all available mounts
- Deletes a mount
- Write secrets to KV mounts
- Read secrets from KV mounts
- List all secrets under a path
Highlights
Highlighted by the publisher on AWS Marketplace.
Read or Write key/value (KV v1, KV v2) secrets to Vault
Create or delete mounts in Vault (KV v1, KV v2)
List all secrets or mounts in Vault
Agent build and provenance
See the full provenance
The layer-by-layer build, the evidence behind each claim, the risk basis and the cross-marketplace links are open to any account. Some rows are disclosed, some the source leaves Unknown; a free account shows you which.
Compliance
- FedRAMPConfirmedNot listed90%, registry-checkedNo FedRAMP Marketplace entry matched this vendor's domain, checked 2026-08-27registry recordas observed 2026-08-27
Confirmed means matched to a public authoritative registry. Claimed means the vendor or its listing states it, not yet cross-checked. A framework not shown was not found in any source we hold, which is not evidence against it. Not listed means a scoped registry check found no match for this vendor's domain: a No is a scoped registry check, not a compliance judgment. Confidence bands: 95% domain-verified, 90% registry-checked, 80% self-attested, 70% weak signal. Self-attested items marked “vendor's site” are gathered from the vendor's own website and are not verified by us.
Sources
Linked repositories
Unknown means this listing does not publish a repository. It is not a statement that the code is closed, and a linked repository is not a claim that the publisher wrote it: the registry computes that relationship privately and does not publish it.
Evidence risk is the share of the build you cannot see before you deploy, not a security rating. Sign in to see the layer-by-layer basis for this band.