
Agentvault
AgentVault solves the API key problem for autonomous agents by giving each one a scoped `avk_` credential that can fetch Fernet-encrypted secrets on demand. The MCP server exposes `get_credential`, `list_credentials`, `view_audit_log`, and `set_budget` tools over stdio, letting Claude or any MCP client pull decrypted keys with TTL bounds while recording every access. You get permission patterns like `stripe_*`, daily and monthly spend caps enforced at fetch time, and a full audit trail in Postgres. Reach for this when you're running multiple agents that need isolated access to production API keys without hardcoding secrets or building your own vault. Self-host or use the hosted Railway instance with Stripe billing tiers.
- tools
- 5
- auth
- Secret needed
- transport
- STDIO
- env vars
- 2
- last updated
- May 13, 2026
Tools
5 toolsPublic tool metadata for what this MCP can expose to an agent.
list_credentialsLists credentials exposed through the MCP server.
Lists credentials exposed through the MCP server.
No parameter schema in public metadata yet.
get_credentialReturns the decrypted value of a credential (e.g. vault.get_credential("stripe_key")).
Returns the decrypted value of a credential (e.g. vault.get_credential("stripe_key")).
No parameter schema in public metadata yet.
vault_status
No parameter schema in public metadata yet.
set_budget
No parameter schema in public metadata yet.
view_audit_log
No parameter schema in public metadata yet.
Sponsors
Configuration
AGENTVAULT_API_URL*default: https://agentvault-api-production.up.railway.appBase URL of your AgentVault deployment
AGENTVAULT_AGENT_KEY*secretYour avk_ agent API key
Readme
AgentVault
AI-native credential management for autonomous agents. Store API keys with column-level Fernet encryption, issue unique avk_ keys to registered agent identities, proxy decrypted values with TTL, enforce per-agent spending budgets, log every access, and expose everything as an MCP server.
- Live API: https://agentvault-api-production.up.railway.app
- Docs: https://agentvault-api-production.up.railway.app/docs
- Status: Production (Railway + Postgres + Stripe live)
Why
Autonomous agents need API keys to do anything useful — Stripe, OpenAI, SendGrid, your own internal services. Three bad options today:
- Hardcode in the agent prompt or config. Leaks in logs, can't rotate, no audit trail.
- Pass via env vars at spawn. No per-agent isolation, no budget controls, no revocation without redeploy.
- Roll your own vault. Real work — encryption at rest and in transit, audit logs, key rotation, budget tracking.
Details
- Repository
- github.com/bch1212/agentvault
- Category
- AI & LLM Tools
- Package
agentvault-mcp- Transport
- STDIO
- Auth
- Required
- Registry
- MCP registry, active