# Aguara MCP [Health: Active]

**Category:** 🔒 Security  
**Repository:** https://github.com/garagon/aguara-mcp  
**GitHub Stars:** 4  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/aguara-mcp

## Description
Security scanner for AI agent skills and MCP servers

## Tools
Capabilities this server exposes over MCP:

- **scan_content** — Scan text for security threats before acting on it. Works on agent skills, READMEs, tool definitions, MCP server descriptions, prompts, package manifest content (`package.json`), GitHub Actions workflow YAML when the `filename` argument contains `.github/workflows/`, Claude Code settings when `file…
- **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`, credential exposure in `env`, unsafe argument injection, and tool-poisoning patterns. Use on any `mcpServers` entry from Claude Desktop, Cursor, VS Code,…
- **list_rules** — Browse the embedded engine's catalog: 259 detections (191 YAML pattern rules + 68 analyzer-emitted rules). Useful when the agent needs to understand a finding or filter by category. Catalog availability is not activation: bundle checks and stateful monitoring are not available through these single-…
- **explain_rule** — Get detailed information about a specific rule by ID. Resolves both YAML rules (returns patterns plus true/false-positive examples) and analyzer-emitted rule IDs from ci-trust, pkgmeta, jsrisk, pyrisk, rsbuild, npm-policy, pnpm-policy, agent-policy, NLP, toxic-flow, and rug-pull (returns severity,…
- **discover_mcp** — Discover MCP server configurations on the local machine by reading known MCP client config files (Claude Desktop, Cursor, VS Code, Windsurf, and others). Returns client identifiers, response-local config/server IDs, and argument/environment counts. Commands, arguments, environment keys and values,…

## Claude Desktop Quick Installation
No generated config for this server: it installs through its own setup steps.

The project's own setup steps (from https://github.com/garagon/aguara-mcp), copied verbatim. Run them in order; they are not an mcpServers config.

1. Install:

```sh
git clone https://github.com/garagon/mcp-aguara.git
```

2. Install:

```sh
cd mcp-aguara
```

3. Install:

```sh
make build    # → ./aguara-mcp
```

## Documentation

## What Aguara MCP does

Aguara MCP adds local security review tools to an MCP-compatible agent. It is intended for checking third-party agent skills, README files, prompts, tool definitions, MCP server descriptions, package metadata, workflow files, and client configuration before the agent trusts or executes them.

The scanner looks for prompt injection, credential exposure, data exfiltration, command execution, supply-chain risks, MCP-specific attacks, package-install payloads, risky GitHub Actions trust chains, unsafe agent configuration, and Unicode or encoding evasion. Sensitive matches are redacted in results so a finding does not reproduce a detected secret.

## How it works

The server imports Aguara as a Go library and performs scans inside the MCP process. It does not call an LLM, access the network, or invoke the `aguara` command-line binary. Results include a `clean`, `flag`, or `block` verdict, severity-rated findings, remediation guidance, line numbers, confidence scores, matched patterns where safe, and the analysis engine responsible for each finding.

`scan_content` can use a filename hint to select context-specific checks. It supports context-aware handling through `tool_name`, enforcement profiles, minimum severity thresholds, and caller-selected disabled rules. `check_mcp_config` accepts an MCP configuration as JSON and checks commands, arguments, environment variables, argument injection, and tool-poisoning patterns before a client enables the configuration.

## Setup and configuration

Install the binary with the project’s shell installer. The installer verifies SHA256 checksums and stops if no SHA256 verifier is available. Ensure `~/.local/bin` is on `PATH`, then register `aguara-mcp` over stdio with the chosen MCP client.

Claude Code can add it with `claude mcp add aguara -- aguara-mcp`. Claude Desktop uses an `mcpServers` entry whose command is `aguara-mcp`; Cursor, Windsurf, and other MCP clients can use the same stdio command. Building from source requires Go 1.26 or later.

## Tools and capabilities

- Recognized content includes skills, prompts, READMEs, tool definitions, MCP descriptions, `package.json`, selected workflow and agent-instruction files, Claude Code settings, and npm or pnpm policy files.
- `check_mcp_config`: Reviews an MCP server JSON configuration before installation or activation.
- `list_rules`: Filters the embedded catalog of 259 detections by category.
- `explain_rule`: Provides details for a rule ID, including remediation and, for YAML rules, patterns and examples.
- `discover_mcp`: Reads known local client configuration files and returns a redacted inventory with client identifiers, server IDs, and argument or environment counts.

## Limitations and notes

The MCP server provides single-content scans rather than repository-wide dependency auditing. Checks for npm, PyPI, pnpm, Go, crates.io, Composer, RubyGems, Maven, and NuGet repositories remain available through the Aguara CLI. Discovery output is a redacted inventory, not scan input or a security verdict; pass the original configuration JSON to `check_mcp_config`. The embedded engine contains rules and analyzers, but catalog availability does not activate bundle checks or stateful monitoring through these MCP tools.

_Full upstream README: https://allmcps.com/mcp/aguara-mcp/readme_