A side-by-side look at the MCP Security Guard and MCP Audit MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
No tool names declared yet. Check the project README from the listing page.
MCP Audit tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MCP Security Guard
No confirmed install command for MCP Security Guard yet — follow the setup steps linked from its listing page rather than a guessed package name.
MCP Audit
No confirmed install command for MCP Audit yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
MCP Security Guard is categorized under Security and uses an install path we have not confirmed yet. MCP Audit belongs to Security and uses an install path we have not confirmed yet. Pick MCP Security Guard for security work and MCP Audit for security.
Neither server has a confirmed install command yet, so we don't publish a guessed config. Follow each project's own setup instructions, linked from its listing page.
MCP Security Guard is listed as free. Auth: no auth required. MCP Audit has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mcp-security-guard and mcp-audit-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Security Guard has a quality signal of 32/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars. MCP Audit has 33/100 (Emerging) with 1 views, 0 installs and 2 GitHub stars.