Security scanner for AI agent skills and MCP servers. Static analysis, incident response, no LLM. One binary. Detection engine behind oktsec.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"aguara": {
"args": [
"-y",
"caches"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Security scanner for AI agent skills and MCP servers. Detect prompt injection, data exfiltration, and supply-chain attacks before they reach production.
This server supports HTTP transport. Be the first to test it — help the community know if it works.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked caches against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in security
An evil MCP server used for redteam testing
Proof primitive for AI agents on MultiversX. Anchor file hashes on-chain as verifiable proofs.
AI-powered reverse engineering assistant that bridges IDA Pro with language models through MCP.
Security-first platform for AI agents. 38 specialized agents, 15 AI-powered extensions, zero-knowledge multi-agent orchestration. SENTINEL WAF, Ed25519 auth, 2.6M grounding facts.
MCP Security Weekly
Get CVE alerts and security updates for Aguara and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Security scanner for AI agents and software supply chains.
Aguara checks the trust points modern projects rely on: dependencies, lockfiles, install scripts, CI workflows, MCP configs, and AI agent tools.
Installation • Quick Start • What Aguara Checks • Supply-Chain Check • AI Agent & MCP Security • CI Integration • Rules • Contributing
https://github.com/user-attachments/assets/851333be-048f-48fa-aaf3-f8cc1d4aa594
Local-first. No SaaS account. No telemetry. No LLM calls. Signed releases.
Supply-chain attacks are not just vulnerabilities in your code. They often arrive through something your project is about to trust: a dependency version, an install script, a lockfile entry, a CI workflow, or an agent tool.
Security reviews used to focus mostly on application code. Modern projects also depend on package registries, lockfiles, install scripts, CI workflows, MCP servers, and AI agent tools. Recent supply-chain incidents have shown the pattern: a legitimate package publishes a malicious version, a project installs it, and the attacker gets a chance to steal tokens, cloud credentials, CI secrets, or local files.
Aguara gives teams a local check before they trust those inputs:
npm install, pnpm install, or yarn install (Aguara reads package-lock.json, pnpm-lock.yaml, and yarn.lock directly, no install needed)For dependencies, Aguara reads resolved lockfiles where it has parsers (today this is pnpm-lock.yaml, package-lock.json, yarn.lock classic, plus Go / Rust / PHP / Ruby / Java / .NET lockfiles) and installed package trees otherwise. So a freshly cloned npm, pnpm, or yarn project can be checked before any install runs. Yarn Berry (v2+) lockfiles are the next-layer parser, not shipping today.
brew install garagon/tap/aguara
docker run --rm -v "$PWD:/repo:ro" ghcr.io/garagon/aguara:0.22.0 check /repo
The image is multi-arch (linux/amd64 and linux/arm64), runs as non-root UID 10001, base images are digest-pinned, and the image is signed at the digest with Cosign plus SPDX SBOM and SLSA proven