Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-rudraneel93-mcp-guardian": {
"args": [
"-y",
"fix"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A safety layer between your AI assistant and the tools it uses.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'fix' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked fix against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in devops
MCP server for using the GitLab API
A Unified MCP Server Management App (MCP Manager).
MCP server for Komodo - manage Docker containers, servers, stacks, and deployments via AI
MCP-NixOS - Model Context Protocol Server for NixOS resources
MCP Security Weekly
Get CVE alerts and security updates for io.github.rudraneel93/mcp-guardian and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A safety layer between your AI assistant and the tools it uses.
Version 4.1.8 · Website · npm · Install & troubleshooting · Changelog
enabled: false is honored across rule strategies with backward-compatible defaultsmcp-guardian start — one command for proxy + web dashboard on port 4000 (local dev defaults)mcp-guardian setup — one-shot install for git clones (pnpm install, build, dashboard SPA)deploy/dashboard-spa/out/) built at publish time@mcp-guardian/server@4.1.4 registry manifest (workspace: deps). Use 4.1.5+.mcp-guardian onboard from global npm — resolves the installed package root (not cwd); writes guardian-configs/ under your current directory; ships scripts/guardian-proxy.sh and policy-audit.yaml in the npm tarballnpm install fix — registry manifest now matches published tarballs (^4.1.3 semver deps, not workspace:). Use @mcp-guardian/server@4.1.3 or later. Publish via ./scripts/publish-npm-all.sh (server/CLI ship from .tgz so metadata stays correct).
npm install hygiene — fixes supply-chain scanner findings from 4.1.0:
postinstall or other lifecycle scriptsworkspace: dependencies are rewritten to semver (^4.1.1) at pack time./scripts/publish-npm-all.sh (core → plugin-sdk → server → cli)Industry roadmap plan compliance — runtime verification and dashboard wiring for all eleven fleet-wide modules (A1–C5, B1–B3):
guardian roadmap audit — CLI + GET /api/agentic/plan-compliance/audit verify every shipped module; exit 0 when production-ready