VaultGuard is answering right now. Last checked 7 min ago. It exposes 1 tools.
Secret scanner preventing leaks of corporate keys and credentials.
Today is the operative word: we check VaultGuard every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.
claude mcp add vaultguard --transport sse https://vaultguard-mcp.vercel.app/api/mcp
https://vaultguard-mcp.vercel.app/api/mcp
[mcp_servers.vaultguard]
url = "https://vaultguard-mcp.vercel.app/api/mcp"
{
"mcpServers": {
"vaultguard": {
"url": "https://vaultguard-mcp.vercel.app/api/mcp"
}
}
}
{
"servers": {
"vaultguard": {
"type": "sse",
"url": "https://vaultguard-mcp.vercel.app/api/mcp"
}
}
}
This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
audit
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://vaultguard-mcp.vercel.app/api/mcp | sse | needs auth | 110 ms | 7 min ago |
High-speed regex and entropy-based scanner redacting API keys, JWT tokens, and credentials
Scan text and git diffs for committed credentials using real vendor key formats plus entropy.
GitHub Secret Scanner - Find Leaked API Keys | Gitleaks
Secret and credential management MCP — securely store, retrieve, manage API keys and tokens
Scans files for leaked secrets and API keys
Scans files for leaked secrets and API keys
MCP server security scanner: detects prompt injection, credential leaks, SSRF, tool poisoning.
Context-aware secret scanner: lets an AI agent scan, verify, and rewrite secrets before committing.
Answers built from our own checks of this server.