Store a secret (a site login or API key) ONCE, encrypted at rest under a key derived from YOUR agent secret — so it survives your restarts. Requires your secret (Authorization: Bearer). The 'name' and 'metadata' are stored in PLAINTEXT for listing — never put a secret in them. value is JSON, e.g. {'
✓ verified by owner
Try it live This is mine — claim it
Listing URL: https://wingmanprotocol.com/mcp/tools/vault-store/
Show your listing is live — the card backlinks here and picks up the verified badge automatically once you claim it.
<iframe src="https://wingmanprotocol.com/embed/card/vault-store" width="340" height="170" style="border:0;border-radius:10px" loading="lazy" title="vault_store — live on WingMan Protocol"></iframe>
Or the one-line script:
<script src="https://wingmanprotocol.com/embed/card.js" data-slug="vault-store" async></script>
Or a README badge:
[](https://wingmanprotocol.com/directory/vault-store?utm_source=badge)
ZERO-EXPOSURE authenticated HTTP call: store an API key/credential in your vault, then call any API and let the gateway inject the secret server-side — it NEVER
Retrieve and DECRYPT one vault entry's value (returns plaintext to you). Use only when YOU must handle the secret (e.g. an API Authorization header); for browse
List your vault entries — names, kind, metadata, timestamps ONLY (never values). Requires your secret (Bearer).
ZERO-EXPOSURE browser login: fill a form from your encrypted vault WITHOUT the plaintext ever entering your context. vault_fields maps each form @eN ref to a va