
VaultGuard
Scan repos and artifacts from your agent for leaked API keys, tokens, and corporate credentials before merge or deploy.
Overview
VaultGuard is a MCP server for the Ship phase that scans for leaked secrets and credentials to reduce accidental key exposure before release.
What is this MCP server?
- Secret scanner oriented toward corporate keys and credentials
- Agent-invokable via remote SSE MCP
- Supports pre-ship and pre-publish hygiene checks
- Premium remote tier may require EIP-3009 payment-signature header
- Complements manual .env discipline with automated leak detection
- Server version 1.0.0 per published server.json
- One documented remote SSE endpoint on vaultguard-mcp.vercel.app
- Payment-signature header documented for premium settlement
What problem does it solve?
You ship often and fear an API key or corporate credential slipped into a repo, log, or pasted file your agent just generated.
Who is it for?
Indie developers and tiny teams auditing code and docs for hardcoded secrets immediately before merge or launch.
Skip if: Enterprises needing full secret lifecycle management, HSM integration, or certified penetration testing engagements.
What do I get? / Deliverables
You get agent-driven secret leak signals you can remediate before push, deploy, or public repo exposure.
- Leak findings for keys and credentials in scanned material
- Security-oriented signal to block or fix before release
Recommended MCP Servers
Journey fit
How it compares
Agent-callable secret scanner MCP, not a hosted vault product or IAM console.
Common Questions / FAQ
Who is VaultGuard for?
Builders who use AI coding agents and need a quick MCP-backed pass to catch credential leaks before shipping or open-sourcing work.
When should I use VaultGuard?
Use it in Ship security checks before merging, tagging a release, or publishing a repo—especially after agent-generated config or env examples.
How do I add VaultGuard to my agent?
Add the SSE remote MCP URL https://vaultguard-mcp.vercel.app/api/mcp to your client configuration; include the payment-signature header when premium settlement is required.