Aguara MCP
OCI · GHCR.IO/GARAGON/MCP-AGUARA:0.8.0 · SCANNED SEP 20
Scan skills, MCP configs, and agent content for injection and supply-chain risks. Offline, no LLM.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 80 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 992 tokens (~198/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the Aguara MCP server?
Aguara MCP runs locally as a container image, launched with docker run --rm -i ghcr.io/garagon/mcp-aguara:0.8.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/garagon/mcp-aguara:0.8.0
claude mcp add garagon-mcp-aguara -- docker run --rm -i ghcr.io/garagon/mcp-aguara:0.8.0
{
"mcpServers": {
"garagon-mcp-aguara": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/garagon/mcp-aguara:0.8.0"
]
}
}
} {
"servers": {
"garagon-mcp-aguara": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/garagon/mcp-aguara:0.8.0"
]
}
}
} codex mcp add garagon-mcp-aguara -- docker run --rm -i ghcr.io/garagon/mcp-aguara:0.8.0
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"garagon-mcp-aguara": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/garagon/mcp-aguara:0.8.0"
],
"enabled": true
}
}
} mcp_servers:
garagon-mcp-aguara:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/garagon/mcp-aguara:0.8.0"] {
"McpServers": {
"garagon-mcp-aguara": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/garagon/mcp-aguara:0.8.0"
]
}
}
} {
"mcpServers": {
"garagon-mcp-aguara": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/garagon/mcp-aguara:0.8.0"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
- 8 Sept 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed oci/ghcr.io/garagon/mcp-aguara:0.8.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_mcp_config ~196
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 MCP server config block (`mcpServers` entries from Claude Desktop, Cursor, VS Code, etc.) before installing or enabling it. Sensitive matches are redacted in the response.
| Name | Type | Req | Description |
|---|---|---|---|
| config | string | yes | The MCP configuration as a JSON string |
| disabled_rules | array | – | List of rule IDs to disable (e.g., ["PROMPT_INJECTION_001"]) |
| min_severity | string | – | Minimum severity to report: INFO, LOW, MEDIUM, HIGH, or CRITICAL |
| scan_profile | string | – | Scan profile: strict (default, all rules), content-aware (reduced FP for known tools), or minimal (flag-only mode) |
No output schema declared.
No examples provided.
discover_mcp ~86
Discover MCP server configurations on the local machine by reading known MCP client config files (Claude Desktop, Cursor, VS Code, Windsurf, and others). Returns the server definitions including commands, arguments, and environment variables. Read-only: this tool never executes the discovered commands and never connects to any server; pair with `check_mcp_config` to evaluate each definition before acting on it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
explain_rule ~121
Get detailed information about a specific security rule by ID. Resolves both YAML rules (returns patterns plus true/false-positive examples) and analyzer-emitted rules from ci-trust, pkgmeta, jsrisk, pyrisk, rsbuild, npm-policy, pnpm-policy, agent-policy, NLP, toxic-flow, and rug-pull (returns severity, category, analyzer name, description, and remediation; analyzer rules have no inline patterns or examples).
| Name | Type | Req | Description |
|---|---|---|---|
| rule_id | string | yes | The rule ID to explain (e.g., PROMPT_INJECTION_001) |
No output schema declared.
No examples provided.
list_rules ~151
List the security rules cataloged by Aguara. Returns 250 detections (193 YAML pattern rules + 57 analyzer-emitted rules from ci-trust, pkgmeta, jsrisk, pyrisk, rsbuild, npm-policy, pnpm-policy, agent-policy, NLP, toxic-flow, and rug-pull analyzers) spanning multiple threat categories. Optionally filter by category (e.g. `prompt-injection`, `exfiltration`, `credential-leak`, `supply-chain`, `mcp-attack`, `toxic-flow`, `agent-trust`).
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter rules by category (e.g., prompt-injection, exfiltration, credential-leak) |
No output schema declared.
No examples provided.
scan_content ~398
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 filename contains `.github/workflows/`, Claude Code settings when filename is `.claude/settings.json` or `.claude/settings.local.json`, agent instruction files (`.cursorrules`, `.windsurfrules`, `.clinerules`, `AGENTS.md`, `copilot-instructions.md`), npm install-trust policy when filename is `.npmrc` or `package.json`, and pnpm policy when filename is `pnpm-workspace.yaml`. Detects prompt injection (pattern + NLP), credential leaks, data exfiltration, command execution, supply-chain patterns, MCP attacks, package metadata risks, JavaScript / Python / Rust install-time payload shapes, GitHub Actions trust chains, risky agent host configuration, weakened npm / pnpm supply-chain settings, and Unicode / encoding evasion. Findings are categorized by severity with remediation hints. Sensitive matches are redacted before output. Supports context-aware false-positive reduction via tool_name.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The text content to scan (e.g., skill description, README, tool definition) |
| disabled_rules | array | – | List of rule IDs to disable (e.g., ["PROMPT_INJECTION_001"]) |
| filename | string | – | Filename hint for the content (affects rule matching). Default: skill.md |
| min_severity | string | – | Minimum severity to report: INFO, LOW, MEDIUM, HIGH, or CRITICAL |
| scan_profile | string | – | Scan profile: strict (default, all rules), content-aware (reduced FP for known tools), or minimal (flag-only mode) |
| tool_name | string | – | Tool that generated the content (e.g., Bash, Edit, WebFetch). Enables context-aware false-positive reduction |
No output schema declared.
No examples provided.
What is the Aguara MCP server?
Aguara MCP is listed in the public MCP registry as io.github.garagon/mcp-aguara. Scan skills, MCP configs, and agent content for injection and supply-chain risks. Offline, no LLM. This page covers its container image (ghcr.io/garagon/mcp-aguara:0.8.0).
Is the Aguara MCP server safe to use?
Aguara MCP scores 53 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Aguara MCP server expose?
Aguara MCP exposes 5 tools: check_mcp_config, discover_mcp, explain_rule, list_rules, scan_content. Their descriptions and schemas cost roughly 952 tokens of context every time the server is loaded.
Is the Aguara MCP server still maintained?
Aguara MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Aguara MCP server under?
Aguara MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.