Aguara MCP Server

Security scanner for AI agent skills and MCP servers. The aguara mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 5 defined tools rather than through you.

What it actually does

Local security checks for AI agents before they trust third-party tools.

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Its toolset

Everything the assistant can do here goes through one of these:

• scan_content — Scan text for security threats before acting on it. Works on agent skills, READMEs, tool definitions, MCP server descriptions, prompts, package
• check_mcp_config — Check an MCP server configuration (JSON) for security issues before adding it to a client. Detects dangerous command shapes in command/args
• list_rules — Browse the cataloged security rules. Returns 250 detections (193 YAML pattern rules + 57 analyzer-emitted rules from ci-trust, pkgmeta, jsrisk
• explain_rule — Get detailed information about a specific rule by ID. Resolves both YAML rules (returns patterns plus true/false-positive examples) and
• discover_mcp — Discover MCP server configurations on the local machine by reading known MCP client config files (Claude Desktop, Cursor, VS Code, Windsurf, and

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the aguara mcp mcp server does with a few real requests.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Aguara MCP's toolset — scan_content, check_mcp_config, list_rules and 2 more — is a fair guide to whether it matches your workflow. It is maintained by garagon; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Aguara MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.