The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Agentguard listing page.
MCP server for @mukundakatta/agentguard. Lets Claude Desktop, Cursor, Cline, Windsurf, Zed, or any other MCP client check whether a URL is allowed under a network-egress policy before any fetch.
Three tools:
check_url — single URL check: returns { allowed, reason } without making any actual request.check_urls_batch — batch check with per-URL decisions plus a summary.validate_policy — sanity-check a policy spec for empty allowlists, overly broad * wildcards, and malformed host patterns.Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
Same shape for Cursor (~/.cursor/mcp.json), Cline, Windsurf, Zed.
check_url:
Returns:
check_urls_batch:
Returns:
validate_policy:
Returns issues for the * wildcard, the scheme prefix, and the path suffix — common mistakes when first writing a policy.
@mukundakatta/agentguard is a zero-dependency JavaScript library. This MCP server makes its decision engine accessible from any MCP-aware AI assistant: ask Claude "does my agent's tool list pass this firewall?" or "which of these 50 URLs would my policy block?" and the assistant calls these tools directly.
Note: this MCP server only checks URLs — it does not actually wrap fetch or block real requests. For runtime enforcement, use @mukundakatta/agentguard directly inside your Node process.
Part of the agent-stack series:
@mukundakatta/agentfit-mcp — Fit it.@mukundakatta/agentguard-mcp — Sandbox it. (this)@mukundakatta/agentsnap-mcp — Test it.@mukundakatta/agentvet-mcp — Vet it.@mukundakatta/agentcast-mcp — Validate it.MIT