A side-by-side look at the MCP Audit and MCP Security Guard 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 Security Guard 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 Audit
No confirmed install command for MCP Audit yet — follow the setup steps linked from its listing page rather than a guessed package name.
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.
Frequently asked questions
MCP Audit is categorized under Security and uses an install path we have not confirmed yet. MCP Security Guard belongs to Security and uses an install path we have not confirmed yet. Pick MCP Audit for security work and MCP Security Guard 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 Audit has no declared pricing — check the project's own site. MCP Security Guard is listed as free. Auth: no auth required. 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-audit-2 and mcp-security-guard as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Audit has a quality signal of 33/100 (Emerging) with 1 views, 0 installs and 2 GitHub stars. MCP Security Guard has 32/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars.